home.social

#antora — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #antora, aggregated by home.social.

fetched live
  1. We've updated our docs website to be based on Antora and is now published here! :cockpit:

    This has the added benefit of showing us docs for different versions and allows us to be more flexible.

    docs.cockpit-project.org/cockp

    #asciidoc #antora

  2. We've updated our docs website to be based on Antora and is now published here! :cockpit:

    This has the added benefit of showing us docs for different versions and allows us to be more flexible.

    docs.cockpit-project.org/cockp

  3. We've updated our docs website to be based on Antora and is now published here! :cockpit:

    This has the added benefit of showing us docs for different versions and allows us to be more flexible.

    docs.cockpit-project.org/cockp

    #asciidoc #antora

  4. We've updated our docs website to be based on Antora and is now published here! :cockpit:

    This has the added benefit of showing us docs for different versions and allows us to be more flexible.

    docs.cockpit-project.org/cockp

    #asciidoc #antora

  5. We've updated our docs website to be based on Antora and is now published here! :cockpit:

    This has the added benefit of showing us docs for different versions and allows us to be more flexible.

    docs.cockpit-project.org/cockp

    #asciidoc #antora

  6. has anyone gotten #Antora with #asciidoctor #bibtex to work? I would really love to use Antora as a front end for some kind of paper with lots of citations.

    All I get is an error about #opaque in #npm I cannot get fixed.

  7. has anyone gotten #Antora with #asciidoctor #bibtex to work? I would really love to use Antora as a front end for some kind of paper with lots of citations.

    All I get is an error about #opaque in #npm I cannot get fixed.

  8. ✨️ New blog post: "STF Milestone 10: Documentation improvements"

    Modernizing #JUnit's documentation by adopting #Antora and hosting on @statichost

    👉️ marcphilipp.de/blog/2026/01/25

    Thanks to the @sovtechfund for their support!

  9. ✨️ New blog post: "STF Milestone 10: Documentation improvements"

    Modernizing #JUnit's documentation by adopting #Antora and hosting on @statichost

    👉️ marcphilipp.de/blog/2026/01/25

    Thanks to the @sovtechfund for their support!

  10. ✨️ New blog post: "STF Milestone 10: Documentation improvements"

    Modernizing #JUnit's documentation by adopting #Antora and hosting on @statichost

    👉️ marcphilipp.de/blog/2026/01/25

    Thanks to the @sovtechfund for their support!

  11. ✨️ New blog post: "STF Milestone 10: Documentation improvements"

    Modernizing #JUnit's documentation by adopting #Antora and hosting on @statichost

    👉️ marcphilipp.de/blog/2026/01/25

    Thanks to the @sovtechfund for their support!

  12. ✨️ New blog post: "STF Milestone 10: Documentation improvements"

    Modernizing #JUnit's documentation by adopting #Antora and hosting on @statichost

    👉️ marcphilipp.de/blog/2026/01/25

    Thanks to the @sovtechfund for their support!

  13. I'm going to have to write my own #AsciiDoctor-based static site generator, right?

    I still haven't found anything that fits my use case, coming from #ikiwiki, which I want to leave because it's slow, written in Perl (not my favorite language) and doesn't integrate well with AsciiDoctor.

    #Antora manages to both be overengineered for my use case *and* miss essential features like feed generation. Also node.js, no thanks

    1/2

    #SSG

  14. I'm going to have to write my own #AsciiDoctor-based static site generator, right?

    I still haven't found anything that fits my use case, coming from #ikiwiki, which I want to leave because it's slow, written in Perl (not my favorite language) and doesn't integrate well with AsciiDoctor.

    #Antora manages to both be overengineered for my use case *and* miss essential features like feed generation. Also node.js, no thanks

    1/2

    #SSG

  15. I'm going to have to write my own #AsciiDoctor-based static site generator, right?

    I still haven't found anything that fits my use case, coming from #ikiwiki, which I want to leave because it's slow, written in Perl (not my favorite language) and doesn't integrate well with AsciiDoctor.

    #Antora manages to both be overengineered for my use case *and* miss essential features like feed generation. Also node.js, no thanks

    1/2

    #SSG

  16. I'm going to have to write my own #AsciiDoctor-based static site generator, right?

    I still haven't found anything that fits my use case, coming from #ikiwiki, which I want to leave because it's slow, written in Perl (not my favorite language) and doesn't integrate well with AsciiDoctor.

    #Antora manages to both be overengineered for my use case *and* miss essential features like feed generation. Also node.js, no thanks

    1/2

    #SSG

  17. I'm going to have to write my own #AsciiDoctor-based static site generator, right?

    I still haven't found anything that fits my use case, coming from #ikiwiki, which I want to leave because it's slow, written in Perl (not my favorite language) and doesn't integrate well with AsciiDoctor.

    #Antora manages to both be overengineered for my use case *and* miss essential features like feed generation. Also node.js, no thanks

    1/2

    #SSG

  18. Coming from #MkDocs on #ReadTheDocs , I think about migrating our projects user manual to #Asciidoc using #asciidoctor and/or #antora .

    But I wonder if there is a service like #readthedocs for #asciidoc based manuals available for #OpenSource or #foss projects.

    Important is that those platforms do support @Codeberg (#forgejo aka #gita ) code hosting, instead of Microsoft GitHub.

  19. Coming from on , I think about migrating our projects user manual to using and/or .

    But I wonder if there is a service like for based manuals available for or projects.

    Important is that those platforms do support @Codeberg (#forgejo aka ) code hosting, instead of Microsoft GitHub.

  20. Coming from #MkDocs on #ReadTheDocs , I think about migrating our projects user manual to #Asciidoc using #asciidoctor and/or #antora .

    But I wonder if there is a service like #readthedocs for #asciidoc based manuals available for #OpenSource or #foss projects.

    Important is that those platforms do support @Codeberg (#forgejo aka #gita ) code hosting, instead of Microsoft GitHub.

  21. Coming from #MkDocs on #ReadTheDocs , I think about migrating our projects user manual to #Asciidoc using #asciidoctor and/or #antora .

    But I wonder if there is a service like #readthedocs for #asciidoc based manuals available for #OpenSource or #foss projects.

    Important is that those platforms do support @Codeberg (#forgejo aka #gita ) code hosting, instead of Microsoft GitHub.

  22. Coming from #MkDocs on #ReadTheDocs , I think about migrating our projects user manual to #Asciidoc using #asciidoctor and/or #antora .

    But I wonder if there is a service like #readthedocs for #asciidoc based manuals available for #OpenSource or #foss projects.

    Important is that those platforms do support @Codeberg (#forgejo aka #gita ) code hosting, instead of Microsoft GitHub.

  23. Switching to Antora for the OliveTin docs was the best thing ever for the docs. Now just added support for doc tabs with a simple extension :-) #asciidoc #antora thanks Dan Allen!

  24. Switching to Antora for the OliveTin docs was the best thing ever for the docs. Now just added support for doc tabs with a simple extension :-) #asciidoc #antora thanks Dan Allen!

  25. Switching to Antora for the OliveTin docs was the best thing ever for the docs. Now just added support for doc tabs with a simple extension :-) #asciidoc #antora thanks Dan Allen!

  26. 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: docs.olivetin.app/ #opensource #selfhosted #homelab

  27. 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: docs.olivetin.app/ #opensource #selfhosted #homelab

  28. 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: docs.olivetin.app/ #opensource #selfhosted #homelab

  29. 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: docs.olivetin.app/ #opensource #selfhosted #homelab

  30. 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: docs.olivetin.app/ #opensource #selfhosted #homelab

  31. Installing Antora in a Podman container for Pi server provisioned with Fedora IoT. I aim to set up my personal Docs site, also proof of concept for my work project.

    Next step is to configure Antora Playbook and site properties.

    #docs #antora #Podman #iot

    @fedora

  32. Installing Antora in a Podman container for Pi server provisioned with Fedora IoT. I aim to set up my personal Docs site, also proof of concept for my work project.

    Next step is to configure Antora Playbook and site properties.

    #docs #antora #Podman #iot

    @fedora

  33. Installing Antora in a Podman container for Pi server provisioned with Fedora IoT. I aim to set up my personal Docs site, also proof of concept for my work project.

    Next step is to configure Antora Playbook and site properties.

    #docs #antora #Podman #iot

    @fedora

  34. Installing Antora in a Podman container for Pi server provisioned with Fedora IoT. I aim to set up my personal Docs site, also proof of concept for my work project.

    Next step is to configure Antora Playbook and site properties.

    #docs #antora #Podman #iot

    @fedora

  35. @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:

    intellij-asciidoc-plugin.ahus1

    If you use antora.org, you can even point to the stylesheets from your custom #Antora UI.

    #AsciiDoc #IntelliJ

  36. @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:

    intellij-asciidoc-plugin.ahus1

    If you use antora.org, you can even point to the stylesheets from your custom #Antora UI.

    #AsciiDoc #IntelliJ

  37. @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:

    intellij-asciidoc-plugin.ahus1

    If you use antora.org, you can even point to the stylesheets from your custom #Antora UI.

    #AsciiDoc #IntelliJ

  38. @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:

    intellij-asciidoc-plugin.ahus1

    If you use antora.org, you can even point to the stylesheets from your custom #Antora UI.

    #AsciiDoc #IntelliJ

  39. @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:

    intellij-asciidoc-plugin.ahus1

    If you use antora.org, you can even point to the stylesheets from your custom #Antora UI.

    #AsciiDoc #IntelliJ

  40. OPS4J Documentation is moving from Confluence to Git. Initial setup is done: ops4j.github.io

    #OPS4J #AsciiDoc #Antora #GitHub

  41. OPS4J Documentation is moving from Confluence to Git. Initial setup is done: ops4j.github.io

  42. @dgarcia360
    We have several toolchains for several products, but the latest decision was
    #antora (ie. AsciiDoc) with "default" search engine lunr.js and additionally po4a to manage translations.
    Speaking of which: The support for multi-language documentation seems not very popular around the SSG community. Same for offline usage. Our products have both these requirements and we struggle quite a bit to find anything decent.

  43. I fixed the thing! The work thing, I fixed it. At, like, 18:30 of a Friday evening. Happy Sant Joan to all in Catalonia, and happy weekend to everyone else.
    #antora #santjoan2023

  44. @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, 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. 😉

  45. @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, 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. 😉

  46. @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, 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. 😉

  47. @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, 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. 😉