Developer Documentation is the technical home for Kaya. It documents how the application currently works so developers can onboard, make safe changes and keep future work aligned with the existing system.

What is covered

Versioning

Each page uses the MDX version frontmatter field. The current docs use current until Kaya documentation is tied to a specific released version.

When Kaya ships a versioned release, developer documentation should be updated in the same change set and the relevant version fields should be kept aligned with the Kaya release being documented.

Future automation

The structure is intentionally modular so future Codex-assisted workflows can scan the Kaya repository, identify changed modules, update only the relevant MDX pages and present those changes for review before publication.