📄️ Contributing
This page is a practical checklist for making changes to SydraDB without fighting the toolchain.
📄️ CI and releases
SydraDB uses GitHub Actions for:
📄️ Documentation site
This repository’s documentation site is a Docusaurus project rooted at docs/.
📄️ Docusaurus toolbox (site improvements)
This page is a practical checklist of Docusaurus “batteries included” features we can use to keep SydraDB docs navigable, searchable, and easy to maintain.
📄️ Documentation coverage plan
This document is a concrete plan for maintaining a documentation site with maximum coverage of SydraDB’s repository contents, with a bias toward:
📄️ sydraQL backlog (snapshot)
This page captures a small, curated backlog for sydraQL work. It originated as a CSV export and is kept here as a linkable, searchable checklist.
📄️ sydraQL readiness checklist
This page is a lightweight checklist used by the sydraQL roadmap to track “ship readiness” gates.
📄️ Zig 0.15.x Migration Checklist
This plan captures every known change required to move the codebase and tooling from Zig 0.14.x to Zig 0.15.x. Work through the sections in order; each bullet calls out the exact files and symbols to touch so we can execute without additional clarification.
📄️ sydraQL Engineering Roadmap
This roadmap translates the sydraQL language vision into a sequenced engineering plan. It assumes the repository is already migrated to Zig 0.15 and that the storage, WAL, and HTTP layers match the current main branch. Each phase lists goals, scope boundaries, detailed work items, interfaces, artefacts, validation gates, and fallback considerations. Milestones are intentionally granular so we can parallelise efforts while keeping tight feedback loops.