I have full context. I'll build a reusable pillar template (shared data + section components), then create two pages: /body as the populated example and /glow as the empty-state example. I'll also wire the homepage pillar grid to the new routes.

Now I'll create the two example pages and wire the homepage pillars grid to the new routes.

Built a single reusable pillar template that drives both routes. The shared sections (PillarHero, PillarArticlesSection, PillarEmptyState, OtherPillarsSection) live under components/pillar/, and a single lib/pillars.ts is now the source of truth for pillar metadata so the homepage grid, the "Also on Guide Kin" row, and any future pillar page stay in sync. View the populated example at /body (cream hero → featured + 6-card grid → mist "Five other things" row → sage newsletter) and the empty-state variant at /glow (cream hero → centered cream signup card on mist → other-pillars row → sage newsletter). Article images use a soft mist/cream gradient placeholder with the pillar name in tracked uppercase, signaling the slot without competing with the headlines.

Now I'll point the prominent "Join your kin" CTAs across the site to /subscribe so this becomes the conversion destination.

The /subscribe page is live and matches the rest of the site exactly: shared header and footer, cream hero with the Subscribe eyebrow, sage Source Serif headline, and ink subhead. The form sits in a centered cream card with a Stone border at max-w-[600px], structured as five fenced parts (fieldset/legend) — Who you are, What you want to read about (six pillar selection cards from lib/pillars.ts that toggle to a sage border on mist background), How should we reach you with two unchecked-by-default consent rows for email and SMS, an expandable "SMS messaging & data policy" disclosure that retains every TCPA/CTIA legal substance point in slightly warmer voice, and the full-width sage submit with amber Terms/Privacy links. A mist-toned three-column trust band closes the page, and I rewired the homepage hero CTA, About CTA, header Subscribe button, and footer Subscribe link to point at /subscribe so every conversion path lands here.