Dublin Library

The Publishing Project

Revisiting design systems

  • 10 min. read

 

Design systems are interesting because of how they scale design to multiple teams and multiple sites/products while still providing a consistent and recognizable brand. For a full introduction to design systems, see [Introducing Design Systems](https://www.designbetter.co/design-systems-handbook/introducing-design-systems) The work I do is not always conducive to creating a design system but it's always good to know about them so we can jump in without having to start completely from scratch. That said we'll look at three areas: - Building a basic component using just HTML, and CSS - Building the same component using existing design systems - Material Design from Google - Atomic Design from Brad Frost - Building the component using Web Components - Plain Web Components - Polymer ## No Design Systems I want to design a card component where we can control the direction (vertical or horizontal), the dimensions (height and width) and the border. The component should also provide ways to layout its children using Flex. The CSS looks something like this: ```css :root { --card-border-color: #000; --card-border-width: 1px; --card-border-style: solid; --card-display: flex; --card-direction: column; --card-width: 400px; --card-height: 300px; --card-padding: 1em; } .card { display: var(--card-display); flex-flow: var(--card-direction); border: var(--card-border-width) var(--card-border-style) var(--card-border-color); height: var(--card-height); width: var(--card-width); } .card-title { color: #fff; background-color: #000; } .card-content { padding: var(--card-padding); } ``` The idea is that by changing the value of the variable declared in the `:root` element we change the way that all card elements will look on the page. I choose the `: root` element rather than `HTML` because `:root` has higher specificity and it would override any declarations in HTML rather than having to depend on the way properties were declared every time. Let's say that we want to create a horizontal card. All we have to do is redefine the variables for the elements we need to change, something like the following example: In this example, we make the card layout its children in a row, rather than a column, we also change the dimensions of the card but we keep all other values the same as our `:root` declaration. ```css :root { --card-border-color: #000; --card-border-width: 1px; --card-border-style: solid; --card-display: flex; --card-direction: column; --card-width: 400px; --card-height: 300px; --card-padding: 1em; } .card2 { --card-border-color: #000; --card-direction: row; --card-height: 300px; --card-width: 800px; border: var(--card-border-width) var(--card-border-style) var(--card-border-color); display: var(--card-display); flex-flow: var(--card-direction); height: var(--card-height); width: var(--card-width); .card-title { width: 10em; } } ``` This is just an initial step, we could further refine the card component by providing defaults in case we want to add an image instead of text on the title, but it'll do as the basic example of what we want to accomplish. One other thing that needs to happen for this card to become an element is to document the ways in which you can customize the component... ideally with full examples that can be copy and pasted to be used. ## Design System Now that we have a basic idea of what we want to do, let's look at different ways in which design systems can make the process easier, less painful or both. ### Material Design The new iteration of material design has its good and bad aspects. The good is that the new version is much easier to customize and make look "less like a Google product" than the original The bad is that Material Design now requires SCSS and ES6 for development. You can't just drop the Material Design components into an existing project if the project doesn't use a build system or SASS to process the CSS. Since I already use both ES6 and SCSS for my projects, I think the drawbacks, if you can call them that, are worth the investment. As you can see the code depends heavily on classes starting with `mdc-`. The reason why will become clearer when we look at the SCSS code that styles the element. ```html
Title

Content goes here

``` Material design is based on SCSS so to add the components' styles we just import them using SASS `@import` syntax... with a twist. ```scss @import '@material/card/mdc-card'; @import '@material/button/mdc-button'; body { font-family: Roboto, sans-serif; } .mdc-card { margin: 2em auto; height: 350px; width: 350px; } .mdc-card__media { background-image: url('../images/sunrise.jpg'); img { width: 350px; } } ``` Because we are going into the `node_modules` directory we have to call the sass command with a special flag to include the modules directory into the path SASS searches. The command is: ```sh sass -I node_modules/ sass/:css/ ``` This works in version 1.13.0, the current Dart version of SASS. ### Atomic Design Atomic Design, conceived by [Brad Frost](http://bradfrost.com/), and explained in [the book of the same name](http://atomicdesign.bradfrost.com/) is a way to break a page into its components down to the single HTML element. The introduction of the book explains it like so: > And then Brad Frost the front-end developer started talking like Brad Frost the chemist. He talked about atoms and molecules and organisms—about how large pieces of design can be broken down into smaller ones and even recombined into different large pieces. Instead of visualizing the finished recipe for the design, in other words, he was showing us the ingredients. And we lit up: this was a shift in perspective, a way to move away from conceiving a website design as a collection of static page templates, and instead as a dynamic system of adaptable components. It was an inspired way to approach this responsive website—and all responsive projects for that matter. Atomic Design — Introduction. Atomic design uses three structures to build pages: Atoms, molecules, and organisms. Think of individual HTML elements as **atoms**, the basic building block of a web page. You can't break down an atom into smaller parts without losing functionality and the effect the element has on the page. Look at the table below to get an idea of what the possible atoms of a web page are. ![](//publishing-project.rivendellweb.net/wp-content/uploads/2016/12/html-periodic-table.png) Periodic Table of HTML Elements shows that all HTML elements are organized around a function. These atoms may be the plain elements or styles for a specific theme or molecule designs. The next step up is a \*\* molecule\*\*. We create a molecule when we combine two or more atoms to perform a given task. **Organisms** are groups of molecules functioning together as a unit. These structures can be as small or as large as you need them to be. We can use these organisms to build pages and applications. For more information about Atomic Design, check the [the book](http://atomicdesign.bradfrost.com/). For the card organism, we'll take the same card declaration that we used when we created the card component. We have two molecules making the card organism: - A `card-title` molecule that contains a title and, optionally, an image inside - A `card-content` molecule that contains the text content Each of these molecules can have any number of atoms inside of them. We can choose to document individual atoms or to just to document the styles for colors, links, and typography, among others. ```html

Card Title

I want to design a card component

``` The styling is the same as for the no-design-system using CSS variables to handle different alternatives for the content and some effects on the text and background colors of the molecules. ```scss :root { --card-border-color: #000; --card-border-width: 1px; --card-border-style: solid; --card-display: flex; --card-direction: column; --card-width: 400px; --card-height: 300px; --card-padding: 1em; --card-title-color: #fff; --card-title-background-color: #000; } body { font-family: Roboto, sans-serif; width: 80%; margin: 0 auto; } .card { display: var(--card-display); flex-flow: var(--card-direction); border: var(--card-border-width) var(--card-border-style) var(--card-border-color); height: var(--card-height); width: var(--card-width); } .card-title { color: var(--card-title-color); background-color: var(--card-title-background-color); } .card-content { padding: var(--card-padding); } ``` ## Web Components As Design Systems Web components, to me, address some of the shortcomings of design systems. They encapsulate styles so there's no bleeding between the containing page and the components, this means that styles across different components can have the same name as they are exclusive to the element... We'll explore the advantages and disadvantages of the model. ### Vanilla JS The vanilla Javascript version consists of two parts: The CSS and HTML that we'll stamp every time we create an element of this kind. We use CSS variables that we'll define in the HTML container for the element. ```js let template = document.createElement('template'); template.innerHTML = ` ``` The HTML portion of the template uses slots to reflect elements of the 'light side' declaration to places in the template. The slots also provide additional ways to style the content. We'll look at slots in more detail on the slotted content when we look at the implementation of the card element. ```js

Title

Content
`; ``` The second part of the `card-element` element is the definition of the custom element itself. We do it by creating a class that extends `HTMLElement`, the base class for all HTML elements. We then build the constructor where we do the following: 1. Call the parent's class constructor using `super()` 2. create a shadow root for the element 3. Append the content of the template to the shadow root we just created Finally, we use the `define` method of the customElements registry to associate a tag name with the component we just defined. ```js class cardComponent extends HTMLElement { constructor() { // Allways call super() first super(); let root = this.attachShadow({ mode: 'open', }); root.appendChild(template.content.cloneNode(true)); } } window.customElements.define('card-element', cardComponent); ``` With that, we're ready to implement the element. In the head of the element, I'll place a link to Google Fonts and a set of variable declarations for the `:root` element. ```html ``` We then import the card element as a module using the `type=module` attribute of the script tag. ```html ``` In the body of the page, we stamp out multiple versions of our `card-element` element. The first one is just the element. This will create a card with only fallback content. ```html ``` The second element uses the slots we defined in the element's template. We can add as much content to each slot as we want... as far as I know there is no limit. ```html

Card Demo #2

Some content that is different from our default

 ``` ### Polymer Polymer adds syntactic sugar on top of web components with additional functionality and syntactic sugar. The idea is to drop these components. Building a Polymer element is very similar to building a vanilla Javascript web component. Instead of extending from `HTMLElement` we extend from `PolymerElement`, the base class for Polymer. Since we're not using any binding in the element, we can use a template like the one we created for the vanilla components. The main difference is that we must import the `html` tagged template literal and `PolymerElement` base class before we can use them anywhere. ```js import { html, PolymerElement } from '@polymer/polymer/polymer-element.js'; class MyCard extends PolymerElement { static get template() { return html`

Title

Content
`; } } window.customElements.define('my-card', MyCard); ``` The host document is almost identical to the plain vanilla web component. We add the following elements to the head of the element. We include the [wecomponents polifill](https://www.webcomponents.org/polyfills) to make sure that the component works in browsers without native support. ```html ``` The Polymer version of the element is identical to the vanilla component. We insert the following into the body of the page. ```html

Card Demo #2

Some content that is different from our default so we can be sure that the slots are working as intended and we are not pulling the default content

 ``` ## Documenting Your Design System Now that we've decided to use a design system and we've chosen the components that we want to share. Now we need to document it. [Fractal](https://fractal.build/) provides tools and structure for design systems. We will not address the specifics of Fractal or any other tools to document. I chose Fractal because it gives you the flexibility to use components with copy/paste or incorporating into a build system. Fractal's downside is the documentation. It leaves a lot to be desired when it comes to documenting the process to incorporate the tool into other applications, the API and mount points for the application. There is ongoing work to improve and update Fractal. See [issue 449](https://github.com/frctl/fractal/issues/449) in the Fractal Github repository for more details as to current status. ## Looking forward: AI Design Systems? An interesting take on design systems is what would it look like if we can get working code from a hand-drawn wireframe? There are projects in early prototype stages that will let you do this. Pix2Code has published both [a paper](https://arxiv.org/pdf/1705.07962.pdf) and the corresponding [Github repo](https://github.com/tonybeltramelli/pix2code) explaining their work. According to the paper: > Transforming a graphical user interface screenshot created by a designer into computer code is a typical task conducted by a developer in order to build customized software, websites, and mobile applications. In this paper, we show that deep learning methods can be leveraged to train a model end-to-end to automatically generate code from a single input image with over 77% of accuracy for three different platforms (i.e. iOS, Android and web-based technologies). [pix2code: Generating Code from a Graphical User Interface Screenshot](https://arxiv.org/pdf/1705.07962.pdf) This would mean that the approximation we craft can be translated to code that can be further iterated on or can be put into production. In an interesting twist, Airbnb is also looking at using Machine Learning to translate mockups into code that can be further moved up and down the design and development chain. There is no actual code prototype but the idea is intriguing enough to merit further attention and research. ## Links and Resources - AirBnB - [The Way We Build](https://airbnb.design/the-way-we-build/) - [Building a Visual Language](https://airbnb.design/building-a-visual-language/) - Atomic Design - [Book](http://atomicdesign.bradfrost.com/table-of-contents/) - Google - [Google Design Library](https://design.google/library/) - Design Systems Repo - [Repo](https://designsystemsrepo.com/) - [Gallery](https://designsystemsrepo.com/design-systems/) - [Articles](https://designsystemsrepo.com/articles/) - Mailchimp - [Content Style Guide](https://styleguide.mailchimp.com/) - Web Components - Google Developers - [Custom Elements v1: Reusable Web Components](https://developers.google.com/web/fundamentals/web-components/customelements) - [Shadow DOM v1: Self-Contained Web Components](https://developers.google.com/web/fundamentals/web-components/shadowdom) - [The Holy Grail Of Reusable Components: Custom Elements, Shadow DOM, And NPM](https://www.smashingmagazine.com/2018/07/reusable-components-custom-elements-shadow-dom-npm/) - [Polymer](https://www.polymer-project.org/) - [Wired Elements](https://wiredjs.com/) - Sites Using Fractal - [City of Boston](https://patterns.boston.gov/) - [City of Ghent](https://stijlgids.stad.gent/v2/) - [24Ways.org](https://bits.24ways.org/) - [Clearleft](http://fractal.clearleft.com/) - [Perch CMS](http://patterns.perchcms.com/) - [US Web Design System](https://components.designsystem.digital.gov/) - [Kanbasu](https://kanbasu.liip.ch/2/) - [Liip](https://styleguide.liip.ch/) - [Eurostar](https://style.eurostar.com/) - Machine Learning and Design Systems - Pix2code - [pix2code: Generating Code from a Graphical User Interface Screenshot](https://arxiv.org/pdf/1705.07962.pdf) - [Github Repo](https://github.com/tonybeltramelli/pix2code) - [Turning Design Mockups Into Code With Deep Learning](https://blog.floydhub.com/turning-design-mockups-into-code-with-deep-learning/) - [Sketching Interfaces](https://airbnb.design/sketching-interfaces/)

Edit on Github