36 lines
1.8 KiB
Markdown
36 lines
1.8 KiB
Markdown
Currently implemented:
|
|
|
|
* [[Subversion]]
|
|
|
|
Rather than implement its own system for storing page histories etc, ikiwiki simply uses subversion. (Supporting other revision control systems is also possible, ikiwiki only needs $FOO add, $FOO commit, and $FOO log).
|
|
|
|
Instead of editing pages in a stupid web form, you can use vim and commit changes via svn. Or work disconnected using svk and push your changes out when you come online. Deal with edit conflicts with others in a sane environment. Take advantage of subversion's smart merges.
|
|
|
|
ikiwiki can be run from a [[post-commit]] hook to update your wiki immediatly whenever you commit.
|
|
|
|
* [[MarkDown]]
|
|
|
|
ikiwiki supports pages using [[MarkDown]] as their markup language. Any
|
|
page with a filename ending in ".mdwn" is converted from markdown to html
|
|
by ikiwiki. Markdown understands text formatted as it would be in an email,
|
|
and is quite smart about converting it to html. The only additional markup
|
|
provided by ikiwiki aside from regular markdown is the [[WikiLink]].
|
|
|
|
* support for other file types
|
|
|
|
ikiwiki also supports files of any other type, including raw html, text,
|
|
images, etc. These are not converted to wiki pages, they are just copied
|
|
unchanged by ikiwiki as it builds your wiki. So you can check in an image,
|
|
program, or other special file and link to it from your wiki pages.
|
|
|
|
* [[SubPage]]s
|
|
|
|
Arbitrarily deep hierarchies of pages with fairly simple and useful [[SubPage/LinkingRUles]]
|
|
|
|
* [[RecentChanges]], editng pages in a web browser
|
|
|
|
Nearly the definition of a wiki, although perhaps ikiwiki challenges how much of that web gunk a wiki really needs. These features are optional and can be enabled by enabling [[CGI]].
|
|
|
|
----
|
|
|
|
It also has lots of [[TODO]] items and [[Bugs]]. This wiki is not ready for production! |