@agent-native/core 0.122.4 → 0.123.1

package/docs/content/template-content.mdx

@@ -1,6 +1,6 @@
 ---
 title: "Content"
-description: "Open-source Obsidian for MDX: edit local Markdown/MDX files, generate rich interactive custom blocks, and write with an AI agent."
+description: "Open-source Obsidian for MDX: edit local Markdown/MDX files, build Notion-style databases, and write with an AI agent."
 ---
 
 # Content
@@ -11,7 +11,7 @@ you. Open a doc, ask "rewrite this paragraph to be more concise" or "create a
 page called Q4 Planning with sub-pages for Goals, Metrics, and Risks" - same
 result whether you do it yourself or ask.
 
-<WireframeBlock id="doc-block-1i1ubpx">
+<WireframeBlock id="doc-block-content1">
   <Screen
     surface="desktop"
     html={
@@ -22,7 +22,7 @@ result whether you do it yourself or ask.
 
 When you open the app, you'll see a page tree next to the editor. The agent always knows which page you're viewing and what text you have selected, so document edits can stay grounded in the current page.
 
-<Diagram id="doc-block-159ykca" title="One document, many editors" summary={"You and the agent both write through the same Yjs pipeline. SQL is the canonical store; local files and Notion are optional sync surfaces."}>
+<Diagram id="doc-block-content2" title="One document, three sync surfaces" summary={"You and the agent both write through the same live editing pipeline. SQL is the canonical store; local files, Notion, and Builder CMS are optional sync surfaces around it."}>
 
 ```html
 <div class="diagram-flow">
@@ -37,11 +37,6 @@ When you open the app, you'll see a page tree next to the editor. The agent alwa
     </div>
   </div>
   <div class="diagram-arrow diagram-muted" aria-hidden="true">&rarr;</div>
-  <div class="diagram-panel center">
-    <span class="diagram-pill accent">Yjs CRDT</span
-    ><small class="diagram-muted">live, conflict-free merge</small>
-  </div>
-  <div class="diagram-arrow diagram-muted" aria-hidden="true">&rarr;</div>
   <div class="diagram-box">
     documents (markdown)<br /><small class="diagram-muted"
       >canonical SQL store</small
@@ -55,6 +50,11 @@ When you open the app, you'll see a page tree next to the editor. The agent alwa
     <div class="diagram-box">
       Notion pages<br /><small class="diagram-muted">pull · push</small>
     </div>
+    <div class="diagram-box">
+      Builder CMS entries<br /><small class="diagram-muted"
+        >pull · guarded push</small
+      >
+    </div>
   </div>
 </div>
 ```
@@ -75,31 +75,19 @@ When you open the app, you'll see a page tree next to the editor. The agent alwa
   font-size: 22px;
   line-height: 1;
 }
-.diagram-flow .center {
-  display: flex;
-  flex-direction: column;
-  align-items: center;
-  gap: 4px;
-}
 ```
 
 </Diagram>
 
 ## What you can do with it
 
-- **Write rich text** with headings, lists, tables, code blocks, images, and links. Slash commands (`/`) insert blocks; selecting text pops up a formatting toolbar.
-- **Organize pages in a tree** — nest infinitely, drag to reorder, favorite pages you use often.
-- **Search across everything** with full-text search across titles and content.
-- **Edit local Markdown/MDX files like Obsidian.** Use the `/local-files` view
-  to connect a folder to a space's Files database, edit with your own tools,
-  sync changes, and review conflicts without leaving the database-backed app.
-- **Generate rich interactive custom blocks.** Register local React components,
-  insert them as MDX, and let the agent create or update component files for
-  your docs.
-- **Sync with Notion.** Link a local doc to a Notion page and pull or push content in either direction. Comments sync both ways too.
-- **Collaborate in real time.** Multiple people (and the agent) can edit the same doc at the same time.
+- **Write and organize documents.** Rich text editing, an infinitely nested page tree, favorites, comments, version history, and sharing. See [Writing & organizing documents](/docs/template-content-editing).
+- **Build Notion-style databases.** Tables where every row is its own document, with typed properties and table/list/gallery/board/calendar/timeline/form views. See [Databases, properties & forms](/docs/template-content-databases).
+- **Collect structured submissions.** Turn a database into an intake form that the agent, Slack, or another app can submit into safely. See [Databases, properties & forms](/docs/template-content-databases).
+- **Edit files on disk like Obsidian**, and keep documents in sync with Notion or Builder CMS. See [Local files, Notion & Builder CMS sync](/docs/template-content-sync).
+- **Collaborate in real time.** Multiple people (and the agent) can edit the same doc at the same time without clobbering each other.
 - **Share docs** with teammates or make them public — private by default, with viewer / editor / admin roles.
-- **Ask the agent for anything**: "Rewrite this paragraph." "Add a TL;DR at the top." "Find all my meeting notes from last week." "Make this tone more formal."
+- **Ask the agent for anything**: "Rewrite this paragraph." "Add a TL;DR at the top." "Find all my meeting notes from last week." "Create a beta-signup database with a form for Slack submissions."
 
 ## Getting started
 
@@ -115,549 +103,21 @@ When you open the app, click **+ New page** in the sidebar, give it a title, and
 
 Select text and hit Cmd+I to focus the agent with that selection pre-loaded — "make this punchier" then operates on exactly what you highlighted.
 
-## Local Markdown/MDX files {#local-files}
-
-Content can round-trip documents through local files without cloning or running
-the Content app locally. It feels like Obsidian for MDX: files stay inspectable
-and editable on disk, while the app gives you a rich editor, agent actions,
-sharing, and custom blocks. Open
-`/local-files`, choose a folder in your browser or Agent Native Desktop, and
-export the current document tree as Markdown/MDX under `content/`.
-
-Each exported file contains frontmatter for document metadata (`id`, `title`,
-`parentId`, `position`, favorite/search/visibility flags, and `updatedAt`) plus
-the document body as Markdown. You can edit those files in your normal editor,
-then return to `/local-files` to preview and import changes back into Content.
-
-This workflow is useful when you want content in source control, want to batch
-edit docs with local tools, or want a no-clone path for teams that prefer files
-as the review surface. The hosted app remains the source of truth for sharing,
-comments, permissions, and live collaboration; the local folder is an explicit
-sync surface.
-
-Local folders now use the same database model as every other page. Each page
-belongs to a space and its system Files database; a folder is a source adapter
-on that database. You can attach a folder to an existing space or create a
-private folder-backed space, then use database properties and saved sidebar
-views on the imported pages. See [Local folder sources](/docs/local-file-mode)
-for configuration, truth policies, conflicts, custom MDX components, and local
-`extensions/` widgets.
-
-To open Content for an existing repo:
-
-```bash
-npx @agent-native/core@latest content .
-```
-
-The CLI starts normal database-backed Content, registers an opaque local-folder
-connection in `agent-native.json`, and opens the connection screen. It does not
-set a local-mode environment variable.
-
-## For developers
-
-The rest of this doc is for anyone forking the Content template or extending it.
-
-### Quick start
-
-Scaffold a new workspace with the Content template:
+To scaffold your own copy of Content:
 
 ```bash
-npx @agent-native/core@latest create my-workspace --standalone --template content
-cd my-workspace
-pnpm install
-pnpm dev
-```
-
-Open `http://localhost:8083` and create your first page. Then ask the agent to "create a page called Onboarding and add three sub-pages under it".
-
-### Key features {#key-features}
-
-**Nested pages.** Documents form a draggable tree with favorites, icons, ordering, and page-level sharing.
-
-**Rich MDX editor.** Tiptap powers headings, lists, tables, code blocks, images, links, slash commands, selection toolbars, and local React components.
-
-**Live collaboration.** Yjs keeps multiple editors and agent edits in sync without clobbering each other.
-
-**Search and comments.** Full-text search, anchored comments, version history, and restore flows are built into the document surface.
-
-**Sync surfaces.** Documents can sync with Notion or local Markdown/MDX folders, while SQL remains the canonical collaborative data model.
-
-### Local file sync
-
-The protected `/local-files` route uses the browser File System Access API, or a
-guarded native folder bridge inside Agent Native Desktop, to connect a folder to
-a Files database. SQL stores only an opaque connection ID, relative paths,
-hashes, and source metadata. Sync materializes ordinary database pages and
-records concurrent edits as reviewable change sets instead of silently
-overwriting either side. Disconnecting preserves both database pages and files.
-
-The folder workflow calls `connect-local-folder-source`,
-`sync-local-folder-source`, `resolve-local-folder-conflict`, and
-`disconnect-local-folder-source`. `export-content-source` can export one source
-using its original relative paths.
-
-The source format lives in `shared/content-source.ts`. Keep that file as the
-single contract for filenames, frontmatter, parsing, and serialization.
-
-Local file workspaces can also provide repo-local React components through the
-configured `components` folder. The Content dev server imports PascalCase
-exports from those files, renders matching MDX tags such as `<ImpactCounter />`
-inside the editor, and exposes them in the slash menu under Local components.
-This is the "Obsidian for MDX" layer: custom MDX blocks stay local to the
-workspace, but the editor can render them and the agent can generate or update
-their source without cloning the Content app. A minimal workspace component can
-be:
-
-```tsx filename="components/ImpactCounter.tsx"
-import { useState } from "react";
-
-export function ImpactCounter({
-  label = "points",
-  start = 3,
-}: {
-  label?: string;
-  start?: number;
-}) {
-  const [count, setCount] = useState(start);
-  return (
-    <button type="button" onClick={() => setCount(count + 1)}>
-      Impact: {count} {label}
-    </button>
-  );
-}
-
-export const ImpactCounterInputs = {
-  label: { type: "string", label: "Label", default: "points" },
-  start: { type: "number", label: "Starting count", default: 3 },
-};
+npx @agent-native/core@latest create my-content --standalone --template content
 ```
 
-Use it in local MDX as `<ImpactCounter />`, or insert it from the editor slash
-menu under Local components. When input metadata is exported, selecting the
-component in the editor shows a corner edit button that rewrites the MDX props
-in the local file.
-
-The browser **Local files** picker can read and write `.md` and `.mdx` files on
-its own, but executable React component previews require a local compiler. Run
-Content locally or use Agent Native Desktop so the selected workspace path can
-be registered with the local Content dev server. Vite then imports
-`components/*.tsx`, hot reloads edits to existing component files, and reloads
-the component registry when files are added or removed. Agents can use
-`list-local-component-files` and `write-local-component-file` to inspect or
-update registered component files while the editor updates from the same source.
-
-### Comments
-
-Threaded comments on documents with quoted-text anchors, replies, and resolve state. Backed by the `document_comments` table and `app/components/editor/CommentsSidebar.tsx`. Actions: `list-comments`, `add-comment`. Notion comments can sync both ways via `sync-notion-comments`.
-
-### Version history
-
-Every significant update snapshots a row in the `document_versions` table. The UI surfaces these in `app/components/editor/VersionHistoryPanel.tsx`.
-
-### Sharing and visibility
-
-Documents are private by default. You can change visibility to `org` or `public`, or grant per-user and per-org roles (`viewer`, `editor`, `admin`). The framework's auto-mounted sharing actions work out of the box:
-
-- `share-resource --resourceType document --resourceId <id> --principalType user --principalId <email> --role editor`
-- `unshare-resource` / `list-resource-shares` / `set-resource-visibility`
-
-See the `sharing` skill.
-
-### Teams
-
-A dedicated team page at `/team` (see `app/routes/_app.team.tsx`) uses the framework's `TeamPage` component for creating orgs and managing members.
-
-### Working with the agent
-
-Because the agent sees your current screen, most prompts don't need you to reference a document explicitly. When you have a page open, "this" means that page.
-
-For small edits, the agent uses `edit-document --find ... --replace ...` so only the changed text flows through Yjs — you'll see the diff applied in place rather than the whole page re-render. For bigger rewrites it uses `update-document --content ...`.
-
-If you select text and press Cmd+I (or focus the agent panel), the selection travels with your next message as context, so "make this punchier" operates on exactly what you highlighted.
-
-### Databases and properties
-
-Documents can host inline databases — Notion-style tables where each row is itself a document. The agent can create databases, add items, configure column definitions, and set property values through actions: `create-content-database`, `add-database-item`, `set-document-property`. Property definitions (type, visibility, options, position) live in `document_property_definitions`; per-row values live in `document_property_values`.
-
-### Additional actions
-
-Beyond the CRUD surface in the data model, the template ships `export-document` for converting a page to Markdown or HTML, `transcribe-media` for attaching a transcript to a page, and `restore-document-version` for rolling back to an earlier snapshot.
-
-### Data model
-
-Nine tables, all defined in `server/db/schema.ts`:
-
-- **`documents`** — the page tree. Columns: `id`, `parent_id`, `title`, `content` (markdown), `icon`, `position`, `is_favorite`, `visibility`, `owner_email`, `org_id`, `created_at`, `updated_at`.
-- **`document_versions`** — full snapshots of title and content for version history. Roll back with `restore-document-version`.
-- **`document_comments`** — threaded comments with `thread_id`, `parent_id`, `quoted_text`, `resolved`, and an optional `notion_comment_id` for bidirectional Notion sync.
-- **`document_sync_links`** — one row per Notion-linked document tracking remote page ID, last sync times, conflict state, content hash, and errors.
-- **`document_property_definitions`** — column definitions for inline databases: name, type, visibility, options, and position.
-- **`content_databases`** — inline database objects attached to a `document_id` with a title and view config JSON.
-- **`content_database_items`** — rows in an inline database, each linking a `database_id` to a `document_id`.
-- **`document_property_values`** — per-document property values (`property_id` → `value_json`).
-- **`document_shares`** — per-user and per-org grants created via `createSharesTable`.
-
-<DataModel
-  id="doc-block-wjyvg3"
-  title="Content data model"
-  summary={
-    "Nine tables in server/db/schema.ts. documents is the page tree; the rest hang off it for versions, comments, Notion sync, inline databases, and sharing."
-  }
-  entities={[
-    {
-      id: "documents",
-      name: "documents",
-      note: "The page tree (ownable, markdown body)",
-      fields: [
-        {
-          name: "id",
-          type: "id",
-          pk: true,
-        },
-        {
-          name: "parent_id",
-          type: "id",
-          fk: "documents.id",
-          nullable: true,
-          note: "infinite nesting",
-        },
-        {
-          name: "title",
-          type: "string",
-        },
-        {
-          name: "content",
-          type: "markdown",
-        },
-        {
-          name: "icon",
-          type: "string",
-          nullable: true,
-        },
-        {
-          name: "position",
-          type: "int",
-          note: "sibling ordering",
-        },
-        {
-          name: "is_favorite",
-          type: "bool",
-        },
-        {
-          name: "visibility",
-          type: "enum",
-          note: "private | org | public",
-        },
-        {
-          name: "owner_email",
-          type: "string",
-        },
-        {
-          name: "org_id",
-          type: "id",
-          nullable: true,
-        },
-      ],
-    },
-    {
-      id: "document_versions",
-      name: "document_versions",
-      note: "Full title/content snapshots for version history",
-      fields: [
-        {
-          name: "id",
-          type: "id",
-          pk: true,
-        },
-        {
-          name: "document_id",
-          type: "id",
-          fk: "documents.id",
-        },
-        {
-          name: "title",
-          type: "string",
-        },
-        {
-          name: "content",
-          type: "markdown",
-        },
-      ],
-    },
-    {
-      id: "document_comments",
-      name: "document_comments",
-      note: "Threaded comments with quoted-text anchors",
-      fields: [
-        {
-          name: "id",
-          type: "id",
-          pk: true,
-        },
-        {
-          name: "document_id",
-          type: "id",
-          fk: "documents.id",
-        },
-        {
-          name: "thread_id",
-          type: "id",
-        },
-        {
-          name: "parent_id",
-          type: "id",
-          fk: "document_comments.id",
-          nullable: true,
-        },
-        {
-          name: "quoted_text",
-          type: "string",
-          nullable: true,
-        },
-        {
-          name: "resolved",
-          type: "bool",
-        },
-        {
-          name: "notion_comment_id",
-          type: "string",
-          nullable: true,
-          note: "bidirectional Notion sync",
-        },
-      ],
-    },
-    {
-      id: "document_sync_links",
-      name: "document_sync_links",
-      note: "One row per Notion-linked document",
-      fields: [
-        {
-          name: "id",
-          type: "id",
-          pk: true,
-        },
-        {
-          name: "document_id",
-          type: "id",
-          fk: "documents.id",
-        },
-        {
-          name: "notion_page_id",
-          type: "string",
-        },
-        {
-          name: "conflict",
-          type: "bool",
-        },
-        {
-          name: "content_hash",
-          type: "string",
-        },
-      ],
-    },
-    {
-      id: "content_databases",
-      name: "content_databases",
-      note: "Inline database objects attached to a document",
-      fields: [
-        {
-          name: "id",
-          type: "id",
-          pk: true,
-        },
-        {
-          name: "document_id",
-          type: "id",
-          fk: "documents.id",
-        },
-        {
-          name: "title",
-          type: "string",
-        },
-        {
-          name: "view_config",
-          type: "json",
-        },
-      ],
-    },
-    {
-      id: "content_database_items",
-      name: "content_database_items",
-      note: "Rows in an inline database (each row is a document)",
-      fields: [
-        {
-          name: "id",
-          type: "id",
-          pk: true,
-        },
-        {
-          name: "database_id",
-          type: "id",
-          fk: "content_databases.id",
-        },
-        {
-          name: "document_id",
-          type: "id",
-          fk: "documents.id",
-        },
-      ],
-    },
-    {
-      id: "document_property_definitions",
-      name: "document_property_definitions",
-      note: "Column definitions for inline databases",
-      fields: [
-        {
-          name: "id",
-          type: "id",
-          pk: true,
-        },
-        {
-          name: "name",
-          type: "string",
-        },
-        {
-          name: "type",
-          type: "string",
-        },
-        {
-          name: "options",
-          type: "json",
-          nullable: true,
-        },
-        {
-          name: "position",
-          type: "int",
-        },
-      ],
-    },
-    {
-      id: "document_property_values",
-      name: "document_property_values",
-      note: "Per-document property values",
-      fields: [
-        {
-          name: "id",
-          type: "id",
-          pk: true,
-        },
-        {
-          name: "document_id",
-          type: "id",
-          fk: "documents.id",
-        },
-        {
-          name: "property_id",
-          type: "id",
-          fk: "document_property_definitions.id",
-        },
-        {
-          name: "value_json",
-          type: "json",
-        },
-      ],
-    },
-    {
-      id: "document_shares",
-      name: "document_shares",
-      note: "Per-user and per-org grants (createSharesTable)",
-      fields: [
-        {
-          name: "id",
-          type: "id",
-          pk: true,
-        },
-        {
-          name: "document_id",
-          type: "id",
-          fk: "documents.id",
-        },
-        {
-          name: "principal",
-          type: "string",
-        },
-        {
-          name: "role",
-          type: "enum",
-          note: "viewer | editor | admin",
-        },
-      ],
-    },
-  ]}
-  relations={[
-    {
-      from: "documents",
-      to: "documents",
-      kind: "1-n",
-      label: "has children",
-    },
-    {
-      from: "documents",
-      to: "document_versions",
-      kind: "1-n",
-      label: "has snapshots",
-    },
-    {
-      from: "documents",
-      to: "document_comments",
-      kind: "1-n",
-      label: "has comments",
-    },
-    {
-      from: "documents",
-      to: "document_sync_links",
-      kind: "1-1",
-      label: "links to Notion",
-    },
-    {
-      from: "documents",
-      to: "content_databases",
-      kind: "1-n",
-      label: "hosts databases",
-    },
-    {
-      from: "content_databases",
-      to: "content_database_items",
-      kind: "1-n",
-      label: "has rows",
-    },
-    {
-      from: "document_property_definitions",
-      to: "document_property_values",
-      kind: "1-n",
-      label: "has values",
-    },
-    {
-      from: "documents",
-      to: "document_shares",
-      kind: "1-n",
-      label: "has share grants",
-    },
-  ]}
-/>
-
-Content is stored as markdown. The editor converts to and from the Tiptap JSON model in memory; the SQL row is always markdown so actions, search, and Notion sync can operate on a single canonical format.
-
-All ownable tables include `owner_email` and `org_id` via `ownableColumns()`, so every row is scoped to the signed-in user (and optionally their active organization) from the moment it's created.
-
-### Customizing it
-
-The four places to look when changing behavior:
-
-- **`actions/`** — every operation the agent or UI can perform. Add a new file like `actions/publish-to-wordpress.ts` using `defineAction` and both sides get it for free. Key existing actions: `create-document.ts`, `edit-document.ts`, `update-document.ts`, `delete-document.ts`, `list-documents.ts`, `search-documents.ts`, `get-document.ts`, `pull-notion-page.ts`, `push-notion-page.ts`, `add-comment.ts`, `view-screen.ts`, `navigate.ts`.
-- **`app/routes/`** — the page surface. `_app.tsx` is the pathless layout that keeps the sidebar and agent panel mounted; `_app._index.tsx` is the landing view; `_app.page.$id.tsx` is the editor route; `_app.team.tsx` is the team settings page.
-- **`app/components/editor/`** — the Tiptap editor. Add a new node type under `extensions/` and register it in `DocumentEditor.tsx`. The bubble toolbar, slash menu, and hover previews are all component files you can edit.
-- **`.agents/skills/`** — guidance the agent reads before acting. If you add a new capability (say, a CMS publishing pipeline), drop a `SKILL.md` in a new skill folder so the agent uses it correctly. Existing skills: `document-editing`, `notion-integration`, `real-time-sync`, `delegate-to-agent`, `storing-data`, `self-modifying-code`, `security`, `frontend-design`, `create-skill`, `capture-learnings`.
-- **`AGENTS.md`** — the top-level agent guide with the action cheatsheet and common-tasks table. Update it whenever you add a major feature so the agent discovers it without exploring.
-- **`server/db/schema.ts`** — data model. Add a column or table here. The Content template has no `db:push` script; it relies on strictly additive migrations that run on startup. Edit `server/db/schema.ts`, write a matching additive migration, and the change applies the next time the app boots — schema updates must never drop, rename, or destructively alter existing tables or columns (see [Database](/docs/database#migrations) for guidelines).
-- **`shared/notion-markdown.ts`** — markdown-to-Notion-blocks conversion. Extend this if you add new block types that need to round-trip through Notion.
-
-The agent can make all of these changes itself — ask it to "add a tags column to documents and expose it in the sidebar" and it will update the schema, migrate, wire the UI, and write the action.
+See [Getting started](/docs/getting-started) for the rest of the setup (`cd`, `pnpm install`, `pnpm dev`) and the framework fundamentals.
 
 ## What's next
 
+- [**Writing & organizing documents**](/docs/template-content-editing) — the editor, page tree, comments, version history, and sharing
+- [**Databases, properties & forms**](/docs/template-content-databases) — inline databases, property types, views, external sources, and intake forms
+- [**Local files, Notion & Builder CMS sync**](/docs/template-content-sync) — the Obsidian-style folder workflow plus Notion and Builder CMS round-trips
+- [**Developer Guide**](/docs/template-content-developers) — data model, action inventory, routes, and how to extend the template
 - [**Templates**](/docs/cloneable-saas) — the clone-and-own model, and every other domain template to start from
 - [**Getting Started**](/docs/getting-started) — the framework fundamentals: actions, application state, and live sync
-- [**Local folder sources**](/docs/local-file-mode) — spaces, Files databases, folder adapters, migration, and safety
 - [**Real-Time Collaboration**](/docs/real-time-collaboration) — the Yjs pipeline documents share with other collaborative surfaces
 - [**Sharing**](/docs/sharing) — the share-grant model documents build on