Josh Black

I feel so lucky that I got to work with you when I first joined! Cheers to the next big thing, hope it's a blast 🍻

Feels like I'm missing something so obvious 🤔

For example, this codepen from Chris Coyier totally works: codepen.io/joshblack/pe... but then bringing it over into Next.js world it doesn't: codesandbox.io/p/devbox/3n9...

Having the hardest time getting events from custom elements working alongside React components in Next.js 🤔 Anyone else have luck with this? It seems to work fine standalone but as soon as I'm in Next.js-world the events stop being fired. I assume something is going on due to SSR? But who knows 🤷‍♂️

Just wanted to +1 the design systems use case! We’re starting to use it for Primer over at GitHub.

Definitely would make sense to me 👍 I think potentially changes to options could also be minor too depending on if they’re broadened vs narrowed.

Super curious, what makes you decide what feature set to cover for a component when looking across libraries?? 👀

God that would be nice, especially from a docs perspective. I feel like DS teams spend a lot of time on effective docs with good examples and I would love to bring these into the context for agent mode or even with things like copilot reviews to help bring guidance closer to everyone’s workflow

When it comes to helpful layout components, what have folks found helpful to include in their design systems?? 🤔 In the past I’ve done ones for Grid, Stack, or a UI shell / page layout type
one but would love to know if there are others people like to include 👀

Also just wanted to say having something like this has also been very helpful for our move internally from the `sx` prop for styling with styled-components to CSS Modules. Wish we had something like this for our token change a couple years ago 😂

Nice, I love this! 🔥 Finally got around to putting up what I was talking about above in a PR: github.com/primer/react..., it's been interesting playing around with to see if it helps out at all 🤔 My hope is that it could help improve code being written with agent mode but who knows lol

After doing design systems work for a bit, the most surprising skill to have learned is how to gradually and safely migrate code (and how to design code to make that easier in the future 😅) With Primer, we own more of the migrations compared to Carbon and it's been interesting comparing the two

The field in the project is especially cool since it let's us annotate issues with a number of the `sx` usages impacted by taking on the work in a particular area (basically codeowners) and is updating daily as the migration is ongoing.

YouTube video by GitHub Every component, everywhere, all at once

Having Primer Query (www.youtube.com/watch?v=lryI...) has been so nice for migrations over the years. Our team is going through moving from styled-components (with a `sx` prop) to CSS Modules and it's been amazing tracking this with charts in datadog or even as fields in our GitHub projects

Oh definitely! Would love to see what you're getting into 👀 Really all my exploration has been is around providing more information in agent mode through tools that help the agent understand components, tokens, patterns, etc to (hopefully) make it better at using the system 😅

Has anyone had success with an MCP server for their design system?? After seeing the shadcn features for their registry would love to try it out and see if it helps or not 🤔

Wire but then with custom elements they are forced to ship JS to the browser.

I think as an overall strategy it’s been difficult without investing more in declarative shadow DOM. That’s been one of the hardest things is making the progressive enhancement story a good one. Especially on the React front, I feel like server components are trying to reduce what we send over the

I love this topic! I’ve been thinking about it a little bit for Primer. I’m curious how others feel about it too 👀 Personally I feel like there are cases where a custom element really feels like a better fit.

Ahhh, hi!! It's been so long, hope things are going amazing 🥳

I think for me the fuck you would feel very personal and hurtful. If someone says that they’re really angry. Fuck off is more casual, you’d hear it in a group of friends with each other and it doesn’t mean they’re angry necessarily. Just exasperated and they want to poke fun at you

I’d love to start writing more (especially about design systems) this year and I’m curious if I did if there are any topics that folks would be interested in here 👀

I did this a ton with TikTok last year 😭 ended up removing it and replacing it with kindle to try to do something different lol

It really is ridiculous, it’s so easy to get to the point where you don’t want to upgrade or are willing to pay a premium to not have this stuff added to things you use everyday.

Loved the post! Thanks for writing it up and sharing. Excited to see what feedback we get on this page 👀 do you think there is a place for a new role with these kinds of semantics or is it better with current roles and the interaction techniques described in the post??

GitHub’s updated Commits page and the interactive list component This post is about interactive lists on GitHub, and how to use them.

Last post of 2024! I wrote about GitHub, interactive lists, and feeeeeeeeelings. ericwbailey.website/published/gi...

I’m irrationally excited for Ghostty 1.0: mitchellh.com/writing/ghos.... A month ago, I don’t know if I even realized how many terminals had come onto the scene as an alternative to iTerm but now I can’t wait to try them all 👀 (currently using WezTerm)

For folks that have made similar tools / or track usage at their company, I'm super curious what you've found most helpful when shipping this kind of tool for your team 👀

YouTube video by GitHub Every component, everywhere, all at once

This kind of tool was my dream to have back on Carbon: www.youtube.com/watch?v=lryI... (tool usage at ~6:00). Being able to query all the ways a component is used is like a super power for decision making. It's also pretty nice to be able to finally measure usage lol

Being able to try things out before fully committing is always helpful (really helps me build confidence when I'm not so sure about something 😅). Also great for running experiments in production to help validate certain types of changes.