Hi, I would also recommend to stay at gdoc. I also evaluated AsciiDoctor and there are a lot of formatting and exporting issues to be solved and currently (as Martin said already) the process is rather simple to update the documentation and it is well integrated in the build process.
If there aren't any big issues with gdoc it would be wasted time to migrate it to ascii doc. kind regards Tobias > Am 26.05.2015 um 14:18 schrieb Martin Grigorov <mgrigo...@apache.org>: > > Hi, > > I remember an earlier discussion about this change. > Can you please list what are the benefits? > One thing I remember is that GDoc is deprecated and Grails community won't > develop it anymore. > But the current version seems to work pretty well (Grails 2.4). It is well > integrated with our Maven build too. > > For Apache Isis Dan Haywood had to implement some extra Ruby scripts to > improve something. I don't quite follow his work on this, but such custom > Ruby scripts bother me a bit because I'm not sure how easy this will be > integrated with Maven and Apache CI servers. > > Martin Grigorov > Wicket Training and Consulting > https://twitter.com/mtgrigorov > > On Tue, May 26, 2015 at 3:01 PM, Martijn Dashorst < > martijn.dasho...@gmail.com> wrote: > >> All, >> >> At my company we have the option of hiring a temp during the summer >> holidays, and one of the things I'd like the temp to do is a migration >> of our user manual from GDoc format to ASCIIdoctor. >> >> This is of course, if you would be willing to accept such a format >> change, and if the temp is willing to perform the task. >> >> This would probably be a search/replace of tags. I don't know how much >> work it would entail, but it is not trivial considering the size of >> the manual. >> >> The temp could probably start soon, and I'd be mentoring this work >> (but you are welcome to mentor as well if you want) >> >> What do you think? >> >> Martijn >>
