A Live Developer Journal

Material design components project setup with reset and typography

Material design is a design system developed by Google in 2014. This system is inspired by tme real world and it's textures, including how they reflect light and cast shadows. Material surfaces reimagine the mediums of paper and ink.

After downloading the free Material Design sticker sheet developed by google, I designed a few screens with it for my work's mobile app, and also a personal app. I really love how they turned out.

My plan then is to recreate the sticker sheet in HTML and SASS, so that I can easily reuse each of the components in live projects just by dragging and dropping the code snippets into my projects.

I'm going to be using variables to represent the font-family, font-sizes, colors etc so that the entire site style can be rebranded just by changing the values in the main variables.

When building the components, I will be looking at Google's guidelines for each of them so that they follow the standards as close as possible. I'll also be testing everything I build against accessability and quality standards. All of these components need to be as clean as possible.

I'm going to start with a mobile version of all of these components, as the sticker sheet is intended for mobile apps. Then I'll look into styling them so that they become web responsive.

I'm going to document the entire project build here because there is going to be a ton of useful information that will be good to revisit, especially as this project is entirely focused around best practices.

Project setup

The first thing I did was set up and empty project that uses node-sass. I also included a small script that recompiles the SASS into a CSS stylesheet every time a SASS file is saved. This means I don't have to recompile my SASS every time I want to see the changes I have made. Here is a tutorial I wrote previously for setting up an empty project with SASS.

First commit

After setting up my 'material-design-library' project, I wanted to ignore a couple files before making the first commit. Here are the files before ignoring any of them.

files to be committed

I added the css directory to the gitignore file because sass automatically regenerates this (compiles) whenever a SASS file is saved, so we don't need to commit it. I ignored the css directory by running the following command:

echo css > .gitignore

This command writes 'css' to a file called '.gitignore'. If there is not already a .gitignore file, this will create one for you as it did in this case.

I also ignored the node_modules directory. If anyone else clones this project, running 'npm install' will add the node_modules directory as well as node-sass because I added it as a developer dependency to the package.json. No need to commit. To ignore this directory, I ran the following command:

echo node_modules > >

The double 'greater than' signs are used to append to a file instead of overwriting everything completely, which is what the single greater than sign does.

To make the first commit, I ran git add . which stages all the files to be committed. Usually, I'd recommend against using this command because it's better to be explicit about the files you are going to commit. If I ran this command before ignoring any of the directories, then I would have accidentally committed things that should not be committed. Only use it if you intentionally want to commit all of the files listed. In this case, I wanted to bundle the rest of the files together in a single commit, because together they represent the project setup, which is ideal for a first commit.

My first commit message for this project was:

git commit -m '🎉 start material design component project, yayy!'

This commit message follows two sets of guidelines. The first comes from a post about How to write a git commit message by Chris Beams, which provides seven rules plus tips. I especially like the advice to come up with a commit message by filling in the blank: "If applied, this commit will _____"

I like using git log --onelineTo see a clean list of commit messages without all the extra meta data like author name and date etc

The second set of guidelines I'm following here is a bit of fun. I use emoji's to represent what type of commit I am making, using the gitimoji guide. The party popper emoji represents your first commit. I'm going to add a list of the ones I'm likely to, or might use in this project so that I don't have to sort through the list each time. This is not a complete list of the available emojis.

When using emojis in commit messages, make sure that your commit message is surrounded by single, not double quotes for it to work.

Emojis for commit messages


The next thing I want to do before starting on any of the components is adding a reset to remove all styles from my CSS. I want my components to be consistent across all browsers, especially as this project is intended to be used by other developers who might not use conventional browsers. (I like using developer specific browsers, current favourites are blisk and sizzy..

To make your CSS cross-browser compatible, you can use a CSS reset or a Normalize CSS. Here is a good breakdown of the difference between the two. I'm choosing the reset over normalize because I want full control over all element sizes without having to override anything to match the material design guidelines.

I'm using Eric Meyer's CSS reset. because it is a widely tried, tested and recommended reset. There might be a better one, but for now this will do.

I don't consider a reset to be a new feature, so will add it in without creating a new branch for it.

I follow the 7-1 pattern for organising my SASS folder architecture.

Commit message: 💄 reset CSS files ready for material design specific styles

The guidelines for the commit message says no more than 50 characters. This commit message is slightly longer, and also explains why the change is being made. This is more meaningful than 'reset CSS'. Now we know what the intent was at a glance. It's important not to follow guidelines blindly, if you need to modify them slightly so that they express your intent more clearly, do so. But make sure your reasons are stronger than the reason's for not diverging.


I consider the typgograhy to be a feature of material design. Usually, I would create a new branch for a new feature when I am working on a code base with other people. As I'm the only person working on this branch, I won't create any branches.

Personally, I like to mark the start and completion of a new feature. To mark the start, I'll create an empty file called '_typography.scss' in the base folder and import it into the 'main.scss' file. Then I'll commit it: '🌱 start typography feature following material design guidelines'

The end commit message for this feature will be along the lines of '✨ completed typography feature, responsive and semantic sizes'

I like writing out the end commit message (which might change) before working on the feature. If I struggle to write it, then it means I don't have a clear idea of the end result, so need to either clarify the feature idea or consider whether it needs to be there at all.

Typography guidelines for material design

In the material design guidelines for typography there are 13 categories of reusable categories of text. One for each of the heading sizes (x 6), 2 x subtitles, 2 x body text, 1 x button, 1 x caption and 1 x overline.

For each of the text categories, there are font-weight, font-size, font-case (uppercase/lowercase etc) and letter spacing. In addition to this type scale information, there are also conversion charts for font-size units. They show you how to translate the units to work on Android (sp), iOS (pt) and Web (rem).

To incorporate the type scale, I want to match each type scale category with it's own set of styles. For the headings 1 - 6, I'll target them directly with their HTML equivalent tags instead of applying classes. This will ensure that every time I use one of these headings, the size will be consistent. If I want to change it, I'll have to override it, so this will force me to think about why I'd want to override the text.

Before doing this, I am interested in what this will mean for the card components which use headings. Will be interested in how the sizes are used there. At the moment, it seems like the visual hierarchy is a direct match for the document hierarchy, when seperating them is useful if you want a smaller heading in terms of size whilst keeping the semantics the same. Will look into this.

I'm making these material design components for the web. The conversion charts say I need to multiple the font size units by 0.0625. The web units are written as 'REM' units which is based on the root size, which by default is 16px.

The reason we are not using pixels, is so that the user can change the default text size if they want. Pixels prevent them from being able to do this.

Importing fonts from Google fonts

The typography scale suggest three font weights, 'light', 'medium' and 'regular'. The font family used here is the Roboto font.

While I can use the Roboto font family in CSS, I can't specify the three specific font sizes mentioned in the type scale by name or number value. So to use it I need to import the font.

I searched for 'Roboto google font' in my search engine, and then clicked on the red plus button with 'SELECT THIS FONT' written next to it. This created a pop up list menu, closed by default with the title '1 Family Selected'.

I clicked on the '-' sign at the top left of this bar to open it. The resulting window showed an embed link for CSS. There is also a tab for customising the font. I clicked on the customize tab and selected the three font sizes specicified by the type scale. Then I copied the new embed link, which I'll need to add to all of the web pages I create that uses that font.

I added an 'index.html' page to the root folder of the project, added a minimal HTML boilerplate and pasted the embed link into the head section. I also added a link to the 'css/style.css' stylesheet which will contain the compiled SASS styles.

Commit: 🔧 import Roboto google font with light, regular and medium weights

Using Font-weights

Inside of the '_typography.scss' file, I used the 'body' selector and set the font-family to 'Roboto', sans-serif. All of the text categories in the type scale use this font, so I applied it to the body to prevent dupication (applying it to each text case).

The typography guidelines provide guidance on selecting fonts for each of these use-cases if you want to deviate.

Then I added selectors for each of the heading sizes (h1-h6) and set the font-sizes to the sizes specified in the type scale. As I was doing this, I struggled to remember what the font-size values meant (light: 300, regular: 400, medium: 500). So I created variables with those names in 'abstracts/_variables.scss'. The abstracts folder and _variables file was created to do this, then imported into the main.scss file.

$light: 300;
$regular: 400;
$medium: 500;

I then converted the font-sizes and font-weights to rems and applied these styles to the headings in the typography file

I did the same thing for the remaining typography cases.

Finally, I opened the sketch file and got the line heights for each of the typography cases. When I used the CSS reset, all of the line-heights were removed, so I have to add them back in.

Completed typography feature.

Color scale

Next feature is the color scale. I set them up using this color palette system I designed:

color palette hack

Wow this all took a huge amount of time to do, but when it's all done will make future design build projects so much easier.