X-Git-Url: http://git.tremily.us/?p=ikiwiki.git;a=blobdiff_plain;f=doc%2Ftodo.mdwn;h=d7326854efd2c79c5b0481072e82825137c693d3;hp=dd69e21fb6cf95d8a4ca65a783b65d032440500a;hb=2aa59621153fcba1d72d7c7688037f1fdfa7f95f;hpb=7144eb3973ac73a5f79440f91a7c01665fb83aa4 diff --git a/doc/todo.mdwn b/doc/todo.mdwn index dd69e21fb..d7326854e 100644 --- a/doc/todo.mdwn +++ b/doc/todo.mdwn @@ -1,6 +1,5 @@ ## online page editing -* Missing support for preview. * Missing conflict detection, just overwrites changes and does not svn up first.. * Eventually, might want page deletion. @@ -19,10 +18,31 @@ is built. (As long as all changes to all pages is ok.) already, so just look at the userdb, svnlook at what's changed, and send mails to people who have subscribed. -## docs + A few details: + 1. [[Joey]] mentioned that being able to subscribe to globs as well as + explicitly named pages would be desirable. + 2. I think that since we're using Perl on the backend, being able to + let users craft their own arbitrary regexes would be good. -Need to turn [[usage]] into a man page. -this wiki too. Can markdown generate a man page somehow? + Joey points out that this is actually a security hole, because Perl + regexes let you embed (arbitrary?) Perl expressions inside them. Yuck! + + 3. Of course if you do that, you want to have form processing on the user + page that lets them tune it, and probably choose literal or glob by + default. + + The first cut, I suppose, could use one sendmail process to batch-mail all + subscribers for a given page. However, in the long run, I can see users + demanding a bit of feature creep: + + 4. Each user should be able to tune whether they see the actual diff parts or + not. + 5. Each user should be able to set a maximum desired email size. + 6. We might want to support a user-specified shibboleth string that will be + included in the email they receive so they can easily procmail the messages + into a folder. + + --[[BrandenRobinson]] ## pluggable renderers @@ -77,13 +97,19 @@ recentchanges that goes to the diff for any listed change. Possibly add "next 100" link to it, but OTOH, you can just use svn log if you need that data.. -## setup classes +## base wiki + +Need a toned down version of this wiki with a basic frontpage, sandbox and +docs to use as a seed for new wikis. + +## search + +* full text (use third-party tools?) +* list of all missing pages +* list of all pages or some kind of page map + +## page indexes -The setup files should "use WikiWiki::Setup" and the like at the top, and -indeed could just be one big use that passes all params to the module's -importer. The module then handles running ikiwiki functions. This would -allow for different types of setup files for more than just the one -hardcoded thing there is now, and would probably be good for upgrades, -incompatible changes, etc, too. +Might be nice to support automatically generating an index based on headers in a page, for long pages. The question is, how to turn on such an index? ## [[Bugs]]