[wildfly-dev] One Doc to Rule Them All

James Perkins jperkins at redhat.com
Fri May 13 12:00:43 EDT 2016

On Fri, May 13, 2016 at 6:12 AM, David M. Lloyd <david.lloyd at redhat.com>

> I like approach 3, assuming that it'll move in to e.g. GitHub.  If
> there's an update to a doc, it's a lot easier to backport using git than
> Confluence.  Less chance of old docs getting abandoned, and easier for
> users to contribute fixes and updates if they can just open a PR for
> each affected version.  We're already reasonably well-trained to deal
> with old branches.
> I don't know how we'd organize it though; I've never done multi-document
> things using asciidoc, and also we'd have to publish it somehow
> (preferably in an automated manner).

Actually it does look like there is an include:: option. My guess though is
the reason there's a lot of combining asciidoc with awestruct is to build
these multi-page sites.

[1]: http://www.methods.co.nz/asciidoc/userguide.html#X63

> --
> - DML
> _______________________________________________
> wildfly-dev mailing list
> wildfly-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/wildfly-dev

James R. Perkins
JBoss by Red Hat
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/wildfly-dev/attachments/20160513/60b79dd7/attachment.html 

More information about the wildfly-dev mailing list