Skip to main content

Overview

The Style Library is the centralized system that stores all your design tokens. It ensures visual consistency and lets you update the design of all emails by changing tokens once. Think of it like a brand kit built specifically for email.

Core Principle

Centralization

All styles are defined once in the Style Library.

Reference, don't duplicate

Emails and components reference these tokens instead of using manual color codes.

Automatic propagation

Change a token, and all elements using it update automatically.

Enforced consistency

Shared tokens keep your colors and typography consistent across emails and components.

Token Types

Fonts

Manage fonts in the Fonts section of the Style Library. Add a custom font by uploading font files or providing their URLs, then choose it in a text style. Set a fallback font for email clients that cannot display your custom font. Use an inbox test to check the result in your target clients.

Colors

Colors are reusable tokens you define once (e.g., “Primary”, “Background”).

Structure

  • Name: Human-readable name (e.g., “Primary Orange”)
  • Value: Color code (e.g., “#F97316”)
  • Usage: Where it can be used (button, text, background)

Usage

Used in color pickers for elements.

Text Styles

Text styles define your typography (size, weight, font family).

Structure

  • Name: e.g., “Heading 1”, “Body Text”
  • Font Size: e.g., “32px”
  • Font Weight: Bold, normal, etc.
  • Font Family: Your chosen font
  • Line Height: Spacing between lines

Usage

Applied to Text and Button elements.

Button Styles

Button styles define complete button appearance.

Structure

  • Name: e.g., “Primary CTA”
  • Background Color: Reference to a color token
  • Text Style: Reference to a text style
  • Padding: Inner spacing
  • Border Radius: Rounded corners

Usage

Applied to Button elements.
Link styles define how links look within text.

Structure

  • Name: e.g., “Standard Link”
  • Color: Link color
  • Decoration: Underline or none
  • Font Weight: Bold or normal

Usage

Applied to links within Text elements.

Managing the Style Library

Adding Tokens

1

Access Style Library

Open “Style Library” from the main navigation menu.
2

Add a token

Click “Add” in the appropriate section (Color, Text Style, Button Style, Link Style).
3

Configure

Fill in the token properties (name, values, etc.).
4

Save

The token is immediately available in all editors.

Modifying Tokens

When you modify an existing token: Review its usage before saving. Mailkick shows the emails and components that depend on shared styles so you can assess the change.
All emails and components using that token automatically update with the new value.
This is the main advantage of the Style Library: one central change propagates everywhere instantly.
Changes in Mailkick do not automatically update templates already synced to a sending tool. Sync the affected emails again to publish their new appearance there.

Deleting Tokens

Before deleting a token, check its usage to see which emails/components use it.
Replace a token in the elements and styles that use it before removing it, so those items keep their intended appearance.

Importing Styles

When you import a design from Figma, Mailkick checks its colors, text styles, and button styles against your library.
1

Paste your Figma design

Copy it with the Mailkick Export plugin and paste it into the email editor.
2

Resolve unmatched styles

If styles are missing from your library, choose whether to match existing styles, add the imported styles, or customize the mapping.
3

Continue the import

Mailkick applies your choices and makes newly created tokens available for reuse.

Email defaults

Open Style Library → Email defaults to configure the starting language, width, backgrounds, and spacing for new emails. Managing these defaults requires an owner or admin role. These content defaults apply when an email is created. Changing them does not restyle existing emails; edit those emails or their shared styles separately. The Editor view setting in the same section chooses the team’s default desktop or mobile editing view.

Best Practices

Use clear names (e.g., “Primary”, “Secondary”, “Heading 1”, “Body”).
Reuse tokens rather than creating duplicates.
After modifying a token, check a few emails using that token to ensure the result looks correct.

Benefits

🎨 Consistency

No off-brand colors or fonts.

⚡ Maintenance

One central change updates all emails.

🚀 Productivity

Select pre-defined styles instead of manually entering values.

🔄 Rebranding

Change your entire brand look by modifying a few tokens.