feat: add branded Supabase account email templates - #188
Merged
Merged
Conversation
5 tasks
5 tasks
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
One Concept's signup, recovery, and password-changed emails now have a consistent text masthead, concise account copy, and a clickable Coding Moves organization link. This PR delivers the three reviewed HTML templates independently of the deferred SMTP/Resend setup in #187. No domain purchase is required to install these templates with the configured sender.
Signup and recovery preserve Supabase's confirmation URLs in both the main button and copyable fallback. The password-changed notification confirms the completed change and directs unrecognized changes to Forgot password and the app's published support email. All templates use inline styles, presentation tables, system fonts, and no external assets. The guide gives exact subjects, installation steps, and the separate security-notification toggle.
Validation: the extracted HTML is byte-for-byte identical to the previously validated source. All 60 local Chromium scenarios passed for that source: 48 signup/recovery scenarios and 12 password-changed scenarios, covering 320/390/600/960px, normal/doubled/stripped styles, and normal/long verification URLs where applicable. Checked links, fallback URLs, text spacing, styled overflow, action sizes, and no external resource requests; inspected mobile, desktop, and enlarged-text previews. Rechecked the existing app redirect contract, local Markdown links/anchors, and git diff --check. Backend/mobile tests were not run because only standalone HTML and documentation changed.
This PR is ready for code review and merge independently of provider activation. Merging or releasing the app does not install the templates in Supabase. After copying the HTML into the dashboard, verify real signup, recovery, and the enabled password-changed notification with test accounts. Real inbox rendering/delivery remain unverified. Supabase's default sender is restricted to project-team addresses and currently two emails/hour; other users require configured custom SMTP, such as the owner's Gmail setup. No SMTP settings, production templates, or app behavior are changed here.
The nine original template commits are preserved individually on this branch; setup and handoff documentation have separate commits. The original draft history remains intact.
Refs #171 (template portion) and #152 (delivery remains deferred in #187). This PR does not close the delivery issues or trigger a production release.