## recentchanges
-* Should support RSS for notification of new and changed pages.
-
- This can be a static rss file that is generated when the moo
-is built. (As long as all changes to all pages is ok.)
-
* Should support mail notification of new and changed pages.
Hmm, should be easy to implement this.. it runs as a svn post-coommit hook
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:
also needs to tie into the main logic, to determine what pages need to be
renered, so maybe that won't be a plugin.
+## blogging
+
+- Add a small form at top and bottom of a blog to allow entering
+ a title for a new item, that goes to a template to create the new page.
+- Should probably add params to control various rss fields like the blog
+ title, its author email, its copyright info, etc.
+
## revisit case
Being case insensative is handy, but it does make the [[BackLinks]] a bit
## search
+* page name substring search
* full text (use third-party tools?)
+
+## lists
+
* list of all missing pages
-* list of all pages or some kind of page map
+
+This could be its own static pages updated when other pages are updated.
+Perhaps this ties in with the pluggable renderers stuff.
## 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
-## page locking
+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.
-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.
+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.
-Probably it's ok if locking is only supported for web commits.
+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.
-## User settings page
+## wikilinks features
-A cgi page to allow a user to log out and to edit their prefs, including password, email, and anything we add later (subscriptions, etc).
+- \[[John|Fred]] is a Wikipedia method for linking to the one page
+ while displaying it as the other, Kyle would like this.
## Logo
-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.
+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]]
sipb-www / ikiwiki.git / blobdiff