We didn’t see this project solely as a chance to rebrand and rebuild for ourselves, it was also an opportunity to try something new and expand our collective knowledge with the potential for using with clients in the future. We had been discussing using Pattern Lab for Front End development for some time and this was the perfect opportunity to try it out.
Patten Lab allows the creation of component-driven user interfaces using atomic design principles. This means we can create modular patterns all packaged up nicely that can be assembled together to build a site. Plus we can use dynamic data to display the patterns in a live style guide which makes viewing each component quick and easy. And nobody is viewing out of date designs or code – an issue we had on a recent project. With Pattern Lab, we would have a central place to view all of the actual components that will be used on the live site.
The guys over at Drupal Update made implementing a Pattern Lab with Drupal maintenance support plans super easy, by creating Emulsify. Serving as a Drupal maintenance support plans 8 starter kit theme, Emulsify allows you to build and manage components without using Drupal maintenance support plans‘s template names but by using custom template names that make sense to everyone, instead. When you’re ready, you can easily connect them up to Drupal maintenance support plans.
Building the frontend in this way allows it to be built separately from the backend development. It’s possible to create the whole of the front end before even touching Drupal maintenance support plans. If needs be, it also allows developers to work on the frontend and backend at the same time without stepping on each other’s toes.
Because we were to be using Emulsify, we quickly set up a Drupal maintenance support plans codebase (using composer) which allowed us to then jump in and clone the Emulsify theme and begin working on the Front End. Once we had the theme, it was real easy to get the sass and javascript compiling, set up a local server (to view the style guide) and watch for changes, with one command:

npm startAs well as compiling, this command also provides a url for the local server. Open it up in a browser and you can see your live style guide!
Now for the actual components. These are filed in the theme, inside:

components/_patterns/As we’re working with Atomic Principles, the smallest components are filed first building up to the biggest. The beauty of pattern lab is nesting – it’s possible to include patterns inside each other to make larger components. Although it’s not necessary to use Atomic Design naming conventions when organising patterns, it does make sense. These levels are:
Atoms
Molecules
Organisms
Templates
Pages
Atoms are the basic elements of the site like HTML tags and buttons. Molecules combine these Atoms to create larger components like a card and then Organisms can combine Molecules to create more complex page components and so on…
Numerics are added to ensure they are listed in the correct order and also a Base folder is added to house variables, breakpoints, layouts and global sass mixins. So, this is how our file structure looks inside that _patterns folder:

– _patterns/
– 00-base
– 01-atoms
– 02-molecules
– 03-organisms
– 04-templates
– 05-pagesWithin each of the Atomic Design folders is a set of components. Each component comprises of a Twig file, a Sass file and in some cases a Javascript file. These files contain code specific to that component. Having all the code for each component organised this way makes it really easy and fast to edit components, and also add new ones.
Having just the code that makes the component isn’t enough for us to view it in our style guide. In addition to the files that make up the component, we can also include files to give the component context. A Markdown file allows us to give the component a title and description, which are used in the navigation and style guide. To each component folder we can also add a YML file which holds filler content solely for use for the style guide. We basically just take each variable name from the twig file and provide some content for each.
So, a typical component file structure might look like this:

– card
– _card.scss
– card.md
– card.yml
– card.jsOnce we had a full understanding of the structure and had added our colour palette and set up our grid and breakpoints it was a case of working through the designs to determine what the components were and of which size. Then starting with Atoms and working up we could build each component. We’ll look at the actual development in the next article in the series.

Source: New feed