Pavel

Thanks @damianricobelli @guilherme_rodz and its-monotype for your contributions. More soon: multi-select, file upload...and more 👀 github.com/shadcn-ui/ui

We've added two new components: the most-requested breadcrumb and a new Input OTP.

@webdevcody I don't, it requires me to check my email, when with password manager I can just auto fill

Do people actually like magic link email login?

code

With ping animation

Notification Bell using @getReshaped and @Pikaicon

@tryamie Ahh, I see! I'm so hyped, it's a pleasure to use the app, the design and everything look incredible.

@itsmonotype web has virtually all the same features as desktop. we’d love to be in android and windows in the future :)

your calendar is your personal philosophy… hear our vision for today and tomorrow:

@blvdmitry @tryamie The most impressive website I've seen, amazing work

I've been helping @tryamie launching their new website and it all started for me with this small clock widget 😅 I had no idea what a ride it will be 👀

@blvdmitry Such a common experience of working on side projects: starting with great enthusiasm and confidence of quick success, and then being faced with the reality 😁

Me picking a side gig: LFG, ready to ship tomorrow 🚀 Me two days later: What am I doing? Gonna add a few tailwind classes here and I'm sure it's going to work 😅

@rauchg Nice, found some exciting tools from "Stack" 😀

So sleek and fast (onur.dev)

@nicks_twt each for a different use case 😉😏

There are only 2 types of designers these days. Which type are you? 👀

@richardhendrix_ @webdevcody Totally agree, unnecessary abstractions can make hell in the codebase, I prefer sticking as close to docs and examples they provide as possible.

@webdevcody Abstraction is what causes errors like this. The best way to mitigate weird errors is to work as closely to the standard library of the language ur using. The further away you get, the weirder the errors. I’m just a noob anyway, what the hell do I know

the more I encounter errors like this in next / react, the closer I get to using HTMX and Go

@ticktick Looks nice 👍

Check your TickTick Year in Review 2023🎉

@blvdmitry @adispezio Agree, rating should have its own color, caution isn't suitable. It's unclear how to offer this with a custom color out of the box, making it more fitting for product-level implementation, usually for e-commerce sites reviews. But still having it built-in would be great. 🤔

@adispezio I'm with you on that to be honest. That's also why I still haven't built a rating component in Reshaped and having an ability to add custom colors to the theme definition keeps me thinking that it should be implemented on the product for that reason

Round two, how would you call a token in between critical and positive?

@Idered @adamwathan nice work

@adamwathan You can try chalk.ist for a little prettier code snapshots. I've added Tailwind CSS theme and it support multiple blocks if needed🙂

Do we all agree that this span should be green when you directly hover the span, not red? I'd like to make some b̶r̶e̶a̶k̶i̶n̶g̶ c̶h̶a̶n̶g̶e̶s̶ bug fixes.

@blvdmitry Here is an example, idk is this better than entering year using keyboard to input or using select but feels native for calendar flowbite.com/docs/plugins/d…

@itsmonotype Right now it's based date or month selection only, with arrow controls for the year. However happy to support it if you want to use calendar for cases like age selection

Reshaped v2.7 is out 🪄 reshaped.so/content/change… Calendar was one of our backlog requests for a long time and it's finally here, supporting full keyboard navigation, localization, separate month selection and much more 🥹 Check how it was built in the thread below

@blvdmitry dyk about react-email ?

Tried it out for the first time myself. Built a responsive marketing email in React that works across all email clients. Took me 30 minutes 🤯

Probably the most unique UI project I've been working on at work recently was our email component library revamp. Very different output requirements 👀 1. Always rendered in node, so it feels like you're working with RSC and don't have to worry much about the js performance. Instead you need an optimal HTML output. 2. We needed out components to be responsive on mobile clients, which means you write inline styles for desktop and style tag on mobile. We've built a utility that automatically resolves all of it and only adds mobile styles for components rendered on the screen that are responsive, doing that in the node runtime 3. Supporting all email clients make you feeling walking on a mine field. You already have to be very creative with API for layout components, but just one client not supporting some html/css edge case - makes you rethink the whole approach again

@pagebakers Or even would be better to showcase your components in some fancy way like may composition of them and make them interactive right in the hero block

@pagebakers Bad image on the right side may try another mockup. Typography is nice 👍

Playing with a new landingspage design idea. Yea or nay?