# No-Build High-State

URL: /docs/guides/no-build-high-state/
Section: guides
Tags: guides, islands, state, no-build

--------------------------------------------------------------------------------

Why this guide You can keep Chirp server-first and still handle complex client state. The default path does not require React, Vite, or npm build pipelines. Recommended stack Server rendering: Chirp + Kida templates Partial updates: htmx Stateful widgets: islands with /static/islands/*.js ES modules Primitive-first pattern Use known primitives first (state_sync, action_queue, draft_store, error_boundary, grid_state, wizard_state, upload_state) before reaching for a full framework island. <section{{ primitive_attrs("wizard_state", props={"stateKey": "signup", "steps": ["a", "b", "c"]}) }}> ... </section> Decision rule Choose no-build primitives when: state is local to one widget htmx still handles server data boundaries you do not need a full client router/runtime Choose framework islands when: third-party JS libraries force framework lifecycle APIs component complexity becomes a mini-app with deep client-only state Operational checklist include SSR fallback content in every mount root always set stable mount id set data-island-version explicitly prefer primitive_attrs(...) to keep props schema clear keep runtime diagnostics enabled (chirp:island:error)

--------------------------------------------------------------------------------

Metadata:
- Word Count: 151
- Reading Time: 1 minutes