Franklin compatibility checklist

We use a variety of digital marketing platforms, each with different styling capabilities. We created this design system to bring these platforms together under a single look and feel, but unfortunately not all of them are able to follow the guidelines to the letter.

When evaluating a new platform, we should aim to ensure they are capable of following the Franklin style as closely as possible.

Platforms can be categorized into three groups:

  1. Full design system users
  2. Medium users
  3. Basic users

With 1 being the most customizable and 3 the least. More customization allows closer alignment with Franklin.


To qualify as a Medium user, a platform must be able to:

Additionally, they can be considered Full users if they can:

If the platform can’t qualify as a Medium user, they are a Basic user. Typically, with Basic platforms there is no ability to write custom HTML, CSS, or JS. Visual customization is limited to e.g. changing colors and picking from predefined templates.

Example questions

Could the platform incorporate our main header navigation by using the HTML defined at: How about tabs, as defined at:

Examples of each type


  • Malvern Panalytical website
  • Materials Talks blog
  • Careers website


  • Bizzabo event pages
  • OneWelcome login screen


  • Salesforce customer portal
  • Bizzabo agenda pages


More detailed instructions on consuming Franklin’s CSS and JS can be found at

Example HTML for nearly every component is available at

Documentation is currently a bit lacking for Medium users – e.g. there’s no simple way to supply compiled CSS for their reference, and the uncompiled Sass is likely overcomplicated for their needs. I’m happy to talk through everything they need, but we should aim to document this more thoroughly.