The best interfaces are built by people who speak both languages.

Why this site exists

"Design developer" isn't a job title; it's a way of working. It's caring about kerning and render performance. It's treating easing curves as design decisions and design tokens as code. For years that way of working lived in the gap between two disciplines, documented nowhere in particular: half of it in design blogs that never showed the code, half in engineering blogs that never explained the taste.

design-profiler exists to close that gap. Every piece we publish assumes you care about both sides of the screen: the spec text and the feel, the DOM tree and the type scale.

The discipline has a name now

The industry caught up. "Design engineer" went from an informal description to a role that companies hire for by name. Vercel, for one, has written publicly about how its design engineering team works and why the hybrid matters. The 2025 State of CSS survey tells the same story from the language side: features that once lived on wish lists (:has(), container queries, subgrid) are now everyday practice, which means the craft of using them well is where the leverage moved.

That's the beat we cover: not "can the platform do it?" (increasingly, yes) but "how do you do it with taste, performance, and accessibility intact?"

What we publish

• Essays & deep-dives: long-form explorations of one feature or pattern, always against real, current browser-support data. See the featured guide to scroll-driven animations.
• Tutorials: step-by-step builds where every step is justified, not just pasted.
• Working demos: every deep-dive ships with a live example small enough to read whole.
• The Tuesday letter: one email a week with the new piece, a browser-support radar, and three links worth your time. Subscribe here.

Editorial principles

• No framework wars. We write about the web platform, used well. Frameworks come up when they're relevant, never as identity.
• Primary sources or it didn't happen. Claims about support, adoption or standards link to specs, MDN, vendor blogs, or datasets like the State of CSS survey and the WebAIM Million. You can check everything we say.
• Show, don't gatekeep. Live demos over screenshots; view-source is a feature of this site, not a leak.
• Accessibility is table stakes. If a pattern can't be used from a keyboard or a screen reader, it isn't finished, and we hold our own pages to that bar first.
• Written by practitioners. Everything here is written by working design engineers, not a content farm and not a language model on autopilot.

Who writes this

design-profiler is written and maintained by the design-profiler Collective: a small rotating group of practicing design engineers who build interfaces for a living and write about it weekly. We keep bylines collective on purpose: the work is peer-reviewed inside the group before it ships, and the site speaks with one editorial voice.

Our patron saints, in framed quotes above the metaphorical desk:

"The details are not the details. They make the design." Charles Eames

"Good design is as little design as possible." Dieter Rams, the tenth of his ten principles

Corrections

When we get something wrong, we fix the article and note the change at the bottom of the piece. Spotted an error? Write to us; corrections earn our genuine gratitude and a thank-you in the changelog.