You are pointing out several things that lead me to creating this work repo like I did.
The phasing in my mind was start with the content and then phase 2, core build and deployment changes. For the users of Cassandra, my initial big lift was giving them first class docs(and are they?) The items you mentioned are when I start moving things over to trunk, and yes, there will be a lot of things to get through there. My hope is we can retire some tech debt along the way and make it easier to contribute changes. Different set of ideas there but on my mind. On Fri, Apr 3, 2026 at 11:53 AM Mick <[email protected]> wrote: > > > If someone's active, wants to do it, and there's enough people who agree > with them (and nobody actively protesting), we should let things progress. > > > > Yes, I'm actively protesting :-) but not out of principle, out of > pragmatism. It has to work, currently I am unsure how it can. My > objection is avoiding us progressing down rabbit holes we later regret. > > Trying to be helpful… some questions to get going… > What version of antora are you using (we are currently stuck on 2.3) ? > How are the auto-generated configuration and nodetool pages included ? Is > the in-docs search still working ? are you using the cassandra-website > ui-bundle ? are you including the current djencks/asciidoctor-openblock > hack ? > > > Probably the simplest test of feasibility is to get the following (from > cassandra-website) working: > > ./run.sh website build -g -u cassandra: > https://github.com/pmcfadin/cassandra.git -b > cassandra:cassandra6-docs-workzone > > > This can be done in parallel, but I don't believe should wait (because > there could be functionality this depends on that simply won't work), and I > will help out.
