trails-cool/trails
1
1
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
trails/openspec/changes/transactional-emails/proposal.md
Ullrich Schäfer c7c1c275df
Add 8 proposed changes and old trails analysis 
Proposed changes (all with proposal, design, specs, tasks):
- app-navigation (9 tasks) — nav bars for both apps
- planner-landing-page (7 tasks) — standalone landing page
- planner-multiplayer-awareness (13 tasks) — participants, cursors, names
- changelog (13 tasks) — public changelog with "what's new"
- transactional-emails (15 tasks) — magic link + welcome emails
- planner-features (18 tasks) — no-go areas, notes, recovery, rate limits
- komoot-import (23 tasks) — Komoot tour import
- route-features (37 tasks) — sharing, multi-day, spatial, photos

Also adds docs/old-trails-analysis.md with feature analysis from the
older trails project.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
2026-03-25 03:57:20 +01:00

1.3 KiB
Raw Blame History

Why

Magic link login doesn't work in production — the link is logged to console but never emailed to the user. Registration works (passkey-based) but the fallback auth flow is broken. We need actual email delivery.

What Changes

  • Add a reusable email sending layer (@trails-cool/email or in-app module) with a provider-agnostic interface so future emails are trivial to add
  • Send magic link emails in production
  • Send a welcome email after registration
  • Use a transactional email provider (Resend, Postmark, or SMTP)
  • HTML email templates with plain-text fallback
  • Document email sending in the privacy manifest

Capabilities

New Capabilities

  • transactional-emails: Send templated emails via a provider-agnostic interface. Current emails: magic link login, welcome on registration. Designed for easy addition of future email types.

Modified Capabilities

  • journal-auth: Magic link flow now actually sends the email instead of logging to console

Impact

  • Files: New email module (lib or package), modified api.auth.login.ts, modified registration flow, email templates
  • Dependencies: One email provider SDK (e.g., resend or nodemailer)
  • Infrastructure: Email provider API key as env var, DNS records for sender domain verification
  • Privacy: Email addresses sent to third-party email provider — must document