Public documentation home for Keyboard Studio,
the browser-based studio that lets language experts create production-ready
Keyman keyboards through a plain-language survey and
show-by-example galleries — no hand-written .kmn.
Site: https://keyboard-studio.github.io/docs/
- What to Expect — the visitor-facing companion, written for keyboard authors in plain language: what making a keyboard feels like today, what is still rough, and what is on its way. Drawn from the project's own user stories in its completed specifications.
- The Trailmap — a living map of the project for developers, modelled on the FWLite Trailmap: what has been accomplished, what is being worked on now, known issues, and what is to come, organised as camps along one trail. It is deliberately not user documentation — the product is too early and too fluid for that; the Trailmap is the public-facing record of the project's state until the ground settles.
The Trailmap is a snapshot, dated on the page, refreshed from the main repository (issues, pull requests, specs) as the project moves. Every item on it links back to its GitHub original.
- App: https://keyboard-studio.github.io/keyboard-studio/
- Source, specs and issues: https://github.com/keyboard-studio/keyboard-studio
Deep contributor documentation (architecture, the criteria catalog, tooling,
workflow) still lives in the main repo under docs/ and specs/; this repo
is the public front door.