modulare Webentwicklung

Developer Ben Frain once remarked that it's easy to write CSS code, but it is hard to scale and support it. This article describes the set of solutions

I have been working to help create styles that are to be used across multiple projects and teams; a Style-guide that should live long and…

Do you remember when working with CSS was like add /* */ to your index.html just before the /* */ 🙄 ?

New Relic engineering teams sometimes encounter CSS versioning conflicts—here’s how we solve the problem.

A tutorial on working with Sass and BEM when building a more obscure than usual component.

Looking at data for some of the most popular websites, we repeat ourselves too much in CSS; using declarations just once is often one solid avenue to avoid repetition; together, we need to put more focus on style sheet optimization.

This is a real worry these days. I've heard it from lots of lots of developers. The years tick by on their projects, and all they ever seem to do is add

Can't find your Sass or JavaScript component files? Well, here's a way to organize them properly :)

Are you afraid of breaking your website when you change CSS? Here's how to overcome it with namespaces.

Since publishing MaintainableCSS I’ve received some criticism from advocates of atomic CSS. One person said they puked up all over their…

Every time I read a hit piece on Atomic CSS, I feel compelled to respond. I can’t help it. I like thinking and talking about this stuff.

There has been controversy about Atomic CSS (or Functional CSS if you prefer). Much has been written, but what about some cold hard…

Our Community, not Companies, Should Build Pattern Libraries

9 fairy tales

By adopting inline styles, we can get all of the programmatic affordances of JavaScript. This gives us the benefits of something like a CSS pre-processor (variables, mixins, and functions). It also solves a lot of the problems that CSS has, such as global namespacing and styling conflicts. For a deep

Creating and documenting a product design system

Writing scalable CSS is hard! We've taken a formalized approach toward writing it, to make it simple, readable, and predictable.

Finding common pain, articulating value and selling the vision

Brad Frost recently wrote about managing technology-agnostic design systems. In his post, he recommends using a technology that doesn’t tie itself to any specific framework. When I was at Yahoo!,...

The shiny new The Times and The Sunday Times has just been released. I thought it would be a good idea to write an article about the UI…

Looking into the various ways we use the 'Don't Repeat Yourself' principle and the reasons against sometimes using it.

Dave Rupert recently tweeted asking a question that I see quite often: .some-context .thing { /* special rules and overrides */ } Does that go in thing.css or some-context.css? Then, Har...

Growing a product is an eternal balancing act. Applying a Design Systems approach to every level of your product – not just the UI – will help you to maintain control over that balance and prevent any one force from dominating too much.

Coding in any language is hard before you spend time mastering it. Imagine what your JavaScript would look like if you never took the time to learn about OOP or

Build UIs in a better way: from the component up

These days, I often find myself hearing people say “we use BEM” or “we use SMACSS” and the question that often comes to mind is “how exactly do you use them?” Coming up with a catchy na...

Design systems make deciding in the browser much easier if you have the right ingredients.