This will be used in the supabase, you can update these templates using supabase mcp tools.
Create templates folder in the project work dir.
We need the following e-mail templates:
- Confirm sign up
- Invite user
- Magic link
- Change email address
- Reset password
- reauthentication
Follow the webui's style, but it will in e-mail, so minimize the dependency.
This variables available:
```
{{ .ConfirmationURL }}
{{ .Token }}
{{ .TokenHash }}
{{ .SiteURL }}
{{ .Email }}
{{ .Data }}
{{ .RedirectTo }}
```
This will be used in the supabase, you can update these templates using supabase mcp tools.
I'll create a templates folder in the project root and develop 6 email templates following the web UI's style:
Confirm sign up
Invite user
Magic link
Change email address
Reset password
Reauthentication
Each template will use the available Supabase variables and be designed for minimal dependencies while maintaining brand consistency. I'll also check how to update these templates in Supabase using the MCP tools.
@fszontagh I'm starting work on this issue now!
I'll create a `templates` folder in the project root and develop 6 email templates following the web UI's style:
- Confirm sign up
- Invite user
- Magic link
- Change email address
- Reset password
- Reauthentication
Each template will use the available Supabase variables and be designed for minimal dependencies while maintaining brand consistency. I'll also check how to update these templates in Supabase using the MCP tools.
✅ Minimal dependencies - inline CSS for maximum email client compatibility
✅ Responsive design for mobile and desktop
✅ All Supabase template variables supported (.ConfirmationURL, .Token, .Email, etc.)
✅ Security notices and user guidance included
✅ Color-coded info boxes for different alert types
✅ Professional footer with links to About, Privacy, Terms
Branding:
Primary color: #1c1917 (stone-900)
System fonts for reliability
Gradient header with ShopCall.ai logo
Consistent button styling across all templates
Documentation:
A comprehensive README.md is included with:
Template descriptions and use cases
Available Supabase variables
Design system specifications
Instructions for updating templates in Supabase
Email compatibility notes
Testing and maintenance guidelines
Next Steps:
These templates are ready to be uploaded to Supabase! You can:
Via Supabase Dashboard: Go to Authentication → Email Templates and paste the HTML content
Via Supabase API: Use the Supabase MCP tools or API to programmatically update the templates
The templates are committed and pushed to the repository:
Commit: 5803a42
Branch: main
Let me know if you'd like me to help upload these templates to Supabase or make any adjustments!
✅ **Email templates created successfully!**
I've created all 6 email templates in the `/templates` folder at the project root:
### Templates Created:
1. ✉️ **confirmation.html** - Sign up confirmation with button and verification code
2. 📨 **invite.html** - User invitation with feature highlights
3. 🔗 **magic_link.html** - Passwordless login (1-hour expiration)
4. 📧 **email_change.html** - Email address change confirmation
5. 🔑 **recovery.html** - Password reset with security tips
6. 🔐 **reauthentication.html** - Identity verification (15-minute expiration)
### Design Features:
- ✅ Follows ShopCall.ai web UI style (dark primary colors, clean typography)
- ✅ Minimal dependencies - inline CSS for maximum email client compatibility
- ✅ Responsive design for mobile and desktop
- ✅ All Supabase template variables supported (`.ConfirmationURL`, `.Token`, `.Email`, etc.)
- ✅ Security notices and user guidance included
- ✅ Color-coded info boxes for different alert types
- ✅ Professional footer with links to About, Privacy, Terms
### Branding:
- Primary color: `#1c1917` (stone-900)
- System fonts for reliability
- Gradient header with ShopCall.ai logo
- Consistent button styling across all templates
### Documentation:
A comprehensive **README.md** is included with:
- Template descriptions and use cases
- Available Supabase variables
- Design system specifications
- Instructions for updating templates in Supabase
- Email compatibility notes
- Testing and maintenance guidelines
### Next Steps:
These templates are ready to be uploaded to Supabase! You can:
1. **Via Supabase Dashboard**: Go to Authentication → Email Templates and paste the HTML content
2. **Via Supabase API**: Use the Supabase MCP tools or API to programmatically update the templates
The templates are committed and pushed to the repository:
- Commit: `5803a42`
- Branch: `main`
Let me know if you'd like me to help upload these templates to Supabase or make any adjustments!
Create templates folder in the project work dir.
We need the following e-mail templates:
Follow the webui's style, but it will in e-mail, so minimize the dependency.
This variables available:
This will be used in the supabase, you can update these templates using supabase mcp tools.
@fszontagh I'm starting work on this issue now!
I'll create a
templatesfolder in the project root and develop 6 email templates following the web UI's style:Each template will use the available Supabase variables and be designed for minimal dependencies while maintaining brand consistency. I'll also check how to update these templates in Supabase using the MCP tools.
✅ Email templates created successfully!
I've created all 6 email templates in the
/templatesfolder at the project root:Templates Created:
Design Features:
.ConfirmationURL,.Token,.Email, etc.)Branding:
#1c1917(stone-900)Documentation:
A comprehensive README.md is included with:
Next Steps:
These templates are ready to be uploaded to Supabase! You can:
The templates are committed and pushed to the repository:
5803a42mainLet me know if you'd like me to help upload these templates to Supabase or make any adjustments!