hbroadbent

Tailwind CSS v4.2 has just been released, including:

- 4 new colors! (mauve, olive, taupe, mist).

- new webpack plugin

- new padding/margin/border-block utilities

- various tweaks and performance improvements

I've just updated my color palette website, https://tailcolors.com, to include the new colors, including custom pages to view each new color in the context of a mock UI, gradients etc.

Example of the new Olive color: https://tailcolors.com/olive

I've still working on

https://attendlist.com

It's a Google Meet attendance & chat tracker, and it's starting to pick up a bit. A few teachers & other people are using it and enjoying it which is really awesome!

Thanks, and cheers for the tip!

Thanks!

Honestly, if you've found something that works for you, I'd stick with it.

Once (if) you start scaling one of your apps, that's when I'd loop back to thinking about infra: either yeah considering something semi-managed like Hatchbox, or even fully managed like DO.

(Hatchbox does actually integrate with managed database instances like those from DigitalOcean which is pretty cool imo)

Hey HN, I've been playing around with HTML & CSS only tooltips for a while, and I finally decided to write a bit about them. Hopefully someone here will find them interesting!

At the end of the article, I also touch on the new CSS anchor API, which will simplify things a bit once (if) it becomes more widely supported.

I'm still building AttendList, a Google Meet attendance tracking extension (https://attendlist.com).

It's starting to pick up! Which is cool — a few new users are trickling in each week. I think it's about time I invest more time in marketing now though (which is probably what I should be doing now instead of posting on HN!)

I'm currently building AttendList — https://attendlist.com — an attendance tracker for google meet.

Hey! Actually that is possible using the <datalist> element.

If you're interested, I wrote a bit more about it here: https://harrisonbroadbent.com/blog/cool-native-html-elements...

Sure it's not the prettiest, but even if you styled this with CSS directly you'd need to target those selectors. `#range-input::webkit-progress-bar` etc.

To your final point, I completely agree that it should be packaged up — I'd package this up into a component (react, partial etc.) which would encapsulate the styles via Tailwind, HTML and logic.

I like Tailwind as a way to more closely tie my markup with styling. I'll package it all up into a component anyway, but Tailwind keeps it all in 1 spot (the markup) rather than spread across multiple files.

Oh cheers, I had no idea. I'll fix it, thank you

Hah fair enough! I've actually just stumbled on the Popover hint demo (https://mdn.github.io/dom-examples/popover-api/popover-hint/) which uses the Popover API to create native HTML tooltips. I'm planning to update my article with them once I've played around a bit more

Stoked to see a few hundred people have already read this article (and one person's already suggested an improvement!).

What other elements should I add?

I've been building Tailcolors lately, a TailwindCSS color palette: https://tailcolors.com

Just recently actually I published a Chrome extension for it too, so you can access and copy all the Tailwind CSS colors directly from an extension: https://chromewebstore.google.com/detail/tailcolors-tailwind...

Hey HN, just sharing the way I've been adding Tailwind CSS to my Chrome Extensions lately.

tldr is that it's dead easy to save the CDN script locally and use it, plus it doesn't come with the typical drawbacks that websites face (ie: loading external resources).

I've also built https://tailcolors.com which you might also like!