+1 for moving to...something. I have very limited familiarity with documentation frameworks, but I'm wondering if something in the line of Mark Down would be possible, and if there's a good parser for turning that into web pages? My thought here is that Mark Down seems to provide both parseable functionality for building into rich text experiences (like HTML), but also maintains good readability from a command line or text editor, making it possible to distribute the manual in multiple formats.
Having said that, and looking at documentation for both asciidoc and RST, it looks like those languages have the same rough goals and features as Mark Down, so I've no strong preference one way or the other. -Nick On Tue, Apr 20, 2021 at 7:08 PM carl harris <[email protected]> wrote: > I've used asciidoc and RestructedText (RST) on two different large > document projects. I kinda prefer the RST toolchain, and I find the > plaintext presentation of RST a little more agreeable, but really either of > them would be good choices to move away from docbook. > > — > carl > > > On Apr 20, 2021, at 6:20 PM, Mike Jumper <[email protected]> wrote: > > > > I've been thinking recently that the current guacamole-manual is not > very > > approachable with respect to contributions, and that members of the > > community that might want to contribute to the manual may be turned off > by > > the complexity/unfamiliarity of DocBook and XML. It'd be nice if > improving > > the manual were as simple as editing a text document. > > > > Thoughts? Asciidoc seems a common alternative that is compatible with > > DocBook. > > > > - Mike >
