Skip to content

feat: newsletter-page - Add a dedicated Brevo signup experience #213

Open

Description

@ashleyshaw

Feature Summary

Deliver the dedicated newsletter page, optional Brevo double-opt-in signup and a dedicated newsletter thank-you page. Thank-you ownership expands this issue’s scope; the existing M estimate remains unchanged and has not been revalidated.

Linked Stories/Tasks

Parent: #374. Project: This One Time on Acid — book. Brevo integration, deployment and verification separate children.

Milestones & Timeline

No milestone, cycle, due date or release date requested.

Proposed Solution

Add a newsletter page under src/app/components/pages/book-site/, /newsletter in src/app/routes.ts, centralised approved content/non-secret configuration and site-owned BEM/token styling. Follow existing route/SEO/data conventions and project Figma direction. Navigation placement remains a design decision.

Embed Brevo-generated supported signup from integration child; preserve provider form behaviour. No Netlify transport/fourth detector. Approved email/consent/privacy wording explains double opt-in. Initial acknowledgement says confirmation is required, never completed subscription. This issue owns the newsletter thank-you page, separate from draft acknowledgement in #208. Exact route and provider-return behaviour require agreement with #209.

Review keyboard, focus, responsive dimensions and provider-controlled presentation independently; if iframe chosen, descriptive accessible title and no assumption parent CSS can style cross-origin content or inspect state. Preserve protected images, mobile/themes/reduced motion. Do not fabricate success from React click handler.

Linked Stories/Tasks

No PR linked. Existing newsletter/style-guide examples remain demonstrations.

Milestones & Timeline

Release timing remains unset.

Acceptance Criteria

  • Thank-you messaging distinguishes a pending request from evidenced confirmed subscription; direct/repeated visits do not establish subscription or conversion.
  • Copy guarantees no cadence, chapter-update schedule, publication date, pre-order benefit or manuscript-access entitlement.
  • Measurement implementation waits for approved event/privacy definitions.

Trace to REQ-012 and AC-013.

  • /newsletter renders through navigation, direct load and reload.
  • Supported Brevo embed, not mock/Netlify submission.
  • Initial feedback requires email confirmation; pending requests never called subscribed.
  • Invalid/failed provider outcomes understandable without false success.
  • Approved consent/privacy/unsubscribe information, no invented extra personal fields.
  • Keyboard/focus/embed title/mobile/site-owned theme presentation reviewed.
  • No API secrets, fourth detector, Function/custom bridge or cross-form enrolment.
  • All acceptance criteria met
  • Documentation/changelog updated
  • Tests added/updated
  • PR uses correct branch prefix (feat/)
  • Labels/types match org standards
  • PR description updated with relevant details
  • Changelog entry prepared for PR (if applicable)
  • Labels/types match org standards

Designs / References

Routes, Brevo signup/embed, existing project Figma Make and repository AGENTS.md/CSS architecture.

Dependencies

Generated Brevo embed, authorised account/list, approved copy/privacy reference and verified SPA deployment. Navigation/design handoff unresolved. Existing draft reader /ebook proposal remains To be decided, unrelated to newsletter confirmation.

Testing Approach

Direct/reload route, metadata, keyboard/focus/mobile/theme and truthful provider outcomes. Verify controlled subscription in Brevo rather than relying on frontend appearance.

Additional Context

React/Vite, no existing /newsletter route in inspected source. New page is approved scope; not automatic enrolment of draft/waitlist/contact senders. LightSpeed Feature defaults retained with Backlog/status:needs-triage conflict disclosed.


Definition of Ready (DoR)

  • Problem statement and outcome defined
  • Acceptance criteria written (Given/When/Then)
  • Designs/specs/references attached (if relevant)
  • Dependencies mapped
  • Estimate added
  • Stakeholders/approvers listed
  • Milestone/iteration assigned (if applicable)

Definition of Done (DoD)

  • All acceptance criteria met
  • Feature implemented and tested
  • Tests added/updated; CI green
  • Accessibility: WCAG 2.2 AA compliance verified (semantic HTML, keyboard support, colour contrast)
  • Security: input validated, output escaped, no OWASP Top 10 vulnerabilities
  • Performance: no measurable regression introduced
  • Documentation/changelog updated if needed
  • Feature toggles/rollout considered
  • QA verified/UAT approved (if applicable)
  • Release notes prepared; monitoring/alerts set
  • Branch prefix is correct (feat/)
  • Branch deleted after merge
  • Linked issue(s) updated with latest status and closed after merge,
  • The related epic should not be closed, instead updated with a comment to reflect the closed issue

Unanswered clarification questions

These questions clarify the approved newsletter page and its design handoff; provider configuration remains owned by #209.

  1. Where should /newsletter appear in site navigation, and which retained pages should link to it?
  2. Which page headline, explanatory copy and call to action are approved?
  3. Which design reference should govern the page layout and site-owned responsive presentation?
  4. Who approves the design and navigation placement, and what handoff evidence is required?
  5. Which approved consent, privacy and confirmation wording from feat: newsletter-integration - Configure Brevo embedded double opt-in #209 must the page reflect?

Related project document: Book website — Newsletter thank-you: content and author questions

Metadata

Metadata

Assignees

Type

No type

Fields

Priority

None yet

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions