CSS: Weekly Summary (January 12-18, 2026)
Key trends, opinions and insights from personal blogs
There’s been a curious hum around CSS this week. Little bursts of fascination, a couple of practical nudges, and one story that feels like a soap opera for the front-end. I would describe the week as a mix of tinkering and tidy-up work. To me, it feels like people are polishing corners of the web where you usually don’t stop to look — gutters, SVG filters, the exact behaviour of 100vw — and also taking stock of what we still carry around from older habits.
Early week: visuals and festive code (01/12–01/13)
On the 12th, a few posts leaned into visuals. Amit Merchant dived into SVG filters and their practical charm. The post walks you through making a water ripple effect on text, using
Also on the 12th, ReedyBear posted an archived Christmas theme. It’s cosy, a little like opening someone’s old decorating box and finding a handful of ornaments with notes attached. The post gives concrete CSS snippets and design choices for the holiday skin. There’s a clear affection for the details — colors, ornaments, small layout decisions — and also an admission that a new theme is coming. That bit of future-talk is nice: hints but not the whole reveal. If you do seasonal styling or like seeing how folks scaffold a theme, this is worth a peek.
On the 13th, Remy Sharp wrote a piece cheekily titled “Bytes I can delete after all this time.” It’s part reflection, part modern toolkit checklist. I’d describe the post as practical and slightly wry. Remy lists CSS things like text-underline-offset and gap, and nudges about AVIF images and handling JS errors better. The tone felt like someone unpacking a backpack after a long trip — saying, “Here’s what I kept, and here’s what I don’t need anymore.” It’s the kind of post that makes you check your own toolbox and think: yeah, maybe that old workaround can finally go in the bin.
There’s a theme in these first few posts: playful cosmetics (SVG ripple), ritualised design (Christmas theme), and practical housekeeping (modern CSS properties). They’re different flavors of the same urge: make the web prettier, but smarter too.
Midweek: layout, viewport quirks, and craft (01/14)
Midweek, layouts took center stage. Alex Chan wrote about building a movie collection site with CSS Grid. The piece is both a how-to and a small lesson in patience. It starts from unstyled HTML and walks through grid setup, hover effects, lazy-loading images, and the little frustrations that come up when items don’t line up. There’s a useful honesty about those moments when you realize you didn’t quite understand the layout structure you just coded. I’d say the post is best for someone who knows the basics of grid but needs a nudge on composition and practical traps.
Then there’s a small technical bombshell — or at least a relief — in Bramus writing about viewport units. Chrome 145 (under certain conditions) now makes 100vw scrollbar-aware. That’s one of those subtle platform shifts that matters a lot when your layout depends on full-width elements. The post goes into the history: why 100vw used to cause layout jumps and how the CSS WG decided on a solution. There’s also advice: use scrollbar-gutter: stable when you want predictable space for scrollbars. If you’ve wrestled with flickering horizontal scroll or awkward side gutters, this piece reads like a tiny but welcome patch for an old annoyance. It isn’t flashy, but it feels like fixing a squeaky door hinge.
Also on the 14th, Maurycy published a guide called “How to write your own website.” It’s a friendly reminder that owning a simple HTML site is still a great way to learn. The guide stays intentionally shallow — essential tags, basic formatting, hosting options — and it nudges you to experiment. To me it reads like a neighbour telling you, “You don’t need a fancy toolbox to hang a picture.” Handy for beginners, and oddly comforting for old-timers who sometimes forget the joy of minimal setups.
This day’s posts share a quiet throughline: layout clarity and platform awareness. People want predictable behaviour from the browser, and when the platform gives it (or when docs explain it), developers breathe easier.
Mid-to-late week: portfolio polish and weird industry news (01/13–01/15)
There was a lovely case study from Lynn Fisher on the 13th. She walked through a 2025 portfolio refresh that uses a fixed-width site that visually stretches and squashes as you resize the window. There’s a theatrical quality to it: part performance, part engineering. The implementation mixes CSS and JavaScript for that elastic feel. The post is a good reminder that websites can be characterful without being chaotic. It’s like choosing an outfit that’s playful but still fits the occasion.
Then the week took a turn into tougher terrain. Chris Ferdinandi wrote a post called “When the tech leopard eats your face.” That’s blunt, and the content matches the bluntness. Chris covers layoffs at Tailwind and frames them against larger trends in the industry, notably the impact of AI and business decisions that can devalue skilled professionals. The post is part critique, part indictment of certain behaviours in the ecosystem. It’s messy. There’s blame, there’s irony, and there’s a sense that tools and business decisions can be out of step with the people who keep the web running. This one reads like local news from a town you thought you understood.
It’s important to mention this here not because it’s purely about CSS syntax, but because stylistic tools like Tailwind are entwined with how teams hire, build, and value design work. The post makes you look up from selectors and ask: who gets to decide what’s worth a developer’s time? There’s a lot to think about, and it’s not tidy.
A little levity: creativity and nostalgia (01/16)
On the 16th, Alex Chan popped back in with something lighter: parody movie posters riffing on CSS and web dev terms. It’s a cheeky, clever side-project that mixes typography and humor. You’ll see titles that make you grin if you’ve spent time debugging z-index problems or wrestling with layout. The craft behind the posters — the geometric image tool and the deliberately constructed jokes — shows that CSS is still a place for fun, not just function. It’s reassuring, like finding a cartoon in your morning paper.
End of the week: site redesigns and grid upgrades (01/18)
The week closes with Dave Rupert sharing what he calls “The best version of my site so far…” It reads like the sort of reflection where someone has tried a sequence of changes, learned a few things, and then settled on a version that “clicks.” The three main changes were: switching to a monospace font, adopting named CSS grid lines, and building better multi-page view transitions. There’s an interesting takeaway here: small, intentional changes can make a site feel notably better. I’d say Dave’s work is an argument for deliberate simplification rather than endless reinvention. Named grid lines in particular feature as a neat productivity win — clearer structure, fewer mental gymnastics when placing items.
There’s a small pattern across these redesign posts — Lynn, Dave, and ReedyBear are all doing variants of the same chore: keeping a site that’s both personal and maintainable. It’s like tuning an old car: you want it to look sharp, but you also want it to start every morning.
Recurring themes and where writers agree (and don’t)
Small tools, big impact. A lot of posts highlight small CSS features or platform changes that quietly improve day-to-day work. Think text-underline-offset, gap, named grid lines, or scrollbar-aware 100vw. None of these are fireworks, but they save a surprising number of headaches. I’d say the week’s mood is: polish over spectacle.
Visual experiments are alive. SVG filters, parody posters, elastic layouts — people still enjoy visual play. When Amit Merchant shows ripple text and Alex Chan makes movie posters, it’s a reminder that CSS is as much a creative medium as it is a utility.
Practical housekeeping keeps surfacing. Remy’s list of bytes to delete, Dave’s simplifications, and the movie-site author’s step-by-step grid strategy all point to the same idea: there’s value in cleaning up. Clean CSS is less fragile. It feels… lighter. Like clearing out a junk drawer.
Platform behaviour matters. The 100vw change is a standout example. Browser updates that remove little inconsistencies are a huge deal — they prevent entire classes of layout hacks. When the browser-help arrives, everyone benefits.
The human side of tooling is tense. Chris Ferdinandi’s post is the week’s thorniest piece, not because it’s about a CSS property, but because it’s about people. It questions the sustainability of certain business models and the ethics behind some decisions. Developers and designers are thinking about more than code; they’re thinking about livelihoods, value, and the consequences of big bets on AI. The conversation is messy, and it’s not going away.
There’s not always agreement. For example, some posts celebrate fancy visual treatments. Others quietly argue for minimalism and clarity. Neither stance is absolutist here; it’s more like people exploring different answers to the question: what makes a site feel well-made?
Little technical threads worth noting
SVG filters: these are useful beyond gimmicks. Amit Merchant shows that you can get readable, animated effects without a canvas or big JS. If you’re into subtle branding or hero animations, SVG filters are worth bookmarking. They’re like spices — use a little, and you notice the difference.
Named grid lines: Dave’s praise is practical. Naming lines helps you reason about layout the same way street names help you navigate a city. It reduces the mental map you need to carry.
Scrollbar and viewport handling: Bramus’s post is a reminder to check behaviour across new browser versions. 100vw being scrollbar-aware fixes a long-standing source of layout jank. If you didn’t even know this was a thing, you were probably the one who accepted a small horizontal flicker and moved on. Now you can fix it.
Image formats and performance: Remy’s piece nudges toward AVIF. It’s not headline-grabbing, but it’s the kind of tweak that loads faster and saves bytes, especially on image-heavy sites.
Accessibility and structure: It’s subtle, but several posts hint at structural thinking that helps accessibility — thoughtful grids, reduced layout surprise, predictable gutters. None of the posts are a deep A11y manifesto, but the best work this week quietly made pages more comfortable for users.
Style, craft, and the personal web
A couple of authors leaned into the idea of owning a small, personal website. Maurycy’s beginner-friendly guide and Lynn’s portfolio story both feel like arguments in favour of running a site that reflects you, not an algorithm. There’s nostalgia here — but useful nostalgia. It’s not just “remember when we had hand-coded pages?” It’s more like: owning your corner of the web gives you the freedom to experiment without performance theater or platform politics.
That small-site ethos ties back to some practical changes this week. If you run a site that matters to you, you’ll notice things like 100vw or named grid lines. You’ll care about small improvements because they make your site smoother to use and easier to manage.
Tone of the conversation: practical, playful, and occasionally worried
Most posts are practical and playful. There’s curiosity. People show code and say: try this. That’s the friendly, hands-on vibe that makes blog posts useful. The worry in Chris’s story is louder because it’s about jobs and sustainability, and that worry colors the rest of the week if you think about ecosystem health. It’s like hearing a neighbour argue about the developer market while you’re deciding whether to paint your fence — you can ignore it, or you can listen and think about what you’ll do next.
A few personal reactions (a bit of navel-gazing, but honest)
I liked how small changes kept coming up again and again. It felt like a chorus singing the same tune: tidy your CSS, embrace new small features, and avoid brittle hacks.
The SVG ripple and the parody posters reminded me that CSS is still fun. You can make things that aren’t strictly necessary and still learn something technical in the process. It’s the web equivalent of doodling in the margins.
The Tailwind/AI piece left a sour taste. When tools that make work easier become reasons to devalue the people who do the work, that’s a real problem. The post forces a conversation about how we measure value in design and development. It makes you think twice when the next “productivity booster” comes along.
Practical posts about grid and viewport behaviour were quietly satisfying. They’re the posts you save and come back to when a specific problem bites. Like a well-labelled recipe card.
If you want to dig deeper
Most of these posts are short experiments or thoughtful how-tos. If you like visual play, start with Amit Merchant for SVG filters and Alex Chan for his movie posters. If you care about layout resilience, Bramus’s note about 100vw and Dave Rupert’s grid naming are good follow-ups. For mental housekeeping and performance nudges, Remy Sharp’s list is the kind of checklist you’ll want beside your editor. And if you’re curious (or angry) about the business side of tooling, Chris Ferdinandi’s take will make you think — perhaps more than you wanted to.
There’s more to each post than I can capture here. The code snippets, the tiny implementation tips, the screenshots — those are worth the trip to the source. Think of this as a map that points you to a few interesting lanes, not a substitute for the streets themselves.
So if you’ve got a minute, click through. Tweak an SVG. Try a named grid line. Consider whether a new tool is a friend or just shiny packaging. And hey, if you find something neat, you’ll probably see it show up in someone else’s blog next week, because that’s how this small ecosystem keeps humming.