Domain orientation
Domain vocabulary and task-specific reading paths.
This repository has one domain context. Before exploring code, read the root glossary and architecture. For document, output or preview work, also read the design document, production or previews reference.
Use the glossary's vocabulary in code, tests, issues and documentation. Record domain terms there; keep implementation details in reference documents.
| Task | Read before changing |
|---|---|
| Configuration, permissions, templates | Configuration, product status |
| Persistence, migration, history | Design document, architecture |
| React integration, callbacks | Integration, API |
| UI, keyboard access, localization | Editor UX |
| Uploads, text, SVG import | Assets and fonts |
| Previews or production | Previews, production |
Update the authoritative reference when its contract changes. Check the actual exported types before copying an API example. Explicitly distinguish available behavior from planned behavior. If a proposal changes a documented architectural choice, identify that choice and explain the trade-off before replacing it.