We used to make websites because it was fun and at a point we lost the way. We need to make dumb shit! Make useless stuff; make the web fun again!

A post about subgrid and the level 2 spec, what is happening and how can you keep track of progress.

Say you have a really long word within some text inside an element that isn't wide enough to hold it. A common cause of that is a long URL finding it's way into copy. What happens? It depends on the CSS. How that CSS is controlling the layout and what the CSS is telling the text to do.

Here is an overview of what we will be covering in this article: Design mobile first for Google; Structure content for organic visibility; Focus on user intent (not keywords); Send the right signals with internal linking; A crash course on image SEO; Penalties for pop-ups; Say it like you mean it: voice search and assistants.

As I dive into more articles, tutorials, courses, and projects about CSS-in-JS, I encounter a ton of garbage markup and styles. It’s almost like saying “we’re doing everything in JS” gives developers permission to flush a few decades’ worth of HTML/CSS best practices down the toilet. I see really basic, cringeworthy stuff like inputs without labels, and really hacky styles that look like Dreamweaver generated them. Seeing enough of this stuff makes me question whether CSS-in-JS advocates truly understand CSS as a language or care to preserve hard-earned CSS best practices.

JavaScript has always been a proving ground. We write code that simulates how we want the web to work. We had dozens of different JavaScript based responsive image solutions before a spec was settled on and adopted by browsers. CSS-in-JS is the development community trying to imagine how CSS should work in the future to solve a specific set of problems.