@riverbankcms/sdk 0.129.0 → 0.129.1

package/dist/cli/init-docs/content/context-brand.md

@@ -1,125 +0,0 @@
-# Brand Assets
-
-This document helps AI agents understand the visual brand identity for consistent content creation.
-
-## Purpose
-
-Document brand assets and guidelines including:
-
-- Logo usage and variations
-- Color palette
-- Typography
-- Image and illustration style
-- Design patterns
-
-## Color Palette
-
-Define the brand colors:
-
-```
-Primary:    #______  (e.g., #0066CC - main brand color)
-Secondary:  #______  (e.g., #00CC66 - accent color)
-Accent:     #______  (e.g., #CC6600 - highlight color)
-
-Neutrals:
-- Dark:     #______  (e.g., #1A1A1A - headings, body text)
-- Medium:   #______  (e.g., #666666 - secondary text)
-- Light:    #______  (e.g., #F5F5F5 - backgrounds)
-- White:    #FFFFFF
-
-Status:
-- Success:  #______  (e.g., #22C55E)
-- Warning:  #______  (e.g., #F59E0B)
-- Error:    #______  (e.g., #EF4444)
-- Info:     #______  (e.g., #3B82F6)
-```
-
-## Typography
-
-Define the font families:
-
-```
-Headings:   [Font Name], [weight] (e.g., Inter, bold)
-Body:       [Font Name], [weight] (e.g., Inter, regular)
-Code:       [Font Name] (e.g., JetBrains Mono)
-```
-
-**Heading sizes:**
-- H1: (e.g., 48px / 3rem)
-- H2: (e.g., 36px / 2.25rem)
-- H3: (e.g., 24px / 1.5rem)
-- H4: (e.g., 20px / 1.25rem)
-
-**Body text:** (e.g., 16px / 1rem, line-height 1.6)
-
-## Logo Files
-
-Reference paths to logo files:
-
-| Variant | Path | Usage |
-|---------|------|-------|
-| Primary | `/public/logo.svg` | Main logo for light backgrounds |
-| Dark mode | `/public/logo-dark.svg` | For dark backgrounds |
-| Icon only | `/public/logo-icon.svg` | Favicon, small spaces |
-| Full width | `/public/logo-full.svg` | Header, large displays |
-
-**Logo usage guidelines:**
-- Minimum clear space: (e.g., equal to the height of the logomark)
-- Minimum size: (e.g., 100px width for full logo, 24px for icon)
-- Don't stretch, rotate, or alter colors
-
-## Image Style
-
-Guidelines for imagery:
-
-**Photography:**
-- Style: (e.g., bright and modern, lifestyle-focused, professional)
-- Subjects: (e.g., people using products, workspace shots, abstract)
-- Avoid: (e.g., stock photo cliches, outdated imagery)
-
-**Illustrations:**
-- Style: (e.g., flat design, 3D, hand-drawn, geometric)
-- Color usage: (e.g., use brand colors only, limited palette)
-
-**Aspect ratios:**
-- Hero images: (e.g., 16:9, 1920x1080 minimum)
-- Blog thumbnails: (e.g., 3:2, 1200x800)
-- Social sharing: (e.g., 1.91:1 for Open Graph)
-
-## Icons
-
-Icon style and sources:
-
-- **Icon set**: (e.g., Lucide, Heroicons, custom)
-- **Style**: (e.g., outline, solid, duotone)
-- **Size**: (e.g., 24px default, 16px small, 32px large)
-- **Color**: (e.g., inherit from text, or specific brand color)
-
-## Example Completed Section
-
-```markdown
-## Color Palette
-
-Primary:    #2563EB  (Blue - main brand color)
-Secondary:  #10B981  (Green - success states, CTAs)
-Accent:     #8B5CF6  (Purple - highlights)
-
-Neutrals:
-- Dark:     #111827  (Gray 900 - headings)
-- Medium:   #6B7280  (Gray 500 - body text)
-- Light:    #F9FAFB  (Gray 50 - backgrounds)
-- White:    #FFFFFF
-
-## Typography
-
-Headings:   Inter, semibold (600)
-Body:       Inter, regular (400)
-Code:       Fira Code, regular
-
-## Image Style
-
-Photography: Clean, bright, professional. Real people in real workspaces.
-Illustrations: Flat design with brand colors. Simple, modern, friendly.
-
-Avoid: Dark/moody imagery, overly complex graphics, generic stock photos.
-```

package/dist/cli/init-docs/content/context-brief.md

@@ -1,77 +0,0 @@
-# Site Brief
-
-This document helps AI agents understand the brand, tone, and goals for this site. Fill in the sections below to provide context for content creation.
-
-## Brand Voice
-
-Describe how the brand communicates:
-
-- **Tone**: (e.g., professional, friendly, technical, casual, authoritative)
-- **Personality**: (e.g., helpful, innovative, trustworthy, playful)
-- **Language style**: (e.g., simple and direct, detailed and thorough, conversational)
-
-**Words/phrases to use:**
-- (Add brand-appropriate terminology)
-
-**Words/phrases to avoid:**
-- (Add terms that don't fit the brand)
-
-## Target Audience
-
-Who is this site for?
-
-- **Primary audience**: (e.g., small business owners, developers, enterprise teams)
-- **Secondary audience**: (if applicable)
-- **Technical level**: (e.g., beginner, intermediate, expert)
-- **Key pain points**: (what problems are they trying to solve?)
-
-## Site Purpose
-
-What is this site meant to achieve?
-
-- **Primary goal**: (e.g., generate leads, sell products, provide information)
-- **Secondary goals**: (e.g., build brand awareness, support customers)
-- **Key user journeys**: (what should visitors do on the site?)
-
-## Content Guidelines
-
-Standards for content creation:
-
-- **Preferred content length**: (e.g., blog posts 800-1200 words)
-- **Heading style**: (e.g., sentence case, title case)
-- **Image requirements**: (e.g., minimum resolution, preferred aspect ratios)
-- **SEO focus areas**: (key topics or keywords)
-
-## Example
-
-```markdown
-## Brand Voice
-
-- **Tone**: Professional but approachable
-- **Personality**: Helpful, knowledgeable, straightforward
-- **Language style**: Clear and concise, avoid jargon unless necessary
-
-**Words to use:** streamline, efficient, simple, powerful, reliable
-**Words to avoid:** synergy, leverage, disrupt, revolutionary
-
-## Target Audience
-
-- **Primary**: Small to medium business owners looking for a CMS
-- **Technical level**: Intermediate - comfortable with technology but not developers
-- **Pain points**: Current CMS is too complex, need better content management
-
-## Site Purpose
-
-- **Primary goal**: Convert visitors to trial signups
-- **Key journeys**:
-  1. Learn about features → Start free trial
-  2. Read case studies → Request demo
-  3. Check pricing → Choose plan
-
-## Content Guidelines
-
-- Blog posts: 1000-1500 words
-- All headings in sentence case
-- Include at least one image per blog post
-- Focus on "headless CMS" and "content management" keywords
-```

package/dist/cli/init-docs/content/context-knowledge.md

@@ -1,111 +0,0 @@
-# Knowledge Base
-
-This directory stores domain knowledge, reference information, and facts that AI agents need when working with this site's content.
-
-## Purpose
-
-Help agents understand:
-
-- Industry terminology and definitions
-- Product or service details
-- Technical specifications
-- Frequently asked questions
-- Reference data and statistics
-
-## Suggested Organization
-
-Create files for different knowledge areas:
-
-| File | Purpose |
-|------|---------|
-| `products.md` | Product catalog, features, specifications |
-| `services.md` | Service offerings and descriptions |
-| `faq.md` | Common questions and answers |
-| `glossary.md` | Industry terms and definitions |
-| `competitors.md` | Competitive landscape and differentiation |
-| `stats.md` | Key statistics and data points |
-
-## Example File Format
-
-### products.md
-
-```markdown
-# Products
-
-## Product: Widget Pro
-
-- **SKU**: WP-001
-- **Category**: Automation Tools
-- **Price**: $99/month
-- **Target customer**: Small business teams
-
-### Key Features
-- Feature A: Description of what it does
-- Feature B: Description of what it does
-- Feature C: Description of what it does
-
-### Use Cases
-- Scenario 1: How customers use this
-- Scenario 2: Another common use case
-
-### Comparison to Widget Basic
-- Pro has X, Basic doesn't
-- Pro supports Y users, Basic supports Z
-```
-
-### glossary.md
-
-```markdown
-# Glossary
-
-## A
-
-**API (Application Programming Interface)**
-A set of protocols that allows different software applications to communicate.
-
-**Authentication**
-The process of verifying user identity before granting access.
-
-## B
-
-**Block**
-A modular content component in RiverbankCMS (e.g., hero, text, image).
-
-## C
-
-**CMS (Content Management System)**
-Software for creating, managing, and publishing digital content.
-
-**Content Type**
-A defined structure for a category of content (e.g., blog posts, products).
-```
-
-### faq.md
-
-```markdown
-# Frequently Asked Questions
-
-## General
-
-**Q: What is [Product Name]?**
-A: [Product Name] is a [brief description]. It helps [target audience] to [main benefit].
-
-**Q: How much does it cost?**
-A: Pricing starts at $X/month. See our pricing page for full details.
-
-## Technical
-
-**Q: What integrations are available?**
-A: We integrate with [List of integrations]. Custom integrations are available via our API.
-
-**Q: Is there a free trial?**
-A: Yes, we offer a 14-day free trial with full access to all features.
-```
-
-## Best Practices
-
-- Keep information factual and up-to-date
-- Use consistent formatting across files
-- Include dates when information might become outdated
-- Cross-reference related topics
-- Update when products, services, or facts change

package/dist/cli/init-docs/content/getting-started.md

@@ -1,171 +0,0 @@
-# Getting Started with RiverbankCMS SDK
-
-This site uses RiverbankCMS as a headless CMS. Content is managed through the SDK CLI.
-
-## Quick Setup
-
-### 1. Verify Environment Configuration
-
-Check `.env.local` has these variables:
-
-```bash
-# Local development
-RIVERBANK_LOCAL_SITE_ID=your-site-id
-RIVERBANK_LOCAL_DASHBOARD_URL=http://localhost:4000
-RIVERBANK_LOCAL_MGMT_API_KEY=bld_mgmt_sk_...
-
-# Production (optional)
-RIVERBANK_REMOTE_SITE_ID=your-site-id
-RIVERBANK_REMOTE_DASHBOARD_URL=https://your-dashboard.riverbankcms.com
-RIVERBANK_REMOTE_MGMT_API_KEY=bld_mgmt_sk_...
-```
-
-### 2. Pull Content
-
-Download current content from the CMS:
-
-```bash
-riverbankcms pull
-```
-
-This creates a `content/` directory with JSON files:
-
-```
-content/
-├── entries/
-│   └── [content-type].json
-├── pages/
-│   └── [page-identifier].json
-├── themes/
-│   └── current.json
-└── navigation.json
-```
-
-You can also pull just the theme:
-
-```bash
-riverbankcms pull theme
-```
-
-### 3. Make Changes
-
-Edit the JSON files directly, or use CLI commands:
-
-```bash
-# Create or update an entry
-riverbankcms entry upsert blog-post my-new-post --data '{"title": "New Post"}'
-
-# Create a page
-riverbankcms page upsert about --title "About Us" --path /about
-
-# Add a block to a page
-riverbankcms block upsert about hero-section --kind block.hero --data '{"heading": "About Us"}'
-```
-
-### 4. Push Changes
-
-Preview what would change:
-
-```bash
-riverbankcms push --dry-run
-```
-
-Apply changes to the CMS:
-
-```bash
-riverbankcms push
-```
-
-## Local Theme Iteration (Edge-safe)
-
-If your SDK site uses `createCatchAllPage()`, you can render with local theme objects (and switch themes at runtime) without pushing theme changes to the CMS. See `cli-reference.md` for theme pull/push commands and the SDK README for the `createCatchAllPage({ themes, themeSwitch })` API.
-
-Event registration blocks need both the SDK base stylesheet and a runtime theme scope. Generated SDK pages that render inside `Layout` get `ThemeScope` by default. Standalone `Page` or `Block` usage should wrap registration content in `ThemeBridgeProvider` or manual `generateThemeBridgeCss` with a `data-theme-scope="sdk"` wrapper; keep visual changes in scoped CSS variables instead of forking booking logic.
-
-## Key Documentation
-
-| Document                | Purpose                                                          |
-| ----------------------- | ---------------------------------------------------------------- |
-| `cli-reference.md`      | All CLI commands and options                                     |
-| `content-management.md` | How content is structured                                        |
-| `schema.md`             | This site's content types and blocks (auto-generated)            |
-| `block-types.md`        | Available block types (auto-generated)                           |
-| `theme-schema.md`       | Theme schema reference (auto-generated from Zod)                 |
-| `workflows/`            | Step-by-step guides for common tasks, including editor workflows |
-| `workflows/agent-safe-sync.md` | Agent-safe dry-run, scoped push, and stale-content handling |
-
-## Common Tasks
-
-| Task             | Command                                                               |
-| ---------------- | --------------------------------------------------------------------- |
-| Pull all content | `riverbankcms pull`                                                   |
-| Push changes     | `riverbankcms push`                                                   |
-| Preview changes  | `riverbankcms push --dry-run`                                         |
-| Create a page    | `riverbankcms page upsert <id> --title "..." --path /...`             |
-| Add a block      | `riverbankcms block upsert <page> <block-id> --kind ... --data '...'` |
-| Publish an entry | `riverbankcms entry publish <type> <id>`                              |
-| Publish a page   | `riverbankcms page publish <id>`                                      |
-| List entries     | `riverbankcms entry list <type>`                                      |
-| Get JSON output  | Add `--json` to any command                                           |
-
-## Configuration Files
-
-### riverbank.config.ts
-
-Main SDK configuration defining:
-
-- Site ID
-- Custom blocks
-- Block field extensions
-- Block field options
-- Content type definitions
-- Sync settings
-
-### content.config.ts (if present)
-
-Additional content configuration for scaffolding.
-
-## Working with Remote/Production
-
-If the remote site, management key, or dashboard user access is not set up yet, start with the safe setup planner:
-
-```bash
-riverbankcms setup plan --env=remote
-```
-
-See `workflows/remote-setup.md` for the full site/key/user lifecycle. The SDK CLI uses site-scoped management keys for sync; remote site creation, key issuance, and user access changes stay in the dashboard/admin surface.
-
-Use `--env=remote` to target production instead of local:
-
-```bash
-# Pull from production
-riverbankcms pull --env=remote
-
-# Push to production (requires --yes for safety)
-riverbankcms push --env=remote --yes
-```
-
-**Safety note:** Remote push requires `--yes` flag to prevent accidental production changes.
-
-Prefer the CLI `--env` flag over shell prefixes such as `RIVERBANK_ENV=remote riverbankcms ...`. Site `.env.local` files often contain their own `RIVERBANK_ENV` value, while `--env=remote` is explicit and reliable for CLI sync commands.
-
-For narrow production edits, dry-run and apply the smallest scope:
-
-```bash
-riverbankcms push pages privacy-policy --env=remote --dry-run
-riverbankcms push pages privacy-policy --env=remote --yes
-```
-
-If local content includes unrelated differences, see `workflows/agent-safe-sync.md` for the temporary `--content-dir` pattern.
-
-## Media Safety (Avoid Broken Images)
-
-- Portable content JSON should store media as **identifier-only** (no `assetId` / storage paths / `src`).
-- Download media bytes to disk: `riverbankcms pull --local-media`
-- Optional (CMS → CMS): sync media bytes by identifier + checksum: `riverbankcms pull --env=remote --sync-media --yes`
-
-## Next Steps
-
-1. Read `cli-reference.md` for detailed command documentation
-2. Review `schema.md` to understand this site's content model
-3. Check `workflows/` for step-by-step guides

package/dist/cli/init-docs/content/site-workflows-readme.md

@@ -1,96 +0,0 @@
-# Site-Specific Workflows
-
-This directory is for workflows specific to this site. The core workflows in `../workflows/` cover generic SDK operations, while this folder is for site-specific procedures.
-
-## When to Add Site Workflows
-
-Add workflows here when you have:
-
-- **Site-specific content patterns** - e.g., "How to add a new product to the catalog"
-- **Custom block configurations** - e.g., "Setting up the featured posts carousel"
-- **Multi-step business processes** - e.g., "Publishing a campaign landing page"
-- **Integration procedures** - e.g., "Syncing content with the marketing site"
-
-## Creating a Workflow
-
-Create a markdown file following this structure:
-
-```markdown
-# Workflow: [Name]
-
-## Purpose
-
-What this workflow accomplishes and when to use it.
-
-## Prerequisites
-
-- Required access, tools, or setup
-- Any content that must exist first
-
-## Steps
-
-1. First step with command
-   ```bash
-   riverbankcms ...
-   ```
-
-2. Second step
-   ```bash
-   riverbankcms ...
-   ```
-
-## Verification
-
-How to confirm the workflow completed successfully.
-
-## Rollback (if applicable)
-
-How to undo the changes if needed.
-
-## Notes
-
-Any additional context or edge cases.
-```
-
-## Example Workflows
-
-### Site-specific content creation
-
-`create-product.md`:
-```markdown
-# Workflow: Create a Product
-
-## Purpose
-Add a new product to the catalog with all required fields.
-
-## Steps
-1. Create the product entry
-2. Add product images
-3. Link to category
-4. Publish
-```
-
-### Campaign or seasonal content
-
-`launch-campaign.md`:
-```markdown
-# Workflow: Launch Marketing Campaign
-
-## Purpose
-Create and publish a campaign landing page with all blocks.
-
-## Steps
-1. Create campaign page
-2. Add hero with campaign messaging
-3. Add product grid
-4. Add CTA section
-5. Preview and publish
-```
-
-## Best Practices
-
-- Keep workflows focused on one task
-- Include all commands needed (copy-pasteable)
-- Document site-specific field requirements
-- Reference the CLI reference for command details
-- Update workflows when the site schema changes