Documentation
From first install to advanced terminal interaction, follow one deliberate path through TermRock.
Install and pin the reviewed revision first. Then build one useful screen, learn the ownership boundary, and add customization only when the product requires it.
Start here
- 01InstallationAdd the Git dependency and pin a reviewed revision.
- 02Getting StartedRender a stateful component and handle its outcome.
- 03CustomizationChoose roles, density, glyphs, motion, and capability.
- 04APIInspect canonical components and exact public identities.
- 05AdvancedCompose public components into product-owned application screens.
Choose the right layer
Keep the boundary clear
TermRock owns terminal geometry, interaction mechanics, focus, semantic paint, Unicode behavior, and capability fallbacks. Your application owns domain state, language, persistence, networking, permissions, and effects.
Continue with interaction conventions when a screen adds overlays or composite focus. Use quality and migrations before upgrading a pinned revision.