Skip to main content
Libraries are the foundation of every email you build in Denada. A Library packages your brand’s visual identity — colors, typography, layout patterns, and component designs — into reusable pieces that anyone on your team can assemble into polished, on-brand emails without touching HTML.

Why libraries matter

Without a shared system, every email becomes a one-off project. Designers recreate layouts from scratch, marketers paste content into inconsistent templates, and brand guidelines slowly drift. Libraries solve this by centralizing your email design system:
  • Brand consistency — every email uses the same approved components, so your visual identity stays intact across campaigns, teams, and regions.
  • Reusability — build a component once, use it in hundreds of emails. Update the component, and every future email gets the improvement.
  • Speed — marketers can create professional emails through the Chat interface or Template editor without waiting for design support.
  • Guardrails — Libraries control what can be customized and what stays locked, so non-designers can personalize content without breaking the layout.

Blocks

Blocks are the building blocks of your emails. Each Block is a self-contained piece of responsive HTML that handles one section of an email — a hero banner, a text section, a product grid, a call-to-action strip, a footer, and so on. A typical Library contains 10 to 30 Blocks covering all the common patterns your emails need. When building a template, you pick the Blocks you want and arrange them in order. Blocks are:
  • Responsive — they adapt to desktop and mobile screen sizes automatically.
  • Dark mode compatible — they render correctly in email clients that support dark mode.
  • Self-contained — each Block manages its own HTML and styling, so Blocks can be mixed and matched freely without conflicts.

Parameters

Every Block exposes Parameters — the specific fields that are safe to customize. Parameters are the bridge between the designer who built the Block and the marketer who fills it in.

Parameter types

TypeDescriptionExample
TextShort or long text contentHeadline, body copy, button label
ImageA visual asset from your Image LibraryHero photo, product thumbnail, logo
ColorA color valueAccent color, section background
BooleanA show/hide toggleDisplay disclaimer, show social links
LinkA URLButton destination, product page link
EnumA choice from predefined optionsLayout style, alignment, number of columns
Parameters are how Libraries enforce brand guidelines. By choosing which fields to expose (and which to lock), the Library designer controls the balance between flexibility and consistency.

How parameters work

When a marketer creates a template, they see only the Parameters — not the underlying HTML. They fill in a headline, pick an image, toggle a section on or off, and the Block’s HTML handles the rest. This means:
  • Marketers never need to edit code.
  • The design stays pixel-perfect regardless of what content is entered.
  • The Library designer decides exactly what can change and what cannot.

Brand guidelines through libraries

Libraries are your brand guidelines made executable. Instead of a PDF that people may or may not follow, a Library is a living system that enforces your standards automatically. A well-designed Library:
  • Locks down fonts, spacing, and color palettes so they cannot be accidentally changed.
  • Exposes only the parameters that should vary between emails.
  • Provides enough Block variety to cover your team’s common email patterns.
  • Includes sensible defaults so a new template looks good even before customization.

Publishing libraries

Once a Library is ready, publish it to make it available to your team. Published Libraries appear in the Chat interface and Template editor, where team members can use them to build emails.
Only team owners and managers can publish Libraries. Members can use published Libraries to create templates but cannot modify the Library itself.
Before publishing, review your Blocks and Parameters carefully. Once a Library is in use across multiple templates, changes to the Library’s structure can affect existing work.

Versioning and forking

Libraries support versioning so you can evolve your design system over time without breaking existing templates.
  • Versioning — when you update a published Library, existing templates continue to reference the version they were built with. You can update templates to the latest version when you are ready.
  • Forking — if you need a Library that is similar to an existing one but with meaningful differences (for a sub-brand, a different product line, or a regional team), you can fork it. The forked Library starts as a copy and evolves independently from that point.
Deleting Blocks from a Library can affect templates that use those Blocks. If you need to retire a Block, consider hiding it from new templates instead of removing it entirely.

Creating libraries

Libraries can be created in several ways:
  • From existing emails — send Denada your current email templates and it will train a Library from them, extracting your brand patterns into reusable Blocks.
  • From scratch — work with the Denada team to design a new Library tailored to your brand.
  • From any email or HTML — paste HTML or forward an email, and Denada will create a matching Block in real time.
Learn more about creating libraries in the Creating libraries guide.