3 * Missing support for preview, cancel.
4 * Missing conflict detection.
5 * Missing commit message box.
6 * No support for web user tracking/login yet.
7 * Eventually, might want page deletion.
8 * Eventually, might want file upload.
12 Should support RSS for notification of new and changed pages.
16 Need to document all the command line switches in a man page and somehow on this wiki too. Can markdown generate a man page somehow?
18 ## pluggable renderers
20 I'm considering a configurable rendering pipeline for each supported
21 filename extension. So for ".mdwn" files, it would send the content through
22 linkify, markdown, and finalize, while for ".wiki" files it might send it
23 through just a wiki formatter and finalize.
25 This would allow not only supporting more types of markup, but changing
26 what style of [[WikiLink]]s are supported, maybe some people want to add
27 [[CamelCase]] for example, or don't like the [[SubPage/LinkingRules]].
29 The finalize step is where the page gets all the pretty junk around the
30 edges, so that clearly needs to be pluggable too.
32 There also needs to be a step before finalize, where stuff like lists of pages
33 that linked back to it could be added to the page. However, doing linkbacks
34 also needs to tie into the main logic, to determine what pages need to be
35 renered, so maybe that won't be a plugin.
39 Being case insensative is handy, but it does make the [[BackLinks]] a bit
40 ugly compared to other links. It should be possible to support pagenames
41 that have uppercase, while still allowing them to be linked to using any
46 prettfiy and validate html. css.
48 (Please god, save me from the html template monster though..)