We've heard positive feedback about VillageSQL's documentation, so we wanted to share a bit more on how we build it and how we hope to evolve it. VillageSQL Server tracks upstream MySQL and adds an extension framework, so the documentation has two moving targets. We pull in upstream changes with each MySQL release, and VillageSQL's own changes land daily in the dev branch and ship with each release. We believe that it's important for a complex project to provide accurate documentation that is updated as frequently as code ships. This is easier said than done. We use AI extensively to generate our docs, but we believe it's critical to have a human as a review gate before any change is shipped. AI makes mistakes, so we make it prove every change to itself and to humans by testing against a running server.
Frequent readers of the VillageSQL docs will also notice a recent redesign. The …
[Read more]