Josh Black

The idea is kind of what Mitchell talks about in: mitchellh.com/writing/my-a... with having just one agent running in the background.

Not sure if this 100% what you’re talking about but I love the cli tools for stuff like this (Claude code, copilot cli, etc). Really easy to go from plan mode to implementation (or just exploration) and you can decide if it’s worth opening a PR or not.

I feel like any way that helps practitioners in either space connect is so helpful. It builds connections, relationships, and can really help both get to the bottom of opportunities or challenges and lead to proactive problem solving without the endless game of telephone between org layers.

I think nowadays they have something similar to what you describe (I think they call them away missions?) but even having some idea of customer success being a part of your role would be so helpful. Even projects like building your own site or custom tooling UI with the DS can be insightful

This topic has been on my mind for a bit the last year (relationship between system/product) and one thing I've come to really appreciate when I joined Carbon was how the group was meeting with all the other teams on Bluemix (IBM Cloud) at the time. It helped out so much with stuff like this.

So cool! Also very curious to see the magic behind the ButtonSlot component 👀

Apple Health has decided that now that I have a newborn it is time to talk about my sleep score 😂 I get it, Apple, I also want better sleep at nights but that might not happen for a bit 😅🥲

It’s so much fun as a change of pace and the info you get out of it is such a game changer 🤯

Why Federated Design Systems Keep Failing Why do federated design systems keep failing? I watched it happen twice at Spotify. Here's what actually happened, where they broke down, and why centralised models usually work better.

A few years back, I nearly wrote "The Fallacy of Federated Design Systems." Then @nathanacurtis.bsky.social beat me to it. But what happens when you try it anyway?

At Spotify, I watched federated fail twice, resulting in a huge number of barely reused components and damaged trust in design systems.

Just wanted to say thanks so much for taking the time to write this! Really enjoyed reading it and am sharing immediately in our work Slack 👀 haha

I really credit so much of the Carbon ecosystem around this, personally. There is no way the Svelte, Vue, or React Native projects would have existed without this. So many of the DS sub-systems were created using this model too

The biggest surprise to me with people against it is that treating the project as OSS really sets it up for success in so many ways (imo). The mindset behind it sets you up for contributions, shared ownership, and ultimately a roadmap to scale out the DS model as the project grows.

Another one that came up was release confidence/testing since we are outside of the UI monolith. Thankfully for that we came up with a good process to test PRs in the OSS repo against internal ones 😮‍💨

We've definitely gone through this a couple of times now, curious if others have had these challenges too. Probably the biggest one was moving our docs private so that we could deploy on GH's infra for a running server (definitely a bummer even just losing those edit page links 😞)

Just wanted to say best of luck with your new adventure 🫡 It’s been such a blast working together, you’ll be missed so much! I hope our paths cross sometime soon for more design system shenanigans 🤞

Relevant section: “…truncation is acceptable if the component's full content is available on focus or after user activation and an indication that this information can be accessed, is provided to the user in some way besides the fact that it is truncated.”

Link to the SC that I’m referring to: www.w3.org/WAI/WCAG22/U...

For folks that do truncation patterns in their components, how do you handle SC 1.4.4? We often see requests for truncation in different parts of the UI in GitHub but it seems difficult to satisfy this in a lot of scenarios 🤔

Just wanted to say if you're looking to track down when the toasts page went up @ericwbailey.website added it last week!

This reminded me that if you like Cholula definitely give Valentina a try 😋

Hey! Just wanted to say thanks for responding 🙏 super curious, for your external stylesheet how are you applying shadow DOM styles from it if they are rolled up into one?

I guess the thing for this would be that you would have a network request per custom element style you want to load in? e.g. you could bundle them and serve them together. Or is that not the case?

Thanks @keithamus.social ! Do you know of any good interim solutions or any that you’d recommend? I saw the issue listed out some but obviously not ideal. I’ve seen some hide the custom element until it’s defined as another way to mitigate this but then you can get pop in everywhere 😵‍💫

For folks using custom elements, how do you deal with styles when doing declarative shadow DOM? 🤔 Specifically would love to avoid duplication and also would like the styles present in the initial payload instead of styles having to be parsed from the JS bundle and applied during hydration

Could be cool to try something like this @katielangerman.bsky.social @sid.st 👀👀

Taking a shot at the double focus ring problem using modern CSS A double focus ring is really useful in general but especially so with complex, themed systems. Eric Bailey shows us how to develop a really smart system, using modern CSS.

Focus rings! Plural! I wrote for @piccalil.li about how to create a branded double ring focus effect that is dynamically generated based on the interactive element's text color. piccalil.li/blog/taking-...

Very cool! I love it, thanks for sharing 🙏 I thought it was very interesting to have the `type` live on dropdown here for going between the different types of pickers (combobox, select, etc)

Thanks for sharing! Enjoyed taking a look 😄 Was curious what your take would be on how to do design something like this if the target/tooltip needed to support popovertarget/popover 👀 (if this one already does then ignore me lol)

Finally got around to making an MCP server for Primer: github.com/primer/react... 👀 It's been interesting playing around with tools to provide more context to agents, specifically around our components/tokens/icons/etc and their guidelines. Still holding my breath to see how much it can help 😅

For example, with a tooltip it'd be awesome to have a component with a slot for the trigger and the content but as soon as I mess around with the Shadow DOM I lose the ability to relate these with attributes for a11y. I had assumed this is what ElementInternals was used for but now I'm not sure 🤔