The calculus of this decision seems different when it comes to the documentation portions of the site (e.g., the end user documentation and developer documentation) vs the regular content (e.g., the blog, changelogs, and other static content). I think there may be a sweet spot in using Antora for the end user documentation and developer documentation while using another tool for the blog, changelogs, and other static content.
For the documentation portions of the site, Antora seems like a perfect fit because it is specifically designed for documentation sites and features first-class support for branching/versioning documentation for multiple releases, combining multiple repositories into a single site, etc. There has been a real need for versioned documentation for multiple releases when working on e.g. Java Platform support and other projects. I imagine the long-term maintenance cost of Antora for the documentation portions of the site would be low: just keeping the build running and keeping the templates up-to-date. In contrast it seems that more effort would be required to use e.g. Gatsby for a versioned/branched documentation site. Even with e.g. the Rocketseat docs theme as a source of inspiration, it seems that Gatsby offers less support for the versioned documentation use case out-of-the-box and that custom code would need to be written and then maintained in order to fully accommodate the versioned documentation use case. In contrast, Antora was not designed for blogs, and Antora issue #444 makes it clear that the maintainers do not intend to support blog-like functionality in Antora. Using Antora for anything other than a documentation site seems ill-advised, as this is not Antora's intended use case. While it might be possible to use e.g. Gatsby for everything (including the blog and documentation portions of the site), my sense is that the benefits of using Antora for the documentation portions of the site (both from an initial development and maintenance perspective) may be more compelling. -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-dev+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CAFwNDjqHDVdiwDTLiUAEtYF-3Pw4mb_Go9JDg2Ts%2B5LG%3DW7yPQ%40mail.gmail.com.
