KofTwentyTwo/nuncio-website
3
0 Fork 0
Code Issues Pull Requests 14 Actions Packages Projects Releases Wiki Activity

site: 'Notify me at launch' signup as the primary CTA (no Download) #28

New Issue
Closed
opened 2026-07-28 15:48:30 +00:00 by KofTwentyTwo · 1 comment
KofTwentyTwo commented 2026-07-28 15:48:30 +00:00 (Migrated from github.com)
Copy link
Copy source

Context & goal

Give interested visitors an honest way to convert on the vision (instead of a fake Download).

Requirements

  • Add a "Notify me at launch" email capture using a static/Next-friendly provider (Buttondown, Formspree, or Resend via a route handler) — provider/account is a PO decision; wire the key via env vars, never commit secrets.
  • If no provider is chosen yet, fall back to a prominent "Watch/Star on GitHub" + roadmap CTA. Either way, no "Download".
  • Honest success/error states (no fake "You're subscribed" without a real submit).

Acceptance criteria

  • A working signup (or GitHub/roadmap fallback) is the primary conversion CTA site-wide; no "Download".
  • No secrets committed; provider key via env.
  • Build + lint pass.

Size: S–M.

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.

## Context & goal Give interested visitors an honest way to convert on the vision (instead of a fake Download). ## Requirements - Add a **"Notify me at launch"** email capture using a static/Next-friendly provider (Buttondown, Formspree, or Resend via a route handler) — provider/account is a PO decision; wire the key via env vars, never commit secrets. - If no provider is chosen yet, fall back to a prominent **"Watch/Star on GitHub"** + roadmap CTA. Either way, no "Download". - Honest success/error states (no fake "You're subscribed" without a real submit). ## Acceptance criteria - [ ] A working signup (or GitHub/roadmap fallback) is the primary conversion CTA site-wide; no "Download". - [ ] No secrets committed; provider key via env. - [ ] Build + lint pass. Size: S–M. --- **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:42 +00:00 (Migrated from github.com)
Copy link
Copy source

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.
No Branch/Tag Specified
Labels
Clear labels
bug
Something isn't working
 content
Copy/content change
 dependencies
Pull requests that update a dependency file
 documentation
Improvements or additions to documentation
 duplicate
This issue or pull request already exists
 enhancement
New feature or request
 github_actions
Pull requests that update GitHub Actions code
 good first issue
Good for newcomers
 help wanted
Extra attention is needed
 honesty
Truth-in-marketing: remove/replace fabricated or unshipped claims
 invalid
This doesn't seem right
 javascript
Pull requests that update javascript code
 question
Further information is requested
 story
Site story: full spec for an implementer
 wontfix
This will not be worked on
No labels content story
Milestone
No items
No Milestone North-star vision site
Projects
Clear projects
No projects
Assignees
Clear assignees
forge-recovery (Forge Recovery) james.maes (James Maes)
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: KofTwentyTwo/nuncio-website#28