For a lot of people, an email is the first — and sometimes only — impression they get of Datum. A waitlist confirmation, a welcome note, a heads-up that someone signed in from a new device: small moments, but they're often where trust is won or lost. This repo is where those emails live.
Screenshots below are committed alongside each template change, so what you see is always what's actually in main.
Platform Invitation — the very first hello, inviting someone to join Datum's private beta (click to preview)
User Invitation — welcoming a new teammate into an organization on Datum (click to preview)
User Approved — the good news that someone's access request has been approved (click to preview)
User Rejected — a considerate no, when an application to Datum wasn't approved (click to preview)
User Waitlist — letting someone know they're in line and we haven't forgotten them (click to preview)
User Welcome — the front-door greeting for a brand-new Datum user (click to preview)
Suspicious Sign-in — a quiet tap on the shoulder when we spot a sign-in from somewhere unfamiliar (click to preview)
Need wording changed on an existing email, or a brand-new template entirely? You don't need to write any code — open an issue:
- Content / Wording Change Request — tweak the copy on an existing template (example issue, example PR).
- New Email Template Request — describe a new email and when it's sent (example issue, example PR).
If you're a member of the team, Claude automatically drafts a PR as soon as you submit the issue. Anyone else's request is triaged by a maintainer first, who adds the ai-draft label to have Claude take a pass at it — that same label re-triggers a run that failed or fell short. Either way, a draft PR still needs human review (copy, brand, and — for new templates — layout) before it merges.
Want something changed on a draft? A maintainer can reply @claude with the feedback — on the issue or the PR itself — and Claude pushes a follow-up commit to the same PR.
Once that PR is merged, it's not live for real users yet — see "How do I actually release this?" for the (no-code) steps to publish it.
Setup instructions and how to create or update a template live in CONTRIBUTING.md. The release process is documented in RELEASING.md.