CSS Grid

CSS Grid Gotchas And Stumbling Blocks

In March this year, CSS Grid shipped into production versions of Chrome, Firefox and Safari within weeks of each other. It has been great to see how excited people are about finally being able to use it to solve real problems.

CSS Grid is such a different way of approaching layout that there are a number of common questions I am asked as people start to use the specification. This article aims to answer some of those, and will be one in a series of articles on Smashing Magazine about layouts.

Brilliant approach to CSS

CSS Inheritance, The Cascade And Global Scope: Your New Old Worst Best Friends

I’m big on modular design. I’ve long been sold on dividing websites into components, not pages, and amalgamating those components dynamically into interfaces. Flexibility, efficiency and maintainability abound.

But I don’t want my design to look like it’s made out of unrelated things. I’m making an interface, not a surrealist photomontage.

As luck would have it, there is already a technology, called CSS, which is designed specifically to solve this problem. Using CSS, I can propagate styles that cross the borders of my HTML components, ensuring a consistent design with minimal effort. This is largely thanks to two key CSS features:

inheritance, the cascade (the “C” in CSS).

CSS

Reading CSS at BBC Sport (Part 1) lead me to this presentation by Harry Roberts and then to CSSWizardry on GitHub.

Roberts also has created some basic components including the “nav” abstraction and, of course, Nicole Sullivan started all of this with back in 2010 with the media object

The BBC Sport article also talks about BEM which I’ve never really embraced but this might help me along.

Update: 06/21/16 Also found this book titled “Scalable and Modular Architecture for CSS” which serves as a good intro with some examples.