Thinking about different states of mind guiding the way that we approach #designsystems and #webdwvelopment. What do you think? Are you more of a gardener or a butterfly collector? A taxonomist or a geneticist? Let’s talk. gehrmann-design.de/blog/buterfl...

I really really really want to make @penpot.app work for me. I really do. But it’s a challenge.

Hello, TypeScript users! What advantages does using TS offer you that JSdoc doesn't? What are the points that make it worth the overhead of a build? Would you skip it for certain project types?

I am uncomfortable with our reliance on npm, GitHub, build tools and so on. We see big infrastructure fail spectacularly. Because we ignored the decentralized nature of the web. Going Buildless should not be a revolutionary concept. modern-web.dev/guides/going...

I make a point of talking about "html custom elements" or "custom element" instead of "webcomponents". Many colleges use react, and the term "component" comes with conceptual baggage that I try to steer around.

Auch wenn das viele hier nicht hören wollen: erschwingliche Lebensmittel sind eine der größten sozialen Errungenschaften, die eine Kultur haben kann.

However, we must be clear that progressive enhancement is not dependent on whether JavaScript is enabled. JavaScript, CSS, and HTML have evolved, and progressive enhancement is very much about balancing modern features, ensuring a site works for everyone, and making robust layout decisions.

The biggest question is: why? The argument that the world is made for the human shape definitely doesn’t work. We are surrounded by bad „good enough“ ergonomics everywhere. And balancing on two legs is hard. We ourself struggle with. We use sticks and walkers. Just add more legs. And arms.

“ More chaos brings more power. More power brings more control. ” by @switchangel.bsky.social www.youtube.com/watch?v=GWXC...

One of these technologies is actually quite easy to grasp. It is unknowingly used by everyone, is really easy to produce, and shockingly, few people are aware of it or actively use it.

I am always surprised and frustrated by how much behavioral science informs marketing, yet how little it informs policymaking. When you talk to politicians about their plans, you sit there feeling like you're in a madhouse devised by Lewis Carroll, wondering if they really think this will work.

I signed up for “Web Components Demystified” by @scottjehl.com and I can't wait to dig in. This week you can get it for 25$, which is an absolute steal, using the code OCT25-26. webcomponentsdemystified.thinkific.com/courses/web-...

Halloween 🎃 is just around the corner. So behold the dread of every single person in tech: naming things. 👻

There's a new #CSS Working Group poll to get feedback on different names for the infamous 'Pinterest' layout. - Since it uses many of the grid-* properties, `grid` will be in the name somewhere - We don't use metaphors in CSS names, so `masonry` is not listed here docs.google.com/forms/d/e/1F...

I bought this this morning and I’m over half way through it. Probably the best $25 I’ve spent in years. I use web components for my blog posts and have known for a while that there are big gaps in my knowledge, and this has filled a whole bunch of them.

Did we all celebrate that `::details-content` works in all major browsers now? 🎉 developer.mozilla.org/en-US/docs/W...

True words spoken with ease

Should we go in o a class diet? In #CSS Devs use way to often class names. Patterns like BEM have encouraged an explosion of class names, that often rely on Javascript to be updated. Using pseudo classes, and semantic attributes helps us to work closer with the DOM.

📝 New Post: The Killer Feature of #webcomponents A quick dive into the Custom Elements Manifest and why this community standard is a 10x effort multiplier. daverupert.com/2025/10/cust...

"Then, delete the javascript you just wrote and repeat the task using CSS alone instead!" This practice prompt by @scottjehl.com is basically my job description. And I want it on a T-Shirt … … after I stoped giggling uncontrollably.

WOW! That's so incredibly useful!

Lassen wir uns hier keinen Bären aufbinden. Was als „Verbraucherschutz“ daherkommt, ist in Wahrheit ein Kampf um Identität und philosophische Reinheit. Es geht nicht um Aufklärung, sondern um Ordnung; nicht um Sicherheit, sondern um Symbolik. #Veggiburger #EU

✍️ New post: Euro­pean Tech Alternatives 🇪🇺 #blogtober #tech #software #europe matthiasott.com/notes/europe...

2 reasons you should be using single color gradients in CSS - YouTube | Super cool! @kevinpowell.co | www.youtube.com/watch?v=8Nfa...

So. How would I add documentation for custom invoker commands in custom elements manifest and jsDoc? #customElements #webcomponents

Accessible CSS carousels are here! Our new post, co-authored with @flackr.bsky.social and Lucas Radaelli (x.com/lucasradaelli), walks you through building them with the new APIs. The APIs are Interop 2026 proposals, soon on their way to all browsers. 🤞 developer.chrome.com/blog/accessi...

Fund thing is that with today’s capabilities it should be trivial to host a static fund little page again. We dropped the ball a bit on this a bit. Time to pick it up again.

Regular reminder that it’s really sad that @bsky.app doesn’t support natively SVG and animated #SVG. Why do we rely on GIF? In a world where we are integrating interactive 3D in our apps the usage of plain vector files is completely stuck. g12n.github.io/svg-animation/

If removing the stylesheet renders your element useless and you need to rely on JavaScript to make it work or hide it from the user, then you have failed to separate concerns.

While Custom Elements Manifest (CEM) seems to be a really powerful tool for documenting javascript based elements. For my current design System Work I am a little bit lost for options to documents #CSS Custom Properties and plain class names that reside outside of javascript pipelines. Any tipps?

Still fighting form controls with endless CSS? Tim Nguyen from Apple reveals upcoming improvements that will finally make them customizable with pure CSS #Forms #DevSummit25 Tim Nguyen at Dev Summit 25 bit.ly/3Iooh20

Hey just saw that the SVG Working Group is back together! Congrats! Note: The MathML Working Group is still going! We meet once a month, and would love to have all the browser vendors join and participate in our discussions.

I would love to see @miggi.me and his team to contribute to the next iteration of SVG standard. Especially variable width strokes wait for standards for ages.

👍👍👍👍👍

Can you help me out, bluesky? 🦋 I recall someone once writing in an article about how shadows are supposed to be darker, so white shadows don't make sense even when we have a dark theme. Does anyone else recall that article? Can anyone help me find it again? Reposts appreciated. Thanks! #CSS

PLEASE UPVOTE AND SHARE, I DESPERATELY NEED THIS FEATURE EVERYWHERE.

Exactly. Every argument you make for segmented scroll controls and indicators you got to make for linear scroll controls and indicators as well. There isn’t any reason to not treat them consistently. Including their focus behaviors, keyboard and voice controls.

Why and how should the lower element be in the html while the upper isn't. Why and how would we treat indicators for continuous scroll differently to indicators for segmented (snapping or paginated) scroll?

You can host a website on really primitive hardware. It’s surprising that not every router for home usage offers this built in.

Just a reminder that it's perfectly normal to feel confused and slightly overwhelmed when choosing a technological solution. There isn't usually a right or wrong answer, just multiple ways to go about it. Please free yourself from the urge to seek best practices which are often just marketing lies.

I've been using a "follow-the-leader" pattern with CSS anchor positioning lately so I decided to write about it! You set up a "follower" element and dynamically update the anchor on an event/state. Surprisingly simple and effective. Read more with demos!: 👀➡️ una.im/follow-the-a...

This is a great example of why I think ARIA rules such as 'aria-orientation' are seriously problematic. They force purely visual concepts into the DOM. Layouts and orientation can change based on device type, device orientation and even the writing direction of a language.

This kind of Legislation reminds me so badly of pink margarine. I am flabbergasted this kind of politics still exists. @99pi.org 99percentinvisible.org/episode/i-ca...

I am really, REALLY uncomfortable to clutter static DOM with elements that only work if javascript is present. Accessible and sustainable Code must as well be prepared for bad bandwidth, missing Javascript support and even dramatic layout changes based on device size or preferred UI settings.

Talking about separation of concerns for #a11y. I think should not be written into the #html DOM. The layout it purely in the domain of #CSS. This property reads like an artifact from times before #responsive design. Now I need to involve #JavaScript for a menu. developer.mozilla.org/en-US/docs/W...

We mentioned on Winging It that we might show some of our favorite browser tips. Here's one of many that I find delightful. If you are working with shape-outside, then Firefox has a great path editor. I made a quick video to show how it works.

You’ll want to look at the @11ty.dev file passthrough API www.11ty.dev/docs/copy/ This is how I bring my node_module files through to my build. Not the most elegant, but the path of least resistance

I mean: something about that just feels off.

Ok. This might sound like a dumb question: how do you integrate standalone Webcomponents like @darn.es <play-button> into an @11ty.dev site without extra build. I basically want the comfort of installing stuff with npm, but only drop the delivered files into my website build.

There are many people who point out when an alt is missing from an image on social media. It is therefore very surprising that there is no criticism when books are only published in print instead of in digital form.