Stefan wrote: > Me and Holger pointed out that it would a good idea just to maintain the > developer documentation [...] > which could be updated through normal Gerrit Reviews
True, it still is. Stefan wrote: > and then add a > process that transform the original XML document into Drupal pages. > > Unfortunately it seems that such a task was to hard for the assigned > student. In his defense: It was not his main goal, but more of a side quest. Anyway, I added this to the list of thesis ideas [1] (only in German). Denis wrote: > For instance, there is http://jekyllrb.com I'm not sure how this plays together with our Drupal setup, but it does not look like a completely absurd idea, e.g. [2]. Denis wrote: > 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. As stated here [1], there even *is* already a Git repo on Gerrit, incl. Jenkins jobs for "building" and "deployment". Cheers, Franz [1] http://www.inf.fu-berlin.de/w/SE/ThesesDPP#KnowledgeMgmtDevDoc [2] http://www.gizra.com/content/dekyll-drupal-on-jekyll/ -----Original Message----- From: Denis Washington [mailto:de...@denisw.de] Sent: Monday, August 24, 2015 12:48 PM To: Stefan Rossbach <srossb...@arcor.de>; dpp-devel@lists.sourceforge.net Subject: [DPP-Devel] Page editing (was: Coding Conventions <==> Practice) > 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 ------------------------------------------------------------------------------ _______________________________________________ DPP-Devel mailing list DPP-Devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dpp-devel
