site: north-star content system (vision vs available-now signal + roadmap link) #20

New Issue

2026-07-28T15:48:18Z

KofTwentyTwo commented

2026-07-28 15:48:18 +00:00

(Migrated from github.com)

Context & goal

Foundational story — do this first. Give the site a small system for presenting the vision boldly while keeping the three guardrails. This is NOT about stamping "PLANNED" on everything (that kills the north star); it's about one clean, consistent way to signal "vision vs available-now" and to keep the in-development status + roadmap always one glance away.

Requirements

Add CONTENT-POLICY.md at the repo root capturing the north-star philosophy + the three guardrails (below).
Add a light, tasteful "In active development" signal used site-wide (e.g. a slim top ribbon or a consistent hero chip) that links to the roadmap — present, not apologetic, not screaming.
Add an optional, subtle "Available now" marker component the pages can use to distinguish the handful of things a developer can already do today (build + run the daemon/CLI from source) from the broader vision — used sparingly, not as a per-feature gate.
Add a single source of truth for what's genuinely available-now vs vision (e.g. src/content/status.ts) so pages don't hard-code it.
Fix the site repo README/description if it makes an "available today" or invented-data claim.

Acceptance criteria

CONTENT-POLICY.md committed; the in-development signal + roadmap link render on every route (tasteful, on-brand).
An "available-now" marker + a typed source of truth exist and are used by at least Home/Features.
Build + lint pass.

Size: M. Blocks the other site stories.

Governing philosophy — north star. This site sells the vision: what Nuncio will be. Present it boldly and aspirationally, as the destination we're building toward — do not water it down to "here's a broken pre-alpha." Only three hard guardrails apply:

Not available today. No "Download"/"Latest Release"/"install now". CTAs are "Notify me at launch", "Follow the build → GitHub", "See the roadmap →" (https://koftwentytwo.github.io/nuncio/roadmap/).
No invented data as real. Benchmarks must be genuinely measured (cite the source) or omitted — no "<10ms across 100,000+ emails" as if proven. UI mockups/renders are encouraged, but framed as product previews of the vision, not screenshots of a real running inbox with real people.
Status discoverable. A tasteful, consistent signal that this is in active development, plus a roadmap link, so a visitor understands it's what's coming and can see where we actually are.

Process: branch story/<slug> off the site's default branch; PR back; the PO reviews for vision quality AND the three guardrails before merge. npm run build + npm run lint must pass.

## Context & goal Foundational story — **do this first.** Give the site a small system for presenting the vision boldly while keeping the three guardrails. This is NOT about stamping "PLANNED" on everything (that kills the north star); it's about one clean, consistent way to signal "vision vs available-now" and to keep the in-development status + roadmap always one glance away. ## Requirements - Add `CONTENT-POLICY.md` at the repo root capturing the north-star philosophy + the three guardrails (below). - Add a light, tasteful **"In active development"** signal used site-wide (e.g. a slim top ribbon or a consistent hero chip) that links to the roadmap — present, not apologetic, not screaming. - Add an optional, subtle **"Available now"** marker component the pages can use to distinguish the handful of things a developer can already do today (build + run the daemon/CLI from source) from the broader vision — used sparingly, not as a per-feature gate. - Add a single source of truth for what's genuinely available-now vs vision (e.g. `src/content/status.ts`) so pages don't hard-code it. - Fix the site repo README/description if it makes an "available today" or invented-data claim. ## Acceptance criteria - [ ] `CONTENT-POLICY.md` committed; the in-development signal + roadmap link render on every route (tasteful, on-brand). - [ ] An "available-now" marker + a typed source of truth exist and are used by at least Home/Features. - [ ] Build + lint pass. Size: M. **Blocks the other site stories.** --- **Governing philosophy — north star.** This site sells the *vision*: what Nuncio *will be*. Present it boldly and aspirationally, as the destination we're building toward — do not water it down to "here's a broken pre-alpha." Only three hard guardrails apply: 1. **Not available today.** No "Download"/"Latest Release"/"install now". CTAs are "Notify me at launch", "Follow the build → GitHub", "See the roadmap →" (https://koftwentytwo.github.io/nuncio/roadmap/). 2. **No invented data as real.** Benchmarks must be genuinely measured (cite the source) or omitted — no "<10ms across 100,000+ emails" as if proven. UI mockups/renders are encouraged, but framed as **product previews of the vision**, not screenshots of a real running inbox with real people. 3. **Status discoverable.** A tasteful, consistent signal that this is in active development, plus a roadmap link, so a visitor understands it's what's coming and can see where we actually are. **Process:** branch `story/<slug>` off the site's default branch; PR back; the PO reviews for vision quality AND the three guardrails before merge. `npm run build` + `npm run lint` must pass.

KofTwentyTwo commented

2026-07-29 14:42:23 +00:00

(Migrated from github.com)

Implemented and merged in PR #30 (north-star relaunch, commit f567d9b).

Implemented and merged in PR #30 (north-star relaunch, commit f567d9b).

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: KofTwentyTwo/nuncio-website#20