Skip to main content

Modules

Modules are the reusable content blocks marketers add to emails. A strong module is easy to recognize, easy to configure, and flexible enough to cover a real content need without becoming messy.

Each module usually contains:

  • HTML and Liquid code
  • settings and inputs
  • metadata such as thumbnail, hidden status, and AI context

What makes a good module​

A good module should have one clear job. For example:

  • hero
  • article card
  • promo banner
  • image with text
  • product row

If a module is trying to do everything, it usually becomes hard to use in the Email Editor.

Creating modules​

You can create a module in the Template Editor by:

  • adding a new blank module
  • extracting an existing section of code from the template base into a module

The extraction workflow is especially useful when you start from a finished HTML email and want to turn it into a reusable system.

TODO: Add a screenshot or short video showing a section of base HTML being extracted into a new module.

Settings​

Each module has its own settings. These settings are what marketers edit when they select the module in the Email Editor.

Read more:

Metadata​

Metadata improves how the module behaves and how easy it is to manage.

Thumbnail​

The thumbnail helps marketers recognize the module quickly in the module list. Use a realistic example state, not a blank placeholder.

Hidden status​

Hidden modules stay in the template but do not appear in the marketer-facing module list. This is useful when you want to retire a module without deleting its code immediately.

AI metadata​

AI metadata helps Betty understand how the module should be used, what kind of content it is for, and any important rules it should follow.

TODO: Add a screenshot of the Metadata tab showing module name, hidden toggle, thumbnail, and AI metadata.

  • Keep module names short and specific.
  • Give every production module a useful thumbnail.
  • Hide modules before deleting them when you are unsure whether they are still needed.
  • Use repeatable settings when one module needs a repeatable content structure.