* [[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).
+ ikiwiki simply uses subversion. (It's also possible to [[plugins/write]] support for other systems.)
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
* support for other file types
- ikiwiki also supports files of any other type, including raw html, text,
+ ikiwiki also supports files of any other type, including plain 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.
matching a specified [[GlobList]] will be displayed as a weblog within
the blog page. And an RSS feed can be generated to follow the blog.
- Ikiwikit's own [[TODO]] and [[news]] pages are good examples of some of
+ Ikiwiki's own [[TODO]], [[news]], and [[plugins]] pages are good examples of some of
the flexible ways that this can be used.
* Fast compiler
shown in the file to resolve the conflict, so if you're already familiar
with that there's no new commit marker syntax to learn.
- For all the gory details of how ikiwiki handles this behind the scenes,
- see [[commit-internals]].
-
* page locking
Wiki admins can lock pages so that only other admins can edit them.
* [[Plugins]]
- A plugin system allows extending ikiwiki in arbitrary ways.
+ Plugins can be used to add additional features to ikiwiki. The interface is quite flexible, allowing plugins to register [[PreProcessorDirective]]s, hook into [[CGI]] mode, and more. Ikiwiki's backend RCS support is also pluggable, so support for new revision control systems can be added to ikiwiki.
----