* [[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, and ikiwiki also includes support for [[Git]]
+ now.)
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
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]].
+ provided by ikiwiki aside from regular markdown is the [[WikiLink]] and
+ [[PreprocessorDirective]]
* 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.
Arbitrarily deep hierarchies of pages with fairly simple and useful [[SubPage/LinkingRules]]
-* [[blog]]s
+* [[blogging|blog]]
- You can turn any page in the wiki into a [[blog]]. Pages with names
- 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.
+ You can turn any page in the wiki into a [[blog]]. 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
- the flexible ways that this can be used.
+ Ikiwiki's own [[TODO]], [[news]], and [[plugins]] pages are good examples
+ of some of the flexible ways that this can be used.
+
+* [[tags]]
+
+ You can tag pages and use these tags in various ways.
* Fast compiler
* [[BackLinks]]
- Automatically included on pages. Rather faster than eg [[MoinMoin]] and always there to help with navigation.
+ Automatically included on pages. Rather faster than eg MoinMoin and
+ always there to help with navigation.
* [[PageHistory]]
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.
ikiwiki can be configured to send you commit mails with diffs of changes
to selected pages.
+* [[Plugins]]
+
+ 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.
+
----
It also has some [[TODO]] items and [[Bugs]].