I've been spending a bunch of evenings migrating to a new documentation system for OliveTin - #antora, fixing dead links, improving formatting, and overall design of the docs: https://docs.olivetin.app/ #opensource #selfhosted #homelab
heise+ | Softwareprojekte konsistent mit #Antora dokumentieren | iX Magazin https://www.heise.de/ratgeber/Softwareprojekte-konsistent-mit-Antora-dokumentieren-9992034.html #heiseplus #asciidoc
Just in case someone with some #Antora #AsciiDoc and maybe #PlantUML experience is around: I've a question: https://github.com/madmas/demo-antora-doc-A/issues/1 #plsretoot #retoot
For years I've been a big fan of #Asciidoc; I've used it for presentations, documentation, and training materials. #Markdown is usually fine for simpler use cases, but after working on the #JakartaEE tutorial with Asciidoc and #Antora, writing a README in Markdown is painful...
@AstridSawatzky The IntelliJ AsciiDoc Plugin by @ahus1 can be configured to use custom stylesheets for the preview pane, so you see exactly what your output will look like:
https://intellij-asciidoc-plugin.ahus1.de
If you use https://antora.org, you can even point to the stylesheets from your custom #Antora UI.
@meansofescape
Well, free software is most affordable, so how about, e.g., writing your sources in #Markdown? Conversion to PDF (or anything else) can be done by one of the many free tools, https://github.com/jmaupetit/md2pdf, #Pandoc, ...
Or this: I'm currently investigating #antora - pretty cool framework built around #AsciiDoc.
Guess I'm biased toward software documentation and docs-as-code, though. 
dear #documentation people: Is there a way in #Antora to keep #AsciiDoc and images together. I would like to have a subdir per page and in there a 'image' subdir containing only the images for that page
Random smattering of interests for newcomers:
