Most of the design work that actually matters will never make it onto your portfolio.
It won't get likes on Dribbble. Nobody's making a conference talk about it. But the quiet, unglamorous decisions — should this be a modal or a new page? Why does this dropdown keep breaking? — are where the real craft lives. And today's stories are a good reminder that getting these small things right is, in many ways, the whole job.
When a modal is wrong, everyone feels it
Vitaly Friedman has published a practical decision tree for one of the most common UI calls we make: modal dialog or separate page? It sounds almost too simple to warrant a framework. But think about how many times you've been mid-flow on a site and hit a modal that felt wrong — too much content crammed in, a form that should've had its own space, a confirmation step that broke your sense of where you were.
The framework boils down to some clear principles. Modals work for brief, focused tasks where the user's context matters — think "are you sure you want to delete this?" They fall apart for anything complex, content-heavy, or requiring real input. A separate page gives users room to breathe, a URL to bookmark or share, and a clear sense of navigation.
None of this is revolutionary. That's the point. We've all shipped modals we shouldn't have because it felt quicker or because someone on the team said "just put it in a modal." Having a decision tree you can point to — even a mental one — is worth more than another animation library.
The dropdown bug that's been quietly annoying everyone
Here's one for the designer-developer handoff file: dropdown menus inside scrollable containers have been breaking for years, and most of us have just… worked around it. The menu gets clipped by its parent's overflow boundary, vanishing behind the container edge like it's been swallowed.
Godstime Aburu's written up a proper explanation of why this happens — it's down to how CSS overflow properties and stacking contexts interact — and more importantly, how to fix it properly rather than hacking around it with z-index prayers.
I find this kind of deep-dive invaluable. Not because every designer needs to write the CSS fix themselves, but because understanding why something breaks makes you a better collaborator. When you know that your scrollable card layout is going to clip that filter dropdown, you can design around it — or at least flag it before the dev team discovers it at 11pm on a Thursday.
This is craft. Invisible, thankless craft. But it's the difference between a product that feels polished and one that feels held together with tape.
"I don't think about relevance"
Laura Stein, chief creative officer at Bruce Mau Design, gave an interview that's quietly one of the most grounding things I've read this month. Her line — "I don't think about relevance, I think about doing good work" — feels almost radical in an industry that's constantly asking you to have a take on the latest tool, trend, or paradigm shift.
She describes herself as a lifelong learner, and frames curiosity and depth as the things that sustain a creative career. Not chasing what's current. Not performing expertise on social media. Just… getting better at the work.
It's a philosophy I think more of us need right now. The pressure to have an opinion on every new AI release, every design system update, every framework du jour is exhausting. And it can pull you away from the thing that actually makes you good: spending time with the hard problems in front of you.
Tool spotlight: WordPress lets AI agents run your site
WordPress.com has rolled out the ability for AI agents to manage and create content on your site. It's part of a broader push toward AI-assisted publishing — less manual effort, more automated workflows.
I'll be honest: I'm watching this one with interest but also caution. For solo creators and small teams, having an AI handle routine content tasks could be genuinely useful. But "AI agents working on your site" is a vague promise. The value will depend entirely on how much control you retain, how transparent the output is, and whether the quality holds up without constant babysitting.
If you're running a WordPress site, it's worth exploring. Just don't hand over the keys without checking what it's actually doing.
The bigger picture
There's a thread running through all of today's stories, and it's this: design quality is made up of thousands of small, boring decisions.
Modal or page. Fixed dropdown or clipped one. Thoughtful career path or trend-chasing one. None of these choices will win you an award. But they compound. Over weeks and months and years, they're the difference between a designer who ships reliable, considered work and one who's always firefighting.
In an era where AI can generate layouts, write copy, and now apparently manage your whole website, the human value isn't in production speed. It's in judgement. Knowing when to use a modal. Knowing why a dropdown is breaking. Knowing that doing good work matters more than doing visible work.
So basically…
Don't sleep on the small decisions. Build yourself mental frameworks for the common UI calls — modal vs. page, inline vs. overlay, scroll vs. paginate. Understand enough about implementation to spot problems before they ship. And if you're feeling the pressure to stay "relevant," maybe take Laura Stein's advice instead: just focus on doing good work.
The boring stuff is the whole job. And that's not a bad thing — it's where the craft actually lives.