Skip to main content
Once your organization has a component library, most of the work isn’t writing new component code (in MJML, the email-building language allGood uses). It’s opening the right block, changing the right part of it, and knowing what else in allGood will pick up that change. This article walks through the library’s inspection and authoring surfaces, and the version workflow underneath both. Prerequisites
  • Access to your organization’s Email Component library in allGood. If you don’t see one, ask whoever administers allGood for your team.
  • Familiarity with what’s safe to edit in a component. See Email components for the EDIT/LOCKED boundaries this article assumes.

​
Inspect and Author: the two sides of a component library

A component library’s navigation splits into two groups. Inspect covers Overview, History, Assets, and Notes: a component’s current state, its past versions, and where it’s used. Author covers Workshop and Settings: where you actually make a change. Most of your time is spent moving between two of these: Overview, to find a block, and Workshop, to edit it. History and Assets are what you check before and after.

​
Steps

1

Open the component library and find the block you need

The Overview tab lists every block in the library, each with a plain-language description and a rendered preview. Read the description rather than relying on the preview alone: a library typically holds a few dozen blocks, and near-duplicates, such as two button rows or two footer variants, are common by design.
Scrolling through the Overview tab's block list: each block's kit name, description, and an editable preview area.

Scrolling through the Overview tab's block list: each block's kit name, description, and an editable preview area.

2

Edit a component in the Workshop

Components aren’t edited in a form or a visual builder. Open Workshop. If the block already has a chat associated with it, allGood offers to reopen it. Open “[component name]” in the Workarea picks up the same chat the component was originally written in. From there you’re in a conversation with Ask Mary, allGood’s AI. Describe the change in plain language, or ask to see and adjust the underlying MJML directly if you want that level of control.
Asking Mary to edit a component in the Workshop, with the chat on the left and the rendered block on the right.

Asking Mary to edit a component in the Workshop, with the chat on the left and the rendered block on the right.

Saving a change in the Workshop creates a new version immediately, but that version doesn’t go live until it’s published. You can iterate freely. The emails currently going out keep using the last published version the whole time.
3

Check what a component is used by before you change anything but copy

The Assets tab lists every Email Template and Email currently built on this library, under Used by. Open it before making a change that touches structure, styling, or anything outside the EDIT boundaries documented on the block. Every one of those templates and emails picks up a published change automatically. This is where you see everything an edit would affect before you make it.
The Assets tab's Used by list: every Email Template and Email built on this library, each tagged 'references'.

The Assets tab's Used by list: every Email Template and Email built on this library, each tagged 'references'.

A change that only touches EDIT content — copy, a link, a color already marked editable — is safe; that’s what EDIT means. A change to anything LOCKED affects every template and email listed under Used by the moment it’s published, so check that list first.
4

Track a change through History

The History tab lists every version of the library, newest first. Two kinds of entries appear: plain version bumps, and lifecycle events like Published. Use this tab to confirm a change went through. Look for your new version, then a Published entry once it has been published.
The History tab: the version rail with its Published events, and the Roll back row above it.

The History tab: the version rail with its Published events, and the Roll back row above it.

5

Roll back to an earlier version

History also offers Roll back on every earlier version. Rolling back doesn’t erase anything. It creates a new version that matches the one you rolled back to. Like any other change, that new version has to be published before it takes effect.
A rollback you regret isn’t final. Roll back again to the version you rolled back from. History keeps every version, so nothing is lost either way.
Once a change is published, its version becomes what every dependent Email Template and Email renders on the next send. You’ll see the confirming Published entry in History, and the block’s status on Overview updates to show the version now live. If a version won’t publish, a rollback target is missing, or Used by doesn’t match what you expect to see, contact the team that maintains allGood’s email tooling rather than guessing at the cause.
  • Email components: what a component is and what EDIT/LOCKED actually mean, assumed background for this article
  • What MJML is: the short primer behind the MJML editing option in the Workshop step below
  • Write an email component: the authoring how-to this article’s Workshop step assumes