Skip to content

roadmap: wedding-ready by May 2027 #91

Open
7 of 9 issues completed
Open

Description

@devantler

🤖 Generated by the Daily AI Assistant

Problem

The wedding-app has all core features (login, RSVP, room booking, program, gallery, admin view) and is production-deployed. The wedding is May 16, 2027. The product direction shifted from feature-delivery to polish, reliability, and event operations: ensuring the app holds up under real guest traffic, that the couple can act on RSVP data efficiently, and that the guest experience is accessible and fast on any device.

Phase 1 — MVP → wedding-ready ✅ DELIVERED

Three themes closed the gap from MVP to wedding-ready:

  1. Guest experience quality — accessibility and performance.
  2. Administrative tools — the couple can act on RSVP data.
  3. Ops reliability — lightweight quality gates to catch regressions before guests arrive.

Children

All four shipped. The admin view also gained an at-a-glance summary (attending / declined / pending / bookings) and per-pair dietary + booking detail. The app is HA (3-instance CloudNativePG, 2 app replicas + PDB + topology spread), backed up daily to R2 with PITR, and hardened (restricted securityContext, NetworkPolicy, External-Secrets-managed admin code).

Phase 2 — operations & polish (post-MVP)

Strategy-review assessment (2026-06-22): the app is mature and well-built; with ~11 months to the wedding and only 14 guest pairs, Phase 2 is intentionally small — targeted ops-reliability and optional UX polish, not new feature surface. Over-scoping here would be manufactured work.

Children / candidates

Rough size

Phase 2 is ~1–2 small ready items (#133, #100) plus two optional candidates the couple may choose to skip. Suggested order: #133 → #100.

Activity

  1. devantler commented on Jun 10, 2026

    @devantler
    ContributorAuthor

    🤖 Generated by the Daily AI Assistant

    Implementation order & notes

    Suggested order: #92 → #93 → #94 → #95

    #92 (a11y guard): Start here — zero CI changes needed (runs in existing npm run test:e2e). Fixes any existing violations before the other changes add new routes.

    #93 (RSVP export): Simple server-only CSV endpoint. Prerequisite: a real DB connection for manual verification, but unit tests work with the mock layer.

    #94 (RSVP deadline): Build after #93 so the admin view already shows the closed state clearly. The deadline env var pattern is additive — safe to merge independently.

    #95 (Lighthouse budget): Last, since it depends on the final build state and is most likely to need threshold tuning. If the Node adapter + Lighthouse port-binding proves unreliable in CI, fall back to bundlesize and track as a follow-up.

    What was verified NOT needed:

    • Secrets migration → already done (deploy/ uses admin-code-externalsecret.yaml + platform openbao SecretStore; no SOPS)
    • copilot-instructions.md → already present in .github/
    • New CI workflow changes → all features work within the existing ci.yaml structure
  2. added theissue type on Jul 19, 2026
  3. moved this to 📥 Backlog in 🌊 Project Boardon Jul 25, 2026
  4. devantler commented on Oct 17, 2026

    @devantler
    ContributorAuthor

    🤖 Generated by the Agentic Engineer (interactive Claude Code session)

    Strategy review, 2026-10-17

    Where the app is. Feature-complete and in the polish and reliability phase this epic describes. Every child linked here is closed, and so are both Phase 2 candidates in the body (the backup restore drill #133 and the Core Web Vitals budget #100). Recent work hardened delivery: one declared Node toolchain (#388), release of runtime and base-image updates (#408), and two RSVP and admin fixes today (#410, #411).

    Delivery is still the weak link. The latest release is v1.15.19 (2026-10-11). #408 and today's fixes merged after it, and the release runs for them are queued behind saturated Actions runners, not failing. #407 stays open until a release that includes the SvelteKit 3 move (#402) is published; check that on the next run rather than re-opening the fix. Two gaps remain beyond #408:

    Roadmap, in the order I recommend:

    # Item Size State
    1 #407 Verify the first release after #408 — Waiting on the queued release runs
    2 #422 Release framework and compiler updates (Svelte, SvelteKit, Vite …), which #408 left out because they are dev dependencies that adapter-node bundles S Refined, ready to pull
    3 #423 Pin the Node base image by digest; without one Dependabot never proposes its patch updates, so #408's base-image rule cannot fire S Refined, ready to pull
    4 #176 Pass the Core Web Vitals budgets so the Lighthouse lane can become required M Now linked here; its old parent #100 is closed
    5 #291 Prove cold-start behaviour before any scale-to-zero M Backlog

    Nothing here needs new guest-facing features before the wedding; the remaining work keeps what guests use current and reliable.

    Upstream release review (key dependencies):

    Dependency Here What it means
    SvelteKit / adapter-node 3.x / 6.0.0 (#402) Not live until the queued release runs. The Dependabot ignore for adapter-node 5.5.5 is now stale (the app is on 6.0.0); it can go in a small chore.
    Svelte, Vite open #420 (5.57.2), #419 (8.3.4) Both are build(deps-dev) and will not release on their own; that is #422.
    Node 26-alpine, both stages Due to become LTS this month on the Node.js schedule; no action beyond #423.
    drizzle-orm, pg 0.45.4, 8.23.1 Runtime dependencies; #408 already releases them.
    TypeScript 6.x 7.0 is out; hold it until the Svelte tooling supports it, as business-site does (business-site#137).

    Decision for the maintainer: none required. If you want this epic to mirror the remaining work more tightly, its body could gain a Phase 3 list with the items above.

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

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    Fields

    No fields configured for Epic.

    Projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions