React SDK

The React SDK is the rendered half of the platform. Python ships schema and operations; TypeScript ships UX. Their only seam is the typed contract the composer emits — there is no hand-written API client.

The SDK is two layers:

• @angee/sdk — headless: contracts, hooks, and urql wiring.
• @angee/base — the single rendered binding: shells, page presets (DataPage / HeroPage / CanvasPage), a view family (ListView / FormView / BoardView / …), meaning-bound field widgets, Tailwind-token theming, and per-addon i18n.

An addon with UI ships a sibling React package @angee/<addon>-base that contributes its routes, views, widgets, menus, and translations through defineAddon; the host composes them with createApp.

Start here

• Frontend Guidelines — the rules: one component tree, additive slots, token-first theming, and the server as the authorization boundary.

Across the platform

• The Opinionated Stack — the frontend libraries and the rendered binding, and what each one owns (React 19, urql, TanStack, base-ui, …).
• Concepts & Glossary — defineAddon, createApp, slots, tokens, the rendered binding.
• End-to-End Testing — how the composed Vite/React SPA is driven against the running backend with Playwright.

The backend that emits the contract this SDK consumes lives under Django framework.