Devotional subscriber management (UI + MongoDB recipient list)

[JoshuaVSherman]

Placeholder — no firm plans yet. Captured during discussion of web-jam-tools#69. Flesh out before any execution.

Idea

Replace the hardcoded single recipient in the daily-devotional sender with a managed subscriber list:

• A UI to add/remove devotional recipients.
• A MongoDB collection (via web-jam-back) to store them.
• The daily sender fetches the list and sends to all subscribers.

Context / relationship to web-jam-tools#69

• web-jam-tools#69 deploys the daily-devotional generator to a laptop-independent cloud runtime (Deno Deploy + Deno.cron) with the recipient hardcoded (joshua.v.sherman@gmail.com).
• That deploy is intentionally a clean seam for this: today sendEmail is called once with one address; here it becomes "fetch the list, loop and send." No rework of Add a picture slideshow to the homepage, but always have it start with the church building pic #69 expected.
• The generator lives in web-jam-tools/src/devotional/send_daily_devotional.ts (Deno/TS); the subscriber data + API would live in web-jam-back (MongoDB), surfaced through a CollegeLutheran UI.

Open questions (to settle later)

• Self-signup (public subscribe form) vs admin-only add?
• Unsubscribe flow — required by CAN-SPAM once sending to people other than Josh.
• Auth: who can manage the list (admin UI vs public)?
• web-jam-back schema: subscribers collection shape (email, name, status, createdAt, unsubscribe token?).
• How the deployed Deno job authenticates to web-jam-back to fetch the list.
• Double opt-in / email confirmation?