sample post
We're building the Blueprint Code CMS (Payload 3 on Next 16) in this repo. Phases 1–4 are done and in production. Start Phase 5 (the blog).
https://media.blueprintcode.ai/media/9aeb89f0-2e32-482c-a1cb-655280e211ea/parv-jain-1d3dad56.png
Before doing anything else, read docs/CMS-HANDOFF.md in full — it is the authoritative state of the project, the conventions, the environment, the known gotchas, and the complete Phase 5 spec. Follow it exactly:
- tests first for every pure module (Vitest, `npm test`), then implement; keep tsc and `npm run build` clean
- schema changes only via `npm run migrate:create <name>` → review → `npm run migrate` (dev branch), then `npm run generate:types`
- restart the dev server (bpcode-dev launch config) after collection/hook changes
- gate all public blog routes behind a new BLOG_PUBLIC flag; nothing on the public site changes until I flip it
- never touch production data from local (db-guard); rebase before every push
- verify end to end locally with curl + the browser pane (section 6 of the handoff), then push and verify production as described in section 8 "Deploy"
Work in this order: (1) Posts/Categories/Authors collections + migration + tests, (2) public /blog routes with ISR, SEO metadata, JSON-LD, RSS, sitemap and blog-preview, (3) admin polish (dashboard panel, SEO preview for posts, writer-role check), (4) scripts/import-insights.ts run on the dev branch as drafts, (5) push, verify prod with the blog still gated, update docs/CMS-HANDOFF.md, and give me a summary of what I can now do in the admin.
Commit as you go with clear messages. Ask me only when a decision is genuinely mine (e.g. launching the blog).
Before doing anything else, read docs/CMS-HANDOFF.md in full — it is the authoritative state of the project, the conventions, the environment, the known gotchas, and the complete Phase 5 spec. Follow it exactly:
- tests first for every pure module (Vitest, `npm test`), then implement; keep tsc and `npm run build` clean
- schema changes only via `npm run migrate:create <name>` → review → `npm run migrate` (dev branch), then `npm run generate:types`
- restart the dev server (bpcode-dev launch config) after collection/hook changes
- gate all public blog routes behind a new BLOG_PUBLIC flag; nothing on the public site changes until I flip it
- never touch production data from local (db-guard); rebase before every push
- verify end to end locally with curl + the browser pane (section 6 of the handoff), then push and verify production as described in section 8 "Deploy"
Work in this order: (1) Posts/Categories/Authors collections + migration + tests, (2) public /blog routes with ISR, SEO metadata, JSON-LD, RSS, sitemap and blog-preview, (3) admin polish (dashboard panel, SEO preview for posts, writer-role check), (4) scripts/import-insights.ts run on the dev branch as drafts, (5) push, verify prod with the blog still gated, update docs/CMS-HANDOFF.md, and give me a summary of what I can now do in the admin.
Commit as you go with clear messages. Ask me only when a decision is genuinely mine (e.g. launching the blog).
Before doing anything else, read docs/CMS-HANDOFF.md in full — it is the authoritative state of the project, the conventions, the environment, the known gotchas, and the complete Phase 5 spec. Follow it exactly:
- tests first for every pure module (Vitest, `npm test`), then implement; keep tsc and `npm run build` clean
- schema changes only via `npm run migrate:create <name>` → review → `npm run migrate` (dev branch), then `npm run generate:types`
- restart the dev server (bpcode-dev launch config) after collection/hook changes
- gate all public blog routes behind a new BLOG_PUBLIC flag; nothing on the public site changes until I flip it
- never touch production data from local (db-guard); rebase before every push
- verify end to end locally with curl + the browser pane (section 6 of the handoff), then push and verify production as described in section 8 "Deploy"
Work in this order: (1) Posts/Categories/Authors collections + migration + tests, (2) public /blog routes with ISR, SEO metadata, JSON-LD, RSS, sitemap and blog-preview, (3) admin polish (dashboard panel, SEO preview for posts, writer-role check), (4) scripts/import-insights.ts run on the dev branch as drafts, (5) push, verify prod with the blog still gated, update docs/CMS-HANDOFF.md, and give me a summary of what I can now do in the admin.
Commit as you go with clear messages. Ask me only when a decision is genuinely mine (e.g. launching the blog).