Getting Started
/
Project Structure
Project Structure
How a React API Stack repository is laid out, directory by directory.
A React API Stack project keeps a clean separation between what you author (TypeScript resources and tokens) and what is generated (the manifest, the OpenAPI contract, and the typed client).
1
resources/ TypeScript resource definitions — the single source of truth
2
tools/ the rastack package — compiler, codegen, CLI, and the React runtime
3
tokens/ the design system — DTCG design tokens (.json + .ts)
4
rust/ Cargo workspace — the manifest-driven API, Iceberg storage, admin
5
data/ the local database — a committed directory of Iceberg/Parquet files
6
web/ the marketing site and docs (this site)
7
docs/ architecture & design docs
8
examples/ runnable references — serverless/ = Lambda + S3 deployment
schema.rastack.json — the canonical manifest
openapi.json — the API contract
tokens.css, tokens.ts, tokens.rastack.json
› Good to know
The generated manifest drives the Rust API, the admin site, and the codegen — there is no per-resource server code to write. Add a resource, recompile, and every surface updates.
The rust/ directory is a Cargo workspace whose crates are entirely manifest-driven:
•
rastack-manifest — a serde model of the schema.
•
rastack-store — the Iceberg engine over a swappable object backend and codec.
•
rastack-api-core — the framework-free request brain (CRUD, FK validation, access control).
•
rastack-api — the axum HTTP adapter, plus the admin module and JWT verification.
•
rastack-wasm — the same engine compiled for the browser.
•
rastack-server — the binary that rastack serve and rastack admin exec.
Build with AI
Every page is available as clean Markdown for LLMs and coding agents. Point one at the files below to build on top of React API Stack.
React API Stack · alpha · built to scale to millions