Build reusable email content, keep edits in a draft, and publish a known version when it is ready. ZSend makes the boundary between editing and sending visible.
Repository checkThe checked-in workflow is draft, edit, publish, and version listing.
Template edits are kept as unpublished changes. A send that references a template uses its published version, so the content in production stays deliberate while a new version is being prepared.
Templates have human-readable slugs and version history. Application code can keep referring to the same template while the team publishes improvements behind that reference.
The repository includes a React Email guide using `@zsend/sdk` and `@react-email/render`. Render component-based email in your application, then pass the resulting HTML to ZSend.
Join the ZSend waitlist and help shape an email workflow that keeps application code, content, and provider context together.