* [[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
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]] and
+ provided by ikiwiki on top of regular markdown is the [[WikiLink]] and
[[PreprocessorDirective]]
+ If you prefer to use some other markup language, ikiwiki allows others to
+ easily be added by [[plugins]]. For example it also supports traditional
+ [[plugins/WikiText]] formatted pages or pages written as pure
+ [[plugins/HTML]].
+
* support for other file types
ikiwiki also supports files of any other type, including plain text,
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
+* [[SubPages|SubPage]]
+
+ Arbitrarily deep hierarchies of pages with fairly simple and useful
+ [[SubPage/LinkingRules]]
- Arbitrarily deep hierarchies of pages with fairly simple and useful [[SubPage/LinkingRules]]
+* [[blogging|blog]]
-* [[blog]]s
+ 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.
- 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.
+ 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. Tags will show
+ up in the ways you'd expect, like at the bottom of pages, in blogs, and
+ in rss feeds.
* Fast compiler
* [[PageHistory]]
Well, sorta. Rather than implementing YA history browser, it can link to
- [[ViewCVS]] or the link to browse the history of a wiki page.
+ [[ViewCVS]] or the like to browse the history of a wiki page.
* [[RecentChanges]], editing pages in a web browser
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]]
- 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.
+ Plugins can be used to add additional features to ikiwiki. The interface
+ is quite flexible, allowing plugins to implement additional markup
+ languages, 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.
+
+* [[todo/utf8]]
+
+ After rather a lot of fiddling, we think that ikiwiki correctly and fully
+ supports utf8 everywhere.
+
+* [[w3mmode]]
+
+ Can be set up so that w3m can be used to browse a wiki and edit pages
+ without using a web server.
----