<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Asciidoc on Backend Engineering Strategy Tools</title><link>https://backend-engineering-strategy-tools.github.io/site/tags/asciidoc/</link><description>Recent content in Asciidoc on Backend Engineering Strategy Tools</description><generator>Hugo -- gohugo.io</generator><language>en-us</language><lastBuildDate>Thu, 04 Jun 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://backend-engineering-strategy-tools.github.io/site/tags/asciidoc/index.xml" rel="self" type="application/rss+xml"/><item><title>Document Tools — Pandoc, LaTeX, Typst, AsciiDoc, Sphinx</title><link>https://backend-engineering-strategy-tools.github.io/site/public-notes/docs-as-code/adjacent/</link><pubDate>Thu, 04 Jun 2026 00:00:00 +0000</pubDate><guid>https://backend-engineering-strategy-tools.github.io/site/public-notes/docs-as-code/adjacent/</guid><description>&lt;p&gt;Tools adjacent to the Markdown/Hugo docs-as-code workflow — format conversion, typesetting, heavier markup languages, and documentation generators.&lt;/p&gt;
&lt;h2 id="pandoc"&gt;Pandoc
&lt;/h2&gt;&lt;p&gt;The universal document converter. Pandoc reads and writes dozens of formats: Markdown, HTML, DOCX, EPUB, LaTeX, RST, AsciiDoc, and more. The most common use in a docs-as-code workflow is converting Markdown to PDF (via LaTeX), to DOCX for stakeholders who need Word files, or to self-contained HTML for offline distribution. A single source in Markdown, multiple output formats on demand. Docker images make it easy to run without a local install — the full LaTeX stack is large but containable.&lt;/p&gt;
&lt;h2 id="latex"&gt;LaTeX
&lt;/h2&gt;&lt;p&gt;A typesetting system built for precision output — academic papers, technical documentation, books. LaTeX gives exact control over typography, equations, cross-references, and bibliography. The source is plain text markup that compiles to PDF. Steep learning curve, verbose syntax, but the output quality for complex documents (especially anything with mathematical notation) is unmatched. Pandoc uses LaTeX as the intermediate format when generating PDFs, so you often interact with LaTeX indirectly through a Pandoc pipeline rather than writing &lt;code&gt;.tex&lt;/code&gt; directly.&lt;/p&gt;
&lt;h2 id="typst"&gt;Typst
&lt;/h2&gt;&lt;p&gt;A newer alternative to LaTeX with a friendlier syntax and faster compilation. Typst is designed from scratch for the same use case — precise typeset documents, scientific papers, equations — but the markup is more readable and the error messages are useful. Still maturing but gaining traction as a LaTeX replacement for teams starting fresh. Compiles to PDF directly; no intermediate format.&lt;/p&gt;
&lt;h2 id="asciidoc"&gt;AsciiDoc
&lt;/h2&gt;&lt;p&gt;A markup language heavier than Markdown but lighter than LaTeX, designed specifically for technical documentation. AsciiDoc supports cross-references, admonitions (NOTE, WARNING, TIP blocks), includes (assembling a document from multiple source files), and detailed table and image control — things Markdown handles awkwardly or not at all. Asciidoctor is the primary processor (Ruby, with a Java port). Used heavily by Red Hat, the O&amp;rsquo;Reilly book toolchain, and projects that need a single-source publishing pipeline for both web and print output.&lt;/p&gt;
&lt;h2 id="sphinx"&gt;Sphinx
&lt;/h2&gt;&lt;p&gt;A documentation generator from the Python ecosystem, originally built for the Python language documentation. Sphinx reads reStructuredText (RST) or Markdown source and produces HTML sites, PDF (via LaTeX), and ePub. The key feature is its cross-referencing system — links between pages, auto-generated API docs from docstrings, and an index are all first-class. The &lt;code&gt;Read the Docs&lt;/code&gt; hosting platform is built around Sphinx. Common outside Python too for any project that wants a structured documentation site with strong cross-referencing.&lt;/p&gt;
&lt;h2 id="resources"&gt;Resources
&lt;/h2&gt;&lt;ul&gt;
&lt;li&gt;&lt;a class="link" href="https://pandoc.org/MANUAL.html" target="_blank" rel="noopener"
 &gt;Pandoc documentation&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a class="link" href="https://hub.docker.com/r/pandoc/latex" target="_blank" rel="noopener"
 &gt;Pandoc Docker image&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a class="link" href="https://www.latex-project.org/" target="_blank" rel="noopener"
 &gt;LaTeX project&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a class="link" href="https://typst.app/docs/" target="_blank" rel="noopener"
 &gt;Typst documentation&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a class="link" href="https://docs.asciidoctor.org/" target="_blank" rel="noopener"
 &gt;AsciiDoc / Asciidoctor documentation&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a class="link" href="https://www.sphinx-doc.org/" target="_blank" rel="noopener"
 &gt;Sphinx documentation&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;</description></item></channel></rss>