Example projects using DocBook for documentation: OpenStack Documentation: http://docs.openstack.org/
DAPS (OpenSuse): http://opensuse.github.io/daps/doc/index.html PHP Documentation: http://php.net/manual/en/ Eclipse Jetty: http://www.eclipse.org/jetty/documentation/ XÖV-STANDARDS UND -VORHABEN: http://www.xoev.de/sixcms/detail.php?gsid=bremen83.c.11430.de 2015-09-11 18:56 GMT+02:00 Katie Welles <[email protected]>: > It’s been a while since I’ve used Docbook or participated in this forum. > > I used Docbook a number of years ago to put together a web-based API > reference system. To be frank, I found it to be a pretty painful project, > but mainly because I thought it was downright foolish to jump through all > those Docbook hoops just to output simple HTML. It seems to me that the > power of Docbook is when your single XML source is used for multiple > outputs. > > I support a consortium that manages 12+ open APIs, and we’ve been > re-examining the tools we use to output published specs. We know we want > **all** our API specs to be available as PDF and also HTML, but are not > sure which tool to bank on. So far we’ve been looking at asciidoc, which I > find pretty underwhelming. > > Have any of you PDF + HTML output with Docbook? If anyone has such a > project and will be willing to show it off, send some URLs! > > As an aside: Have any of you used asciidoc? > > (BTW — I use MadCap Flare for another of my clients. The output is > stunningly beautiful, but the tool is far too unwieldy and expensive for me > to be able to recommend it to my API client.) > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
