This is the developer blog for Twiki, one of the most powerful wikis. http://twiki.org/cgi-bin/view/Blog/WebHome?category=Development http://twiki.org/cgi-bin/

This is the developer blog for Twiki, one of the most powerful wikis. http://twiki.org/cgi-bin/view/Blog/WebHome?category=Development http://twiki.org/cgi-bin/view/Blog/WebHome?category=Developm... Here are some things to consider up front: * Pluggable authentication and authorization. In the beginning both are simple, but if you weave that simple assumption into the code, it will be hard to add finer grained control. * Keep read latency low. This might mean some form of caching. Twiki is slow in my experience. * Expose all features to a web service interface from day one. Don't weld functionality to the GUI. Side benefit: makes testing your software easier. See: http://twiki.org/cgi-bin/view/Blog/2007-11-14-how-to-rest http://twiki.org/cgi-bin/view/Blog/2007-11-14-how-to-rest I think you'll find much of what you want by poking around the Twiki site.