@brightsideoy/kama 0.1.0-alpha.142 → 0.1.0-alpha.145

package/README.md

@@ -81,67 +81,46 @@ KAMA doesn't just serve content; it actively manages its lifecycle across the gl
 
 At the heart of KAMA is the Schema Engine. Instead of complex database migrations, you define your content models, layouts, and reusable blocks in simple YAML files. KAMA dynamically bundles these definitions at build-time to auto-generate your entire Admin UI, database indexes, and API endpoints.
 
-**[Read the full Schema Documentation here](/@brightsideoy/kama/documentation/SCHEMAS.md)**
+**[Read the full Schema Documentation here](documentation/SCHEMAS.md)**
 
 <br>
 
 ## Getting Started
 
-KAMA comes with an interactive executable CLI to instantly spin up a full monorepo (Backend Worker + optional Astro Frontend), add new sites to existing workspaces, or promote local setups to Cloudflare Edge.
+KAMA comes with a scaffolding CLI to instantly spin up a full monorepo (Backend + Astro Frontend).
 
-### 1. Initialize a Workspace\*\*
-
-Run the KAMA CLI to start the workspace wizard:
+## 1. Initialize a Workspace
 
 ```bash
-npx kama init
+npx @brightsideoy/kama@alpha
 ```
 
-The CLI will prompt you for your setup preferences and automatically:
+Select **"Kickstart new KAMA Monorepo"**. The CLI will automatically:
 
-- Scaffold the `kama-worker` engine and content definition directories (`content/definitions/`).
-- Authenticate with Cloudflare and auto-provision a remote D1 database + R2 bucket bindings (if deploying to Edge).
-- Scaffold a fully configured Astro frontend site inside `sites/` with built-in edge-caching middleware.
-- Configure local SQLite fallback environments for completely offline development.
+- Authenticate with Cloudflare (if deploying to the Edge).
+- Create a new D1 database (or local SQLite equivalent).
+- Bind your R2 media buckets.
+- Setup the Worker backend and Astro frontend.
 
-### 2. Local Development
+## 2. Local Development
 
-Start the local CMS dev server from your workspace root:
+Start the backend and frontend simultaneously on your local machine:
 
 ```bash
 npm run dev:cms
 ```
 
-This command automatically compiles your YAML/JSON schemas into runtime JavaScript definitions, syncs your local SQLite database, and launches the Miniflare worker environment on `http://localhost:8787`.
-
-### 3. Management Commands\*\*
-
-You can run CLI commands anytime inside your workspace.
-
-#### Add a New Astro Frontend Site
-
-```bash
-npx kama add site
-```
-
-#### Promote a Local Workspace to Cloudflare Edge
-
-Convert a local offline workspace to Cloudflare Edge (auto-links domains & D1 databases):
+This bundles your local YAML schemas, syncs the local SQLite/D1 database, and starts the Wrangler dev server on your localhost.
 
-```bash
-npx kama promote
-```
+## 3. Deploy
 
-### 4. Deploy
-
-Deploy your CMS engine, content definitions, and database migrations to Cloudflare Edge:
+Push your API, schemas, and database migrations to Cloudflare's global network, or package it for your virtual server:
 
 ```bash
 npm run deploy:cms
 ```
 
-> **Note:** For self-hosted virtual servers (VPS) or Docker environments, you can run `npm run dev:cms` under PM2/Docker as a standalone `workerd` server.
-> <br>
+<br>
 
 ## Directory Structure Overview
 
@@ -155,7 +134,7 @@ my-kama-workspace/
 │       ├── nodes/           # e.g., page.yaml, product.yaml
 │       ├── blocks/          # e.g., hero.yaml, image_card.yaml
 │       └── node-layouts/    # e.g., two-column.yaml
-├── kama-worker/              # 👉 BACKEND PIPELINE
+├── cms-worker/              # 👉 BACKEND PIPELINE
 │   ├── index.js             # Worker entrypoint (ES Module)
 │   ├── wrangler.json        # Bindings (D1, R2, Vars)
 │   └── package.json