You're right that the routes on kiwi.drasticcode.com leave something to be desired. I was mainly focused on getting a demo of the parser working, and didn't put a lot of thought into the urls, or try to follow any wiki best practices. I did try to avoid some of the MediaWiki conventions, like putting colons in routes, or indicating the action with a GET param. I've found these can be tricky to duplicate in other frameworks like Rails, which doesn't easily support those.

I would like to find the time to address this (although Karl's right that I would welcome contributions.) I'm considering that a routing scheme like this might work:

GET /wiki/a-page-name GET /wiki/another/page GET /edit/another/page GET /upload/someFile.jpg POST /wiki/another/page # update or create

Are there any obvious problems with this approach I might want to consider?

Thanks Sam Goldstein

On Thu, Feb 3, 2011 at 12:41 AM, Platonides <platonides at gmail.com> wrote:

Karl Matthias wrote:

...

...

The url mapping used there, make some titles impossible to use, such as making an entry for [[Edit]] - http://en.wikipedia.org/wiki/Edit

You are right about that. I'm sure Sam would be happy to accept contributions to change that. The site does support double-click to edit, though, so making links to Edit is kind of unnecessary.

It's not just edit, but all actions, such as upload. The real solution is to have the wiki items inside a "folder" and the actions outside. You could prefix actions, like mediawiki does (eg. Action:Edit, and forbidding pages starting with Action:) but you would still have the classic problems for root folder items such as favicon.ico. See http://www.mediawiki.org/wiki/Manual:Wiki_in_site_root_directory#Reasons_why...