Skip to main content

Design System Code Workflows and Betty for Miro Briefs

Nicki Pabst
Nicki Pabst
Co-founder & Email wizard

This week helps teams keep coded Design System modules ready for marketers, lets Betty use approved Miro content during Campaign work, and fixes issues that could block previews, translations, checks, and older Campaigns.

Design Systems can now live in your repository​

Teams where developers maintain Design Systems in Git can now manage versions with the Better CLI, test changes in Better Email, and push a version for Candidate testing. Publishing to Live, the version marketers use for production Campaigns, still happens deliberately inside Better Email after review.

The new local preview loop lets developers edit files on their machine and preview the result in the same module and settings experience marketers use when building Campaigns. Maizzle and React Email teams can also generate Better Email Design System files from existing component projects, so they can keep their current workflow while making the finished modules editable for marketers.

Betty can work from approved Miro boards​

Betty can now connect to workspace-approved content sources, starting with Miro. After a source is connected in Settings, Betty can use approved Miro boards for campaign briefs, launch plans, messaging notes, and review context while helping build a Campaign.

When a Campaign is ready, Betty can add it back to a Miro board as a linked Campaign card with a preview image, so stakeholders can review the result alongside the brief. Admins control this separately: Betty can read from connected sources by default, while actions that change external sources stay off until an admin enables them.

Improvements​

  • Browser sign-in for the Better CLI attributes pushed Design System versions to the person who made the change instead of a shared API key.
  • New Design Systems include a valid Template Base with the required content area, so admins can save and preview immediately.
  • Design System checks now warn when a color field has no preset options and would not be editable for marketers.
  • VS Code users get Liquid suggestions across Template Base, global settings, shared settings, modules, repeatables, images, and links.
  • Microsoft Dynamics 365 Customer Insights - Journeys integrations can now sync Dataverse contact fields, including choice labels, so recipient fields, personalization, and segmentation use Journeys-compatible values.

Fixes​

  • Older Campaigns now restore editing, review, comments, previews, and quality checks the first time they are opened instead of failing to load.
  • Review checks now link directly to the failing field when a Campaign variant has missing or invalid values.
  • After the editor reconnects, Design System saves now keep the current editor session and clear stale save states.
  • Translations now include marketer-editable text from shared editable inputs, so localized Campaigns no longer miss those reused values.
  • Local Design System previews no longer fail when a color field has no preset options.