A component content architecture for React. Build sites where content authors and component developers can't break each other's work—and scale from local files to visual editing without rewrites.
Uniweb separates content (markdown files, structured data) from components (React, portable across sites). The architecture enforces this separation, so teams can work independently and foundations can power multiple sites—locally or on the managed platform.
npm create uniweb my-site --template marketing
cd my-site
pnpm install
pnpm devSee the CLI documentation for templates, commands, and configuration.
| Repository | Description |
|---|---|
| uniweb/cli | CLI for creating and building projects (npx uniweb) |
| uniweb/build | Foundation build tooling |
| uniweb/runtime | Foundation loader and orchestrator for sites |
| uniweb/templates | Official project templates |
For developers
- uniweb.io — Developer hub
- uniweb.io/docs — Framework documentation
- CLI README — Detailed usage and reference
For teams and content creators
- uniweb.app — Managed platform with visual editing
- docs.uniweb.app — Platform documentation
Uniweb implements Component Content Architecture (CCA)—a standard for modeling the relationship between content and components. Instead of hard-coding bindings in templates or scattering them across frontend code, CCA treats the binding as a first-class architectural layer.
The result: content stays portable, components stay reusable, and the same foundation can power local development, static builds, or a full visual editing platform.
- Component Content Architecture — The architectural pattern
- Component Web Platforms — The product category
Apache 2.0
Uniweb is a trademark of Proximify Inc.