underlays are *hard*. feh

[ikiwiki.git] / doc / todo.mdwn

diff --git a/doc/todo.mdwn b/doc/todo.mdwn
index 5c79219fefdf0fb1208f28058673e4f3700e4a42..bdebfb88c42b81b32648225c41df480d4c83bd87 100644 (file)
--- a/doc/todo.mdwn
+++ b/doc/todo.mdwn
@@ -7,7 +7,7 @@
 
 * Should support RSS for notification of new and changed pages. 
 
 
 * Should support RSS for notification of new and changed pages. 
 

-  This can be a static rss file that is generated when the moo
+  This can be a static rss file that is generated when the wiki

 is built. (As long as all changes to all pages is ok.)
 
 * Should support mail notification of new and changed pages.
 is built. (As long as all changes to all pages is ok.)
 
 * Should support mail notification of new and changed pages.


@@ -31,6 +31,9 @@ is built. (As long as all changes to all pages is ok.)
      page that lets them tune it, and probably choose literal or glob by
      default.
 
      page that lets them tune it, and probably choose literal or glob by
      default.
 

+     I think that the new globlist() function should do everything you need.
+     Adding a field to the prefs page will be trivial --[[Joey]]
+

   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:
   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:


@@ -72,7 +75,9 @@ case.
 
 ## html
 
 
 ## html
 

-Make the html valid. Add css.
+Make the html valid. Add css and prettify. Make RecentChanges use table for formatting, and images to indicate web vs svn commits and to link to diffs.
+
+All of this should be doable w/o touching a single line of code, just editing the [[templates]] BTW.

 
 ## sigs
 
 
 ## sigs
 


@@ -87,11 +92,6 @@ design goals for ikiwiki: keeping as much markup as possible out of the
 wiki and not adding nonstandard markup. And it's not significantly hard to
 type "--\[[Joey]]", and as to the date, we do have page history.
 
 wiki and not adding nonstandard markup. And it's not significantly hard to
 type "--\[[Joey]]", and as to the date, we do have page history.
 

-## recentchanges links to commit diffs
-
-Would take a bit more viewcvs integration, let the be a "[diff]" link in
-recentchanges that goes to the diff for any listed change.
-

 ## recentchanges more than 100
 
 Possibly add "next 100" link to it, but OTOH, you can just use svn log if
 ## recentchanges more than 100
 
 Possibly add "next 100" link to it, but OTOH, you can just use svn log if


@@ -105,12 +105,29 @@ you need that data..
 
 ## page indexes
 
 
 ## page indexes
 

-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?
+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?
+
+## basewiki underlay
+
+Rather than copy the basewiki around everywhere, it should be configured to
+underlay the main srcdir, and pages be rendered from there if not in the
+srcdir. This would allow upgrades to add/edit pages in the basewiki.
+
+Impementaion will be slightly tricky since currently ikiwiki is hardcoded
+in many places to look in srcdir for pages. Also, there are possible
+security attacks in the vein of providing a file ikiwiki would normally
+skip in the srcdir, and tricking it to processing this file instead of the
+one from the underlaydir.

 
 

-## page locking
+There are also difficulties related to removing files from the srcdir, and
+exposing ones from the underlaydir. Will need to make sure that the mtime
+for the source file is zeroed when the page is removed, and that it then
+finds the underlay file and treats it as newer.

 
 

-Some wikis will need the abiity to lock a page, or the whole wiki, so that only admins can edit them. Probably using the same globbing as for recentchanges mails to determine what to lock. 
+## Logo

 
 

-Probably it's ok if locking is only supported for web commits.
+ikiwiki needs a logo. I'm thinking something simple like the word "ikiwiki"
+with the first "k" backwards; drawn to show that it's "wiki" reflected.

 
 ## [[Bugs]]
 
 ## [[Bugs]]