> The other issue you currently mention (edits to the documentation / > webpage) was one of the major concerns. > Me and Holger pointed out that it would a good idea just to maintain the > developer documentation (see > http://saros-build.imp.fu-berlin.de/sarosGettingStarted/saros-getting- > started.pdf) > which could be updated through normal Gerrit Reviews and then add a process > that transform the original XML document into Drupal pages.
How about one of these modern static page generators that let you write Markdown? For instance, there is http://jekyllrb.com/ One would just have to write a template. After that, you can keep the whole website (template + Markdown files for the pages) in a Git repository and adopt the Gerrit code review flow. Regards, Denis ------------------------------------------------------------------------------ _______________________________________________ DPP-Devel mailing list DPP-Devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dpp-devel
