Design system guide

Develop your marketing emails and landing pages for consistency, scalability, and collaboration

Email design system elements including color codes, photos, buttons, layouts, and code snippets.

A design system is a set of tools, and resources that help your team scale design processes. With shared workflows and assets, your team can follow brand guidelines be more efficient. It helps solve the following problems:

What to include in your design system

This guide is broken down by each of the key aspects your design system should include and how to effectively share your design system within your organization.

Branding

Refer to your organization's current brand guidelines: a styleguide, logo requirements, etc. Any related design documentation that may be available. And any design patterns that are used for your marketing efforts.

Brand elements to include

Writing

The most important part of any campaign is the message it's communicating, the text itself. Your design system should include some guidelines around how copy is written. From the mechanics of the content, to the voice and tone.

Basics of voice and tone

Use these general tips to develop the rules around your organization's writing approach:

Composition guidelines

Components

A design system shouldn’t feel like something that stifles creativity. Don't make it too rigid, a certain level of hand-crafting is important. It should allow for greater creativity within a set of guidelines. The long-term benefit is that a designer can take greater care and give better thought to solving each solution instead of rushing to put together something that comes along.

Creating a component

A good component is

  • Purposeful - all components solve a specific problem
  • Reusable - components work for multiple use cases
  • Flexible - they work in many different contexts


Related reading

Guide on designing and coding a modular email template →

Guidelines

Static components answer the how. Guidelines provide answers to: why, when, and where. "Can we?", "should we?", and "what if..." They should educate on constraints: workflows, habits, and best practices. Having this information leads to a reduced need for everyday problem-solving and decision-making.

What to include in your notes


Additional considerations

Sharing

Your design system is only as strong as your relationships with the teams who use it. You need to develop trust and allow for it to evolve by encouraging participation in its development.

Make people feel like they’re part of the process

Provide good examples

Show examples of how to be creative with structure. Encourage “off-roading” to evolve system. Consider examples from other organizations to help show ways to utilize a system without feeling boxed into a boring design.

Documentation setup

Documentation as a web page is the best way to go when developing your design system:

  • Format that anyone can access - everyone can always go to the same URL
  • Centralized - updates are dynamic without creating too many versions that need to be passed around
  • Easy to maintain - designers, developers, and organizers can make updates

Your design components tool

This guide has been put together by the Blocks Edit team. Having a design system of reusable components for your organization to use, Blocks Edit makes your components visually editable. So anyone on your team can build emails and landing pages on their own while ensuring they are following brand guidelines throughout the process.

Share this guide

Send via email | Copy link URL