docs: expand Cloudflare adapter guide with Git workflow, build flow, and R2 update notes

Author: zonayedpca

docs/cli/create-statikapi.mdx

@@ -28,24 +28,32 @@ npx create-statikapi
 
 You will be prompted for:
 
-- **Template**: `basic`, `dynamic`, or `remote-data`
+- **Template**:
+  - `basic` — single endpoint starter
+  - `dynamic` — dynamic + catch-all routes examples
+  - `remote-data` — build-time fetch examples
+  - `cloudflare-adapter` — Cloudflare Worker + R2 + KV with build webhook
 - **Package manager** and whether to install now
-- Optional ESLint, TS, directories, and deploy presets
+- Optional ESLint, TS, directories, and deploy presets  
+  _(For the Cloudflare adapter template, ESLint/TS are effectively skipped; you get a JS Worker-focused boilerplate.)_
 
-> **Note:** The **source** (`src-api/`) and **output** (`api-out/`) directories are defaults. You can **customize** these during scaffolding or later in your [Configuration](../config).
+> **Note:** The **source** (`src-api/`) and **output** (`api-out/`) directories are defaults for the core templates.  
+> You can **customize** these during scaffolding or later in your [Configuration](../config).  
+> For the Cloudflare adapter template, `src-api/` is still the default, but the JSON is pushed to **R2** instead of a local `api-out/` for hosting.
 
 ---
 
 ## Flags
 
-- `--template basic|dynamic|remote-data`
-- `--yes, -y` — accept defaults (non‑interactive)
+- `--template basic|dynamic|remote-data|cloudflare-adapter`
+- `--yes, -y` — accept defaults (non-interactive)
 - `--no-install`
 - `--no-gitignore`
 - `--package-manager pnpm|npm|yarn`
 - `--src-dir <dir>` (default `src-api`, configurable)
-- `--out-dir <dir>` (default `api-out`, configurable)
-- `--deploy cloudflare,netlify,github`
+- `--out-dir <dir>` (default `api-out`, configurable; **ignored by the Cloudflare adapter template**)
+- `--deploy cloudflare,netlify,github`  
+  _(non-Cloudflare templates only; the Cloudflare adapter template always targets Workers)_
 - `--help, -h`
 
 **Examples**
@@ -58,9 +66,36 @@ create-statikapi my-api --template dynamic --no-install
 create-statikapi my-api --src-dir api --out-dir public/api --deploy cloudflare,github
 ```
 
+```bash
+# Cloudflare Worker adapter (serverless mode)
+create-statikapi my-worker --template cloudflare-adapter
+```
+
+---
+
+## Cloudflare adapter template (high-level)
+
+When you choose `cloudflare-adapter`, the scaffolder:
+
+- Copies a **Worker + R2 + KV** boilerplate
+- Prompts you for:
+  - **R2 bucket binding name** and **bucket_name**
+  - **KV namespace binding** and **id**
+  - **`STATIK_BUILD_TOKEN`** (used to authorize `/build`)
+  - **`STATIK_SRC`** (defaults to `src-api`)
+  - **`STATIK_USE_INDEX_JSON`** (whether to favor `/foo/index.json` vs `/foo.json` style)
+- Patches `wrangler.toml` with the values you provide
+
+From there you can:
+
+- Run the dev scripts (based on `wrangler dev` + bundling)
+- Deploy the Worker to Cloudflare
+- Trigger builds via the `/build` webhook documented in  
+  [Serverless Adapters → Cloudflare Worker + R2](../serverless/cloudflare-adapter)
+
 ---
 
 ## Exit codes
 
 - `0` success
-- non‑zero indicates an error (parsing, user module errors, etc.)
+- non-zero indicates an error (parsing, user module errors, etc.)

docs/getting-started.mdx

@@ -2,10 +2,11 @@
 
 Welcome to **StatikAPI** — generate **static JSON endpoints** from small JS/TS modules.
 
-This guide shows two flows:
+This guide shows three flows:
 
 - **From scratch** using `create-statikapi`
 - **Inside an existing repo** by adding the CLI and a `src-api/` folder _(this directory is configurable via your [configuration](./config))_
+- **Serverless mode** using the **Cloudflare Worker adapter** (StatikAPI behind a Worker + R2 + KV, with a build webhook)
 
 ---
 
@@ -43,11 +44,41 @@ npm run dev
 
 You will be prompted for:
 
-- **Template**: `basic`, `dynamic`, or `remote-data`
+- **Template**: `basic`, `dynamic`, `remote-data`, or  
+  `cloudflare-adapter` (Cloudflare Worker + R2 + KV + build webhook)
 - **Package manager** and whether to install now
-- Optional ESLint, TS, directories, and deploy presets
+- Optional ESLint, TS, directories, and deploy presets  
+  _(ESLint/TS are disabled for the Cloudflare adapter template; it ships ready-to-run JS Worker boilerplate.)_
 
-The dev server watches your **source directory** (default `src-api/`, configurable via [Configuration](./config)) and serves a local **UI** at `/_ui` with a live manifest, JSON previews, and copy-ready code snippets.
+The dev server for normal templates watches your **source directory** (default `src-api/`, configurable via [Configuration](./config)) and serves a local **UI** at `/_ui` with a live manifest, JSON previews, and copy-ready code snippets.
+
+---
+
+## 1b) Using the Cloudflare Worker adapter (serverless mode)
+
+If you pick the **`cloudflare-adapter`** template, `create-statikapi` scaffolds:
+
+- A **Cloudflare Worker** wired to:
+  - **R2** (stores built JSON)
+  - **KV** (stores the manifest)
+- A **build webhook endpoint** on the Worker (`/build`)
+- A default **JS-only** boilerplate (no TypeScript / ESLint)
+
+From there you can:
+
+- Run the bundled dev commands to iterate locally
+- Deploy the Worker to Cloudflare
+- **Trigger rebuilds via HTTP**:
+  - `POST /build` — rebuild **all routes**
+  - `POST /build?route=/users/1` — rebuild just that route
+
+Authentication is handled via a **`STATIK_BUILD_TOKEN`** env var on the Worker.  
+Clients include this token in requests (see [Cloudflare Worker + R2 Adapter](./serverless/cloudflare-adapter) for full details and `curl` examples).
+
+This mode is ideal when:
+
+- You want StatikAPI’s DX, but need a **serverless endpoint** instead of raw static hosting
+- Your data changes frequently and you want to **trigger updates via webhooks** from other systems
 
 ---
 
@@ -141,3 +172,4 @@ api-out/            # generated JSON (also configurable via Configuration)
 - Read the **CLI Commands** to learn each flag
 - Learn the **Routing** model (static, dynamic, catch-all, remote)
 - Use **data()** and **paths()** to shape your endpoints
+- Explore the **[Cloudflare Worker + R2 adapter](./serverless/cloudflare-adapter)** if you want StatikAPI behind a serverless Worker with a build webhook