Archive

A response to an idea to merge HTML, CSS and JavaScript into one language.

A bit about designing min-content, max-content and auto, and how they can be used.

Recreating old posters, I figured there are at least two approaches to deciding how many grid tracks your component or page needs: one can make it visually perfect, the other is more flexible if content is bound to change.

In cards, you could use grid tracks instead of padding.

Now that Grid Layout is seeing more adoption, it seems like a good time to remember that websites don’t need to look the same in all browsers.

If you have learned how to use Grid Layout, you might wonder what to use it for. In this post, I will give some use cases where I think Grid will excel.

New CSS possibilities are ending the unrealistic content problem and the generic layout problem. It’s a great time to build layouts in CSS!

I’ve rewritten the CSS for this blog, using Grid Layout for the lay-out. These are some of my findings.

A look into the early days of CSS and changes that have occurred since.

On the difference between pseudo classes and pseudo elements

Some notes I wrote after reading the CSS Grid Layout specification.

My thoughts about styling with classnames versus styling with HTML elements. TL;DR: we need both.

On the cognitive overhead of cascading

We can soon use ‘just’ CSS to describe our lay-outs. But, arguably, that leaves us with a naming problem.

I think for large websites and organisations, in addition to having a component system, it makes sense to have one agreed-upon, shared-between-projects grid system.

To solve CSS problems, it is much more important to understand the spec and how browsers implemented it, than which abstraction to use.