Git-like content history
Every save is a commit with author and message; history branches instead of overwriting, and schema-aware diffs make review effortless.
Model content as reusable blocks, edit it visually, deliver it anywhere through a fast, cached Data API.

| You are… | Read |
|---|---|
| New to b10cks | Introduction, then the Quickstart — empty space to rendered page in ~10 minutes |
| An editor or content team member | The user guide — friendly walkthroughs of every screen |
| A developer building a frontend | The Nuxt guide (or your framework's), plus Querying content |
| Running your own instance | Self-hosting |
| Package | Purpose |
|---|---|
@b10cks/client | Framework-agnostic Data API client |
@b10cks/richtext | Zero-dependency rich text rendering (HTML / plain text) |
@b10cks/vue | Vue 3 plugin, composables, editable directives |
@b10cks/nuxt | Nuxt 4 module on top of @b10cks/vue |
@b10cks/react | React provider and hooks |
@b10cks/next | Next.js integration on top of @b10cks/react |
@b10cks/svelte | Svelte context, stores, and actions |
@b10cks/mgmt-client | Typed Management API client — guide |
@b10cks/cli | Terminal workflows & TypeScript type generation — guide |
@b10cks/mcp-server | MCP server for AI assistants — guide |