> For the purpose of producing my own documentation to use as a user, I took > the antlr grammar for Accord CQL and used a model to generate a few dozen > examples of what's possible and not possible in the syntax. I'd love for > something like this to be included in the Accord section.
PR open from before I went on leave. Believe all feedback has been addressed just waiting for approval. Know docs don’t need 2 reviews, just want to make sure the docs are good for users. PR is very example focused, shows limitations and work around! As with the giant over hall. I’m good with the approach. Patric and I were talking about the doc build process when I first sent out the accord PR, my hope is the output of this effort makes it easier to contribute / validate than current trunk Sent from my iPhone > On Apr 3, 2026, at 2:03 PM, Mick <[email protected]> wrote: > > >> >> 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 th… > > > > My concern here is that you're putting the cart before the horse – you can't > commit any of the new docs until you can build them the way they get built > for the website. So, I guess, you have to be extra clear with folk that > phase 1 is only content and layout review, and that those things may change > and need to be reviewed again after phase 2. when the build is fixed/adapted. > Take for example Scott's mention about rendering latex, that's moot because > it can and will change again. > > If phase 1 is what you need as the driving force for motivation and to bring > in collaboration, that's fine by me, just so long as everyone understands the > above. >
