Ask HN: What do you use to write your tech docs?
I&#x27;ve used a bunch of Wikis:
GitLab Wiki (pretty awful), 
GitHub Wiki (same),
Confluence (capable, but tedious),
Moinmoin (crufty), and
MediaWiki (kinda over the top).<p>Confluence&#x27;s export to PDF is kinda useful: we were able to maintain manuals that looked acceptable using it.<p>Other than Wikis, I&#x27;ve used: Texinfo (it has a &quot;look&quot;, but is pretty capable), LaTeX,  troff (and nroff), ReST &#x2F; Sphinx (clunky, but the end result is ok), DocBook and FOP (for structured docs), Framemaker, Word, and Google Docs.<p>Things I&#x27;d consider when making a choice are the skillset of the authors and editors; the balance between text and not-text (figures, photos, videos, whatever) in the content; the required output (PDF? HTML? man pages? Windows help?); and the toolset support (eg. useful diff and merge tools).<p>If I had to choose today, I&#x27;d probably go with Confluence (largely because the plugin ecosystem is just so much bigger&#x2F;better than any of the other Wikis I&#x27;ve used) for internal or knowledge-base type things, and maybe Sphinx&#x2F;ReST for more complex published documents, although I&#x27;d likely have a look at AsciiDoc or something else in that sort of space too.  For a seriously large documentation project, I&#x27;d possibly still build a DocBook-based workflow.