Skip to main content

§ masterplan.md

Classy Digital Wedding Invite

A minimal, elegant invitation with RSVP form, photo timeline, travel details and a countdown to the big day.

All ideas
Classy Minimal

01

App overview and objectives

A private, elegant wedding site that replaces the paper card: the invitation, the story, the schedule, travel help and RSVP in one link the couple can send by message. It should feel personal and calm, never like a form.

02

The problem worth solving

Guests lose paper cards and hosts lose count of who is coming. One link solves both, and the couple keeps a permanent record of the day's plan and the guest list.

03

Target audience

  • Primary — Couples organising a wedding for 50-500 guests.
  • Secondary — Out-of-town guests who need travel, dress code and timing details.

04

Roles and permissions

  • Visitor — read-only public pages, can sign up.
  • Member — owns their own records, cannot see other users' data.

05

Core features

  • Personalised invitation link per guest or household with their name on the card
  • RSVP with attendance, meal choice, plus-ones and a message to the couple
  • Schedule with a timeline for each event day
  • Travel and stay page with hotels, directions and transport
  • Story page with a photo timeline of the couple
  • Host dashboard with live RSVP counts and export

Deliberately later

  • Gift registry
  • Photo upload wall after the event
  • Multi-language invitations

06

Technical stack

React site with a small database, per-guest tokenised links, no public sign-up.

Why: Guests must never create accounts; a signed personal link is both the authentication and the personalisation.

Alternatives: Off-the-shelf wedding platforms (instant, generic, ad-supported) or a plain form (cheap, loses elegance and tracking).

07

Conceptual data model

Wedding — couple, date, venues, theme, privacy setting

Guest — household, names, invite token, dietary notes, language

Rsvp — guest, attending, count, meal choices, message, updated_at

Event — wedding, name, time, venue, dress code

08

Integrations

  • Email or SMS for invitations and reminders
  • Map for venues
  • Image storage for photos

09

UI design principles

  • Generous whitespace, a two-font system, and a palette of three colours at most.
  • Photography and typography do the work; borders, shadows and gradients stay almost invisible.
  • Every screen has one clear primary action, placed in the same spot each time.

10

Security considerations

  • Invite tokens are long, unguessable, and can be revoked individually.
  • The site is noindex by default so a wedding is not publicly searchable.
  • Guest data is exportable and deletable by the couple after the event.

11

Development phases

Phase 1 — Prove the core

  • — Personalised invitation link per guest or household with their name on the card
  • — RSVP with attendance, meal choice, plus-ones and a message to the couple
  • — Schedule with a timeline for each event day
  • — Static content and design system in place
  • — Basic analytics

Phase 2 — Make it real

  • — Travel and stay page with hotels, directions and transport
  • — Story page with a photo timeline of the couple
  • — Host dashboard with live RSVP counts and export
  • — Accounts, sign-in and password reset
  • — Empty, loading and error states everywhere

Phase 3 — Polish and launch

  • — Performance, accessibility and SEO pass
  • — Legal pages, contact route and 404 handling
  • — Wire up: Email or SMS for invitations and reminders
  • — Wire up: Map for venues

Phase 4 — Grow

  • — Gift registry
  • — Photo upload wall after the event
  • — Multi-language invitations

12

Challenges and solutions

Risk — Guests ignore the RSVP

Solution — One-tap yes/no straight from the message, with a reminder schedule the couple controls.

Risk — Elderly guests struggle with the link

Solution — Very large type, no login, and a printable fallback card.

Risk — Last-minute changes

Solution — Editable schedule with a change banner and optional notification to all guests.

13

Future expansion

  • A reusable product for other couples
  • Vendor coordination view
  • Live-stream page for remote guests

14

Page list (13 pages)

  1. 01 AUTH Invite — The personalised card and the single RSVP call to action.
  2. 02 PUBLIC Story — How the couple met, as a quiet photo timeline.
  3. 03 PUBLIC Schedule — Every event, time and dress code.
  4. 04 PUBLIC RSVP — Attendance, meals and message.
  5. 05 PUBLIC Travel — Hotels, directions and transport.
  6. 06 AUTH Sign up — Create an account with email or a social provider.
  7. 07 AUTH Log in — Return to the account, with error and lockout states.
  8. 08 AUTH Reset password — Request a reset link and set a new password.
  9. 09 APP (signed in) Account settings — Profile, email, password, language and delete account.
  10. 10 PUBLIC Contact — Contact form plus real address, phone and email.
  11. 11 LEGAL & SYSTEM Privacy policy — What data is collected, why, and how to remove it.
  12. 12 LEGAL & SYSTEM Terms of service — Rules of use, liability and account termination.
  13. 13 LEGAL & SYSTEM 404 not found — Friendly dead end with search and links back.

15

Page map

PUBLIC       AUTH               APP (signed in)      LEGAL & SYSTEM
───────────  ─────────────────  ───────────────────  ───────────────────
├─ Story     ├─ Invite          └─ Account settings  ├─ Privacy policy
├─ Schedule  ├─ Sign up                              ├─ Terms of service
├─ RSVP      ├─ Log in                               └─ 404 not found
├─ Travel    └─ Reset password
└─ Contact

key flows:
  Invite ──▶ RSVP
  Schedule ──▶ Travel
  RSVP ──▶ Schedule