Hi Tomo, Thank you for sharing that. I see asciidoctor (!= asciidoc) tooling as a good way to generate reference guides, not that good of a way to generate the whole static site. I think that's the reasoning why asciidoctor.org is using Awestruct.
zoran On Wed, Apr 25, 2018 at 10:49 PM, Tomohisa Igarashi <tm.igara...@gmail.com> wrote: > Hi, > > Wasn't asciidoctor-maven-plugin an option? We're using it to generate > AtlasMap developer guide on each master build. > https://github.com/atlasmap/atlasmap/blob/dc9cceb7e7438b88e5d761b636f2f31f4d5c36ff/docs/pom.xml#L50-L71 > https://docs.atlasmap.io/ > > Thanks, > Tomo > > On Wed, 2018-04-25 at 21:55 +0200, Zoran Regvart wrote: >> Hi Cameleers, >> >> On Wed, Apr 25, 2018 at 8:33 PM, Claus Ibsen <claus.ib...@gmail.com> wrote: >> > We are using ascii doc but it should be similar. >> >> Just to chime in, because we use asciidoc, and just to be sure I'm not >> questioning that decision it's clearly superior choice vs markdown, >> the current stack we have on the website branch takes a really long >> time to build. Hugo static site generator has no direct support for >> asciidoc so we need to spin up a new process for each asciidoc file >> and this is quite resource intensive. >> >> An alternative was suggested in CAMEL-11499[1] to try using jbake, and >> I think I will give it a shot in the coming days... >> >> zoran >> >> [1] >> https://issues.apache.org/jira/browse/CAMEL-11499?focusedCommentId=16346954 -- Zoran Regvart
