Joost

@flaviocopes ddev

is there a macOS for local development so I start `npm run dev` in a directory and it's always running mysite.local, not localhost:<PORT>, and if an npm run dev process is already running in that directory it tells me?

@tobimori Halbe Buch

square buttons are back baby!

@fractaledmind @adamwathan And you will most likely use other utilities then css props that tailwind has no utility for. I wanted to avoid mixing both but I guess that’s unavoidable at some point and with using apply this point is more far away.

@fractaledmind @adamwathan Yeah I tried the approach yesterday, and I guess your right. For example when writing normal css props with the tailwind vars you have to learn some new tokens, like for rounded-* the css var is —radius-*.

Building HTML UI forced me to figure out how to write CSS classes that integrate deeply with Tailwind v4. I want 3 things: intellisense, tree shaking, and easy utility overrides. Here’s I make it all work 🧵

@fractaledmind I guess there is also still @adamwathan in my head saying don’t use apply 😅 utility and where are nobrainers for sure!

@fractaledmind Im not quite sold on the apply and variant syntax. I guess sooner or later there will end up a mix with normal css properties in the style block. With v4 we could simply use the css variables (isn’t there also a spacing fn). I guess I would go with variants but without apply.

Ever wondered wich years the songs in your playlist are from? I did so i went back to the tool i built some time ago spotify.joostramke.com

@calebporzio Sick! But it’s annoying that hover states still break during transitions

Absolutely insane how powerful the web's ViewTransition api has gotten 😮‍💨 Dropping with the full Livewire 4 release next week 🫡

@pascalbaljet Did you take a look at @zag_js?

I'm 🤏 this close to building an open-source vanilla JS library for popovers, dropdowns, tooltips, click outside, focus trap, and other utilities. Would give me full control and avoid third-party libs with inconsistent behavior across adapters.

@colmtuite @tannerlinsley That’s right, I only had a few blog articles about scrollbar accessibility in mind that are very against custom scrollbars, which is why I’ve always been cautious on the topic

@jstrmk_ @tannerlinsley Native OSX scrollbars don't even come close to 24px (SC 2.5.8 Target Size)

I've been listening to feedback on docs readability and design. Shipped a bunch of updates today: Docs Layout - New collapsible sidebar with visual minimap showing where you are in the docs - Cleaner content area - removed the translucent backgrounds that were hurting contrast - Breadcrumb navigation so you always know what section you're in - Better responsive behavior on tablets/medium screens Table of Contents - Redesigned with a clear left-border indicator for the active heading - Uses library brand colors so it feels cohesive - Smooth scroll behavior when clicking headings Typography & Contrast - Switched to neutral grays (removed the blue tint) - 99% white in light mode, 96% black in dark mode for better contrast - Reduced shadow intensity across the board - content should feel grounded, not floating New Features - "Copy page" dropdown - copy as markdown, open in Claude, open in ChatGPT General Polish - Softer shadows throughout (less "chunky") - Removed hover lift effects on cards - Cleaner navbar with better button styling - Partners sidebar reorganized Still iterating. If something feels off, let me know. The goal is clarity and calm - docs should get out of the way and let you learn.

@colmtuite @tannerlinsley Im curious if a thinner scrollbar doesn’t violate accessibility?

@tannerlinsley - Put code snippets in <code> tags, and use a monospace font. - Use a white background for code tags, so it's less gray on gray on gray. - Use a custom scrollarea (Base UI 😃) for the left sidebar. Or at least apply CSS to make it thin and subtle. - Left sidebar needs to be wider

@fractaledmind @CameronPak Im sold

@CameronPak If you like Daisy UI, I think you will like what I've got cooking. Think Daisy with aesthetics like Linear or Tailwind's Catalyst React components 👀

When you simply need to have a link look like a button, pretty pretty please do this instead 🙏

@fractaledmind @sub_popular Yeah I really like this approach, thrilled to dig more into this when I’m able to. It seems like a perfect balance between these fronts. I think its pretty hard to express this in words

@jstrmk_ @sub_popular Thanks. Still trying to find the best ways to articulate my thoughts to resonate with more people, but I *know* that this is beneficial. And more people and teams would benefit from expanding their thinking around utilities and a utility-first approach to building views

Your app/design system needs a .button class before it needs a <Button/> component. We need to be able to compose behaviors and appearance as needed. A <label> might need to look like a button, or <summary>, or <input type=radio> Visual affordances deserve their own primitive.

@fractaledmind @sub_popular That’s a great read 🤝

@sub_popular I talk more about this concept of affordance classes here: fractaledmind.com/2025/12/01/ui-…

@pqoqubbw @shadcn I guess vidstack is no longer the focus, they are giving v10.videojs.org a rebirth

@shadcn video player component would be awesome maybe something on top of vidstack.io

What would you like to see in shadcn/ui next year?

born to design in code forced to draw components in figma

@dmytro_kondakov @JohnPhamous @claudiucjc Maybe update the meta tags color with a little js based on scroll

@JohnPhamous @claudiucjc i don't think that works, at least based of my experience did you ever try this successfully?

set html/body background color to match website color so overscroll area blends in

@justin_schueler @tribehousespace @framer Cool :) but I think the text animation is a little too long, you yourself just scrolled past and couldn’t wait for it to finish. Other people scanning the website will likely do the same

website update @tribehousespace tribehouse.space @framer 🫶

@alex_krasikau @moeamaya @joebell_ Obviously your are involved there 🫡

˗ˏˋ operate ˎˊ˗ is live! I can't express how grateful I am to work with @moeamaya, Daniela, and the Operate team to deliver the new Operate website Big shoutout to @joebell_ for always having my back 👊

@joebell_ I think this could break back/forth navigation on trackpad if added on both axis and not only y. But maybe I mix up something here

If your app contains multiple scroll containers, consider adding `overscroll-behavior: none` to your html/body to prevent "page bounce" before → after