Well ok, looking forward to see the single doc PDF export. ;-) +1 to move to asciidoctor (in a branch till it is finished)
kind regards Tobias > Am 26.05.2015 um 14:46 schrieb Martin Grigorov <[email protected]>: > > I am +1 to move to ASCIIdoctor if: > - the student finds the task interesting to work on > - the build is as easy as now > > Martin Grigorov > Wicket Training and Consulting > https://twitter.com/mtgrigorov > > On Tue, May 26, 2015 at 3:42 PM, Martin Grigorov <[email protected]> > wrote: > >> >> On Tue, May 26, 2015 at 3:37 PM, Martijn Dashorst < >> [email protected]> wrote: >> >>> Also, the asciidoctor project has great documentation coming with it >>> (I haven't been able to find any documentation regarding the gdoc >>> format). >> >> http://ci.apache.org/projects/wicket/guide/6.x/guide/contributing.html >> has a link to it: >> >> - The guide uses Grails GDoc to generate the final HTML/PDF so you >> should consult with its syntax <http://grails.org/WikiSyntax>. >> >> >> >>> >>> Martijn >>> >>> On Tue, May 26, 2015 at 2:36 PM, Martijn Dashorst >>> <[email protected]> wrote: >>>> Asciidoctor has many build options, including a maven plugin [1]. >>>> >>>> The default styling of asciidoctor is much more pleasing to the eye. >>>> The momentum for fixing issues and improving the output format is >>>> great, I rather use living technology than dead technology, and >>>> getting fixes for asciidoctor format on github is easy, as it is >>>> supported out of the box in the editors on github. >>>> >>>> Martijn >>>> >>>> >>>> On Tue, May 26, 2015 at 2:30 PM, Tobias Soloschenko >>>> <[email protected]> wrote: >>>>> 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 <[email protected] >>>> : >>>>>> >>>>>> 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 < >>>>>> [email protected]> 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 >>>> >>>> >>>> >>>> -- >>>> Become a Wicket expert, learn from the best: http://wicketinaction.com >>> >>> >>> >>> -- >>> Become a Wicket expert, learn from the best: http://wicketinaction.com >> >>
