Hi Chris, Thanks for sharing — Antora looks like a very interesting tool for building document sites.
Currently, we’re using docusaurus(https://docusaurus.io), for the BifroMQ website: https://github.com/apache/bifromq-sites. It’s working well for our current needs, but Antora's multi-component and multi-branch model looks promising for BifroMQ's future side projects/components portals. For improvement proposals, I think a collaborative tool with versioning support(like CWiki) might be more convenient. Thanks again for the insight! Best, On Wed, Jul 16, 2025 at 8:46 PM Christofer Dutz <[email protected]> wrote: > Hi all, > > in the Apache PLC4X project we just recently switched from a pure > Maven+AsciiDoc approach to using Antora:https://antora.org/ > https://github.com/apache/plc4x/tree/develop/website > > The cool thing is that you can have it produce and maintain the website > over multiple banches. > > Chris > > > Von: Yonny Hao <[email protected]> > Datum: Mittwoch, 16. Juli 2025 um 11:54 > An: [email protected] <[email protected]> > Betreff: [DISCUSS] Tooling for Managing BifroMQ Technical Documentation > and Improvement Proposals > Dear all, > > As BifroMQ continues to grow, I’d like to initiate a discussion on which > tooling we should adopt for managing our technical documentation, > particularly community-driven improvement proposals. I have already > requested the ASF Infra team to provision an Apache CWiki space for > BifroMQ. CWiki offers good support for collaboration and versioning, which > I believe are helpful for our use cases. However, an alternative would be > to simply use GitHub Wiki. Personally, I lean toward using *CWiki*, > especially for collaboratively authoring and tracking improvement proposals > over time. But I’d love to hear what others think. > > Please share your thoughts. This thread will remain open for *48 hours* to > collect feedback from all committers. > > Best regards, > -- > Yonny(Yu) Hao > -- Yonny(Yu) Hao
