Email Specifications
Last updated: September 11, 2015 at 22:58 pm

Business rules and style specifications for emails.

Visual example of the element:

What problem does this element or pattern solve?
Trying to create a consistent HTML email experience across all currently used web-based and
dedicated email clients can be challenging at best. Wildly varying rules governing which visual
styles will, or will not, be displayed makes effective email design and coding a specialty within
many organizations. Use this section to introduce these special considerations, being sure to
include links to any offsite documentation that is available.
It applies to these platforms:

Desktop Web, Tablet Web, Smartphone Web,

An example of this element or pattern in production:

Detailed specifications

Specifications To Consider

  • Does your company create HTML emails? Text only emails? Or both?
  • If creating HTML emails, which email clients and web-mail formats do you support?
  • Provide basic specifications and visual styling restrictions for designers creating mockups. Maximum width, minimum font sizes, approved media formats, etc.
  • Most emails are required to include special disclaimer text that provides a clear unsubscribe link, provides the source of the customers email address, etc. Provide link to the most current text and provide example of the visual styling.
  • Do you have a dedicated team that creates and codes your emails? Provide links to their content guidelines for employees who need to create new emails.

Location of assets to build this element or pattern
Location of UX or visual design assets
Location of development code repository

Additional details
Information on research, user testing, or usability reports:

Not Applicable (Remember: no field should be blank!)

This element or pattern may also be known as:
Not Applicable (Remember: no field should be blank!)
Related elements within this Style Framework:

Not Applicable (Remember: no field should be blank!)

Owners and governance
UX or design 0wner
John Designowner
Business or marketing owner
Mary Businessowner
Development owner
Mike Devowner

Other information
Please include any other relevant information about this element or pattern:
Not Applicable (Remember: no field should be blank!)

Comments & Questions