Publish content with no redeploy

The recipe — paste this to your AI

# Recipe — serve blog + FAQ LIVE from your dashboard (publish with no redeploy)

Out of the box, `/blog` and `/faq` render the SAMPLE content in `lib/content/blog.ts` and
`lib/content/faq.ts` — fine for day zero, embarrassing on day thirty. The framework can serve
both **live from your Genesis org's CMS**: publish a post in the dashboard and the site
updates within minutes, no deploy, no code.

## Step 1 — point the site at your org (one config block)

In `site.config.ts` (your lane), un-comment the `content` block:

```ts
content: {
  organizationId: 'your-genesis-org-uuid',   // defaults to contact.organizationId if set
  // apiOrigin defaults to your configured API origin — set only if it differs
},
```

That single block flips `/blog` and `/faq` from static samples to live data (the resolution
logic and its build-time-failure fallbacks are documented in `lib/content/live.ts` — the site
degrades to whatever it fetched last rather than breaking if the API is briefly unreachable
at build time).

## Step 2 — publish real content in the dashboard

Dashboard → **Content**: write posts (title, slug, body, tags, publish state) and FAQs. Only
**published** items serve; drafts stay invisible. Preview links work before publishing.

## Step 3 — clean up and wire the nav

1. Replace the sample arrays in `lib/content/blog.ts` / `faq.ts` with empty arrays or leave
   them — once `content` is configured they are the offline fallback only.
2. Add Blog to your nav if it isn't there: `site.config.ts → marketing.nav` →
   `{ label: 'Blog', href: '/blog' }`.
3. Deploy once (the config edit is a code change). From then on, publishing is dashboard-only.

## Verify it's really live

Publish a test post in the dashboard, wait ~5 minutes (ISR revalidation), reload `/blog` on
the LIVE site — the post should appear with no deploy having run. If it doesn't, check the
org id and that the post is published, then see `DEPLOY.md` Gotcha 7 (slow/unreachable origin
at build time).

## Bonus

The same content substrate feeds the AI coach — FAQs you publish become answers the coach can
serve members. One editorial effort, two surfaces.