As a blind software engineer who uses a screen reader (and a backer of the accessibility-focused Web Awesome Kickstarter!), I want to emphasize the importance of accessible components. Popular options often fall short, forcing me to build custom carousels, datepickers, and navs. Would love to hear your thoughts on this and how we can make components more inclusive for everyone.
I built a tailwind theming package that creates a custom tailwind plugin. You pass any css color, including hex, and converts it to oklch so you can use alpha values with tailwind. It’s great because with the Tailwind Intellisense extension, you get autocomplete for your custom colors. Also provides helpers for shadcn theming. Currently working on a new one specifically for theming shadcn.
Excellent episode (as usual). I love the camera angles; it really makes it feel like I’m just peeking into your conversation. Also, +1 on that Coolify episode. Got me! Look ma, I’m self-hosting now!
Wanted to echo Scott's suggestion. I started building out my own common component library for personal projects and it's been great for improving my ability to make extensible and composable interfaces, and really thoroughly consider theming and responsive design upfront in my projects. Btw, my new fave feature of the show is those joke intro cards for Scott and Wes. Whoever is writing those is cracking me up!
Loved this episode. I'm building my personal starter project with my preferred stack right now and this felt super relevant. This is the second episode that you've put out that I've thought "Wow, I was just thinking about that". The last one was the React Native episode. Good stuff!
I think there was a point missed on the email link sign-in stuff. The thing that frustrates me about that and also email validation or reset password links is that the links always open a new browser window/tab. Now you have 2 (or more) tabs open to the same website which is unnecessary and possibly could be confusing if you don't remember which tab you were on.
I write all of these things myself every time but it's growing old. I've started a Storybook project for myself to catalog the things I've designed and developed that are "different" enough from each other that I can borrow from.
As a blind software engineer who uses a screen reader (and a backer of the accessibility-focused Web Awesome Kickstarter!), I want to emphasize the importance of accessible components. Popular options often fall short, forcing me to build custom carousels, datepickers, and navs. Would love to hear your thoughts on this and how we can make components more inclusive for everyone.
Do you have any favorite component libs to recommend?
No I don't sorry. That's the problem but I'm going to be releasing some of my own very soon which I hope will be better.
@@Envisionly-YT Please do!!! I'd pay for this!! Like a $100 lifetime license sounds more than fair
IDK what's wrong with me, but I prefer to watch my podcasts. IDK how long y'all've been doing this, but I like it.
Just started earlier this year. Have plans to include more visuals and code into the show
I built a tailwind theming package that creates a custom tailwind plugin. You pass any css color, including hex, and converts it to oklch so you can use alpha values with tailwind. It’s great because with the Tailwind Intellisense extension, you get autocomplete for your custom colors. Also provides helpers for shadcn theming.
Currently working on a new one specifically for theming shadcn.
Excellent episode (as usual). I love the camera angles; it really makes it feel like I’m just peeking into your conversation.
Also, +1 on that Coolify episode. Got me! Look ma, I’m self-hosting now!
Wanted to echo Scott's suggestion. I started building out my own common component library for personal projects and it's been great for improving my ability to make extensible and composable interfaces, and really thoroughly consider theming and responsive design upfront in my projects.
Btw, my new fave feature of the show is those joke intro cards for Scott and Wes. Whoever is writing those is cracking me up!
Great episode, didn't know about Svelte French Toast and it looks good!
Loved this episode. I'm building my personal starter project with my preferred stack right now and this felt super relevant. This is the second episode that you've put out that I've thought "Wow, I was just thinking about that". The last one was the React Native episode. Good stuff!
'patch-package' is a lifesaver to have bug fixes before they're released
Scott & Wes Thanks so much guys... God bless 🙏🏽
I think there was a point missed on the email link sign-in stuff. The thing that frustrates me about that and also email validation or reset password links is that the links always open a new browser window/tab. Now you have 2 (or more) tabs open to the same website which is unnecessary and possibly could be confusing if you don't remember which tab you were on.
I write all of these things myself every time but it's growing old. I've started a Storybook project for myself to catalog the things I've designed and developed that are "different" enough from each other that I can borrow from.
I think web component based core ui components (toasts, switches, etc) feels like the way to go. Really looking forward to web awesome.
Shoelace whips, Web Awesome will be awesome.
@@syntaxfm I discovered shoelace thanks to this comment just now! How am I this late to the party?!