docs: add Campaigns OS Start path

[next-devin]

Adds a short Campaigns OS Start callout before the existing Page Kit quick start. It explains dashboard configuration, the Workspace map and Handoff, and developer or agent build, preview, and QA, while retaining Page Kit as the direct scaffolding path.

Validation: npm run build and npm run check passed. Current CI: build-and-validate passed; the Workers build is pending.

[cloudflare-workers-and-pages]

Deploying with    Cloudflare Workers

The latest updates on your project. Learn more about integrating Git with Workers.

Status	Name	Latest Commit	Preview URL	Updated (UTC)
✅ Deployment successful! View logs	developer-docs	066562c	Commit Preview URL Branch Preview URL	Sep 18 2026, 07:42 AM

[kilo-code-bot]

WARNING: The callout labels the Page Kit as "the manual path for starting a project," but the Page Kit is an automated scaffolding tool (campaign-init CLI), not a manual path. This also contradicts the immediately following paragraph (line 16), which correctly describes Page Kit as "direct project scaffolding," and the PR description, which says Page Kit is "retained as the direct scaffolding path." Consider rephrasing, e.g. "The Page Kit quick start below is the direct CLI scaffolding path for starting a project locally."

[kilo-code-bot]

Code Review Summary

Status: 1 Issue Found | Recommendation: Address before merge

Overview

Severity	Count
CRITICAL	0
WARNING	1
SUGGESTION	0

Issue Details (click to expand)

WARNING

File	Line	Issue
content/docs/campaigns/index.mdx	13	The Campaigns OS Start callout describes the Page Kit as "the manual path for starting a project," which mischaracterizes the automated campaign-init CLI and contradicts both line 16 ("direct project scaffolding") and the PR description ("retaining Page Kit as the direct scaffolding path").

Files Reviewed (1 file)

• content/docs/campaigns/index.mdx - 1 issue

Fix these issues in Kilo Cloud

---

_{Reviewed by minimax-m3 · Input: 0 · Output: 0 · Cached: 0}