email-template

To create consistent React Email templates, you structure them within a dedicated workspace package using domain-based organization like src/user/ or src/billing/, enforce kebab-case filenames, and define strict exports including Props and PreviewProps interfaces for reusability.

The best way to organize frontend email templates is by grouping them into domain-specific directories such as src/order/ or src/user/ within a centralized email-templates package, which ensures clear ownership and high template reuse across different projects.

To make a new React Email component discoverable in the template registry, you must run the codegen regeneration step immediately after creating the template file to refresh the TemplateMap and register the new component.

A React Email template component requires strict exports: a Props interface, a named component, a PreviewProps object, and a default export, with all styling defined using React.CSSProperties to ensure standardization.

No, styling must be defined as React.CSSProperties. This enforces strict styling standards across the workspace's email-templates package, ensuring that all transactional emails remain consistent and accessible.

Your new email template does not show up in the TemplateMap because the codegen regeneration step has not been run. You must execute this refresh process after adding a template to update the central registry.