About the Project

Project meta: where the release history lives, how upgrades work, where the project is going, how to contribute, and the licensing/support picture.

In this section

Changelog: every tagged release, newest first, from the project’s GitHub releases with their own per-release notes.
Upgrades & Migrations: the two real upgrade paths (the deploy script; signed offline bundles) and how the 62-file migration corpus keeps schema.sql and live databases in sync.
Roadmap: what’s planned across forms maturity, SEO discovery, and access control, and what isn’t promised yet.
Contributing: the contribution process for the core repository.
License: MIT for the core.
Support: where to get help and what’s expected.

MIT core: use, modify, self-host, sell services on it; keep the notice intact in distributed copies.
Roadmap says “planned” honestly: nothing listed there is promised or dated; anything not yet merged stays listed as intent, not shipped.
Documentation is the product’s own: these pages are generated from verified audits of the source; when docs and code disagree, the code is the fact and the docs get corrected.

Every tagged Chinaski release, newest first, with dates, what was added or fixed in each, and links to the full changelog diffs.

How Chinaski's schema and code move forward: the 62 numbered SQL migrations, the on-line deploy script, and the air-gapped signed-bundle script.

The improvements planned for Chinaski, grouped by the pillars they serve, starting with forms: what exists today and what is only a proposal.

Contribute to Chinaski, which is MIT-licensed: what to do before you start, local setup, running the tests, and the project's conventions.

Read Chinaski's license: the MIT core, what you may do with it, the conditions that come with it, and the stated direction for commercial add-ons.

Get help with Chinaski: best-effort support by email at help@chinaski.net, where bugs and feature requests go, and what to check first.