We are not designers, not us in the Morfeo's team, not me that I'm writing these docs, and probably not even you reading them.

We're developers, frontend developers more specifically, which means that most of the time we build user interfaces designed by other people.

Maybe this is not your case, maybe you're also a designer or maybe you just have really good taste - either way, before or later you'll collaborate with someone else, some of them will be like you, and some not, and when people start to collaborate they need to be good in one thing: Communication.

Communication in the software world is really underestimated, It's hard to see a company failing where all the departments are clear in their intentions, the sharing of ideas and practices is welcomed, and the documentation is good and easy to browse.

Instead, everywhere I saw people hiding information, not writing clear tasks or documentation, or not clarifying why a feature was needed, then the project didn't reach production, or if it did it was not successful nor scalable/maintainable.


It might sound obvious, but every product is the result of the people who worked on it:
If those people cannot properly talk with each other, how will the product be understandable to their users?

Morfeo's approach

Here is where Morfeo started: how can we make a developer tool that will help (us) developers communicate better with each other and with the designers?

Our answer is:

  1. We need a shared language that both devs and designers can speak and understand;
  2. We need a way to convert this language into visual elements;
  3. And, finally, we need a way to ensure that the language is always spoken correctly.

If you think about it, these are the same principles behind a spoken language:

  1. A set of words that are the only available blocks we use to speak the language;
  2. A representation of those words to write them down;
  3. And a grammar that tells us how to put those words together.

From a technical perspective, we implemented these 3 concepts in this way:

Design Language

The shared language is an object, usually called theme or design language, a single source of truth that contains all the primitive (and only) blocks to construct all the layouts.


that converts this theme into valid HTML & CSS (for the web at least).


which will yell at us if we don't use the theme to describe our UIs.

These are the main concepts around Morfeo, all the decisions we took to create Morfeo's API are made around those concepts and to reach our goal:

Provide a tool to create good-looking UIs in the simplest and most efficient possible way.