Services / Antora
I build, migrate and maintain documentation sites using static site generators, and can analyse which is the best fit for your documentation needs. These sites are built from static files, generated using AsciiDoc or Markdown. This way they load fast and are cheap to host, with no need to worry about complex software.
After I'm done, you will have a build system that any developer or engineer can run themselves.
Antora can publish several product versions side by side, and your site can include a switcher so readers can choose the docs that match their version. Each version lives in its own Git branch, and can be added from the Antora playbook:
content:
sources:
- url: https://example.com/your-org/docs.git
branches: [main, v2.0]
I became familiar with this at GraphAware, which is also where I first learned Antora.
At Kaptio, I used Antora to build a new public-facing documentation site. I wrote the playbook, which pulled from four repositories, including the landing page, release notes and metadata, bringing them together for one site. It also used Lunr for search. My manager and I updated the UI, with input from marketing, and the company's System Architect handled the final deployment step.
In the end we created an easily navigated static documentation site, built automatically from Git. You can read more about the pipeline behind it here.
No matter the tool, the result is a clear, navigable website. The landing page and content are wrapped in a UI that fits your brand design, and the site is fast, lightweight and responsive.
Related: Docs-as-code CI/CD pipelines · Confluence to AsciiDoc migration