* [[Subversion]]
Rather than implement its own system for storing page histories etc,
- ikiwiki simply uses subversion. (It's also possible to [[plugins/write]] support for other systems.)
+ 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
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.
- Ikiwiki's own [[TODO]], [[news]], and [[plugins]] 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
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.