| Need | Guide |
|---|---|
| Install and troubleshoot | Platform downloads · Troubleshooting · Upgrade from Tauri |
| Phone apps | iOS and Android |
| Models and hardware | Engine guides · Model downloads |
| Speech and cloning | Voice design · Expressive speech · Audio quality |
| Dubbing | Multi-speaker guide · Translation · Exports |
| Stories and audiobooks | Longform guide · Projects |
| Voices and sharing | Gallery · Persona format · Network sharing |
| Dictation and transcription | Dictation · Transcriptions |
| Automation | Local API · MCP · Workflows and calls |
| Need | Reference |
|---|---|
| Contribute | Contributing · Electron development |
| Repository layout | Project structure |
| Shipping capabilities | Feature catalog · Electron parity |
| Planned work | Live roadmap |
| Release and distribution | Release checklist · Store publishing |
| Model licensing | Inventory · Review workflow |
| Designs and decisions | Design references · Architecture decisions |
Keep current behavior in the topic guide and update it in the same PR as the implementation. Link to that guide rather than keeping a second status report. The live issue tracker owns pending work; dated plans describe their original snapshot, not current feature availability or repository policy.
Retain migration guidance, format/security contracts, licensing evidence and useful investigation results. Remove superseded implementation checklists after checking incoming references; git history keeps the original text. For example:
git log --all -- docs/maintenance-pages-modularization.md
git show <commit>:docs/maintenance-pages-modularization.mdValidate relative links with:
uv run pytest -q tests/test_docs_links.py