<html><head><meta http-equiv="Content-Type" content="text/html charset=us-ascii"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><br class=""><div><div class="">On Jul 25, 2016, at 1:40 PM, James Perkins <<a href="mailto:jperkins@redhat.com" class="">jperkins@redhat.com</a>> wrote:</div><blockquote type="cite" class=""><div class=""></div></blockquote><div class=""><div class="gmail_extra"><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr" class=""><div class="">Anyway, I'm up for anything that allows the documentation to be consistent, easy to write and easy to use. The main attraction for me to asciidoc is being able to use git for versioning as well as being able to use variables. I don't however know how well asciidoc deals with multiple documents and combining them together.</div></div></blockquote></div></div></div></div><br class=""><div class="">This has probably already been mentioned somewhere in this thread, but a related advantage to an asciidoc (or similar) approach using git, is that you can more easily take documentation contributions in the form of pull requests. I often find myself wanting to suggest a revision, especially after figuring out how to do something that wasn't clearly explained, but apart from adding comments to the page (which are difficult to put in context), there is no good way to suggest revisions in Confluence.</div><div class=""><br class=""></div><div class="">carl</div></body></html>