Features

I’ve worked on more than half-a-dozen AsciiDoc-based docs-suites. And every one of them has also been an Antora project. And exactly none of the companies that I’ve worked with on these AsciiDoc-based docs is interested in switching away from an Antora-based build chain. Which makes adoc-studio a non-starter for their technical writers. By support I don’t automatically mean full-blown Antora playbook support. But the ability to parse an AsciiDoc project that will be built by Antora and present said project for editing and previewing within adoc-studio. That is for adoc-studio to understand the Antora-specific directory structure, < https://docs.antora.org/antora/latest/organize-content-files/ >; understand Antora’s notions of components and modules; and be able to preview not just individual pages, but the project.

An addition to tables

General content and formatting attribute

Do you have plans to support epub export?

For GitHub, GitLab and locally hosted Git repositories. This is not only important for the obvious reasons. There are users who build their accounting on Git checkins. Additionally; it would boost the iPad version as there is no good Git client available (including Working Copy) (Added from an email from a tester)

If you search in ‘All documents’ with at least 100 hits, scroll down in the results to the centre and select the entry in the middle. The search jumps to the first entry and not the one in the middle.

Convert AsciiDoc into graphs: https://kroki.io

Divide content into different tabs. That way, content is grouped and only relevant information gets displayed. Examples: View different code blocks in the same location (switch tabs to view the code blocks in a different programming language). Here’s an image and further information: https://docs-as-co.de/news/tabs-asciidoc/ For Installation Guides, choose the right operating system and only display content for that specific OS. Currently AsciiDoc requires a plugin for tabs: https://stackoverflow.com/questions/38211766/using-tabs-in-asciidoc-spring-rest-docs

And store the checked value in the text.

An alternative style to <<