## online page editing
-* Missing conflict detection, just overwrites changes and does not svn up
- first..
-
- How to resolve this? Would this work when saving a page?
-
- 1. write changes to wc
- 2. svn up (so it can merge with any other changes)
- 3. check for conflicts
- 4. if conflicts, read in page w/conflict markers, svn revert page, and display resolution form
- 5. otherwise, svn commit
- 6. if commit fails, perhaps we were raced and there are conflicts still; so check for conflicts and if found, goto 2.
-
- Note that unless we use `svn lock`, we really can't "warn" about concurrent edits and such the way other wikis do, which is ok, since that system sucks anyway. Using svn up for smart merging will be much nicer most of the time.
-
* Eventually, might want page deletion.
* Eventually, might want file upload.
Possibly add "next 100" link to it, but OTOH, you can just use svn log if
you need that data..
-## 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?)
Probably it's ok if locking is only supported for web commits.
+## User settings page
+
+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).
+
+## 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.
+
+## Page last-changed timestamps
+
+Of course you can go to the history to see when a page last changed in svn, still, it will be nice to have a timestamp at the bottom of pages. Should be based on the modification date of the source file, not the last rebuild date.
+
## [[Bugs]]