Best Use of the Google Wiki Code for Project Documentation

Question

I recently migrated my project from source to Google code. I am intrigued by the wiki version of Google, which integrates with svn, but I'm not sure about using it to provide design documentation.

For my project, the documentation can be displayed in three places: (1) on the wiki, (2) on the desktop application that I am developing (using wxPython), and (3) on the project website (which is http: //www.openstv. org and is based on Drupal).

I like the idea of ​​using the Google Wiki code as the main source of documentation, and then automatically including this documentation both in the desktop application and on the project website.

Does anyone have any suggestions for this?

Answer 1

Wiki files live in Subversion - just svn checkout http://yourproject.googlecode.com/svn/wiki yourwiki and you get yourwiki svn yourwiki that is easy to update (just svn up in it from time to time, for example, in crontab).

The Wiki file format is a variant of Google ReSTructured Text , so that you can write scripts to convert them to regular restart and from there to any other formats that you prefer for your other purposes - or, write ReST on your system, convert it to any convenient for you (including, possibly, Google wiki format ;-), and download this ...