This afternoon/evening some colleagues at RH hosted an internal tech
meetup, where we talked through projects and tech issues. I brought up
the need to author SSG guides in a cross-platform, multi-author format
and Gunnar Hellekson [1] suggested the following (thanks, Gunnar!):
First, you should all be grokking [markdown].
Second, take a look at the truly great [AsciiDoc], which is richer than markdown, and
designed to make creating DocBook (our chosen source format for documentation) much
easier.
Third, you can make them both super-useful with [pandoc], available in your local yum
repo.
[
Markdown]:http://daringfireball.net/projects/markdown/
[
AsciiDoc]:http://asciidoctor.org/
[
pandoc]:http://johnmacfarlane.net/pandoc/
The ability to transform content into multiple final outputs is
incredibly interesting. Has anyone played with these techs, either
individually or as part of some larger workflow?
Perhaps these could lay the foundation for authoring/updating the
workbooks, and could prove to be a great way to contribute for those who
aren't interested in writing OVAL code.
[1] His blog is pretty interesting,
http://atechnologyjobisnoexcuse.com/. Note his podcast mention SSG in
almost every episode!