Today, we released a bunch of improvements to MailMason鈥檚 workflow as well as the starter templates that ship with it. We've been blown away by the support we've received with MailMason. This has been a long time coming.
Improved integration with Postmark
- You can now push templates and layouts up to Postmark using the postmark-cli tool
- MailMason鈥檚 layouts are now compatible with Postmark layouts
Template design improvements
- 3 generic layout options to help you get up and running
- Each template now uses Nunito Sans as the main typeface. Fallback fonts for older versions of Outlook have also been considered.
- Dark mode support in all layouts. Works with email clients that support the
prefers-color-scheme:dark
media query.
Accessibility
- Background and text colors now pass AA contrast ratios defined by WCAG 2.0
- Added
role="presentation"
to container tables so that they are not unnecessarily read by screen readers
Codebase
- Upgraded node.js version to 10.16.0(LTS) in
.nvmrc
- Upgraded node.js packages
- Stylesheets are now compiled to
/dist/stylesheets
instead of/src/stylesheets
- Each layout comes with its own stylesheet for layout-specific theming
- Reorganized
/src
and/dist
folder structure.- Each template or layout is stored in its own folder
- Each template or layout has a
meta.json
file so that it can be uploaded to Postmark. This lets you control things like the name, alias, template type, etc. - Templates that are combined with layouts are compiled to
/dist/compiled
. CSS is also inlined by default with these templates. - Postmark specific templates and layouts are compiled to
/dist/postmark-layouts
and/dist/postmark-templates
. CSS is not inlined by default since Postmark handles it for you.
Upgrading to 1.0.0 from 0.X
We've put together a guide on how to migrate templates from an older version of MailMason to the latest version.
Thanks to those of you that use MailMason and continue to support this project 鉂わ笍