Skip to content

docs(home): footer newsletter, wired to the public subscribe endpoint - #177

Draft
soamdesai-tfh wants to merge 1 commit into
mainfrom
soam/docs3-qa2-7-newsletter
Draft

docs(home): footer newsletter, wired to the public subscribe endpoint#177
soamdesai-tfh wants to merge 1 commit into
mainfrom
soam/docs3-qa2-7-newsletter

Conversation

@soamdesai-tfh

Copy link
Copy Markdown
Contributor

Part of the Docs 3.0 QA round 2 series (with #171#176). Draft — blocked on worldcoin/company-website#4481.

Change

The Docs 3.0 footer includes the Subscribe to World Developers Newsletter block. It has been staged behind a comment since #163 because world.org's own form submits through a Next.js server action holding a server-side Braze token — a static Mintlify site can't keep that secret, and shipping a form with nowhere to post is a silent failure.

This PR turns the staged markup into a real component (/snippets/newsletter-form.jsx) posting to POST https://world.org/api/subscribe — the public endpoint proposed in worldcoin/company-website#4481:

  • Single attempt with a 10s bound; no retries (a retry could double-fire the marketing pipeline).
  • Explicit states: disabled button while sending, "Thanks — you're subscribed." on success, a visible error message on any failure — never a silent no-op. While #4481 is unmerged the endpoint 404s, so the form currently shows the error state by design.
  • type=email validation, privacy-notice consent copy per the design, stacks to one column below 900px.
  • Homepage only: Mintlify's theme footer on docs pages can't host custom markup, so the docs-page footer (from docs(footer): add the Docs 3.0 footer to docs pages #173) stays links-only even though the mock shows the newsletter there too — flagged for the design team.

Merge only after worldcoin/company-website#4481 (plus its rate-limit rule) is live.

Design

design

Implementation (local render, wired to the pending endpoint)

implementation

…be endpoint

The Docs 3.0 footer includes 'Subscribe to World Developers Newsletter'.
The block was staged behind a comment because a static Mintlify site
cannot hold world.org's server-side Braze token; it now ships as a real
form posting to POST https://world.org/api/subscribe
(worldcoin/company-website#4481). Single attempt with a 10s bound and
explicit success/error states — no retries (a retry could double-fire
the marketing pipeline) and no silent failures. Stacks below 900px.
@mintlify

mintlify Bot commented Sep 10, 2026

Copy link
Copy Markdown
Contributor

Preview deployment for your docs. Learn more about Mintlify Previews.

Project Status Preview Updated
world 🟢 Ready View Preview Sep 10, 2026, 6:54 PM

💡 Tip: Enable Automations to automatically generate PRs for you.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant