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!

Thanks! I completely agree.

I'm planning to add more detailed pages for each color too. things like gradients, complementary colors and UI examples so keep an eye out!

thanks! and that's a cool idea — I like the localstorage idea, plus I'm thinking adding some hotkeys could help too (so pressing h would switch to hex mode).

I'll take a look in the next few days!

Yeah it's a cool move by Cloudflare to make those templates so obvious (makes sense though given how often people must ask for this!).

Yeah there are definitely a few ways to go about this — adding a rule to your .htaccess has been a go-to for a looong time now!

I'm hacking away on something I've built recently to improve the native "Publish to Web" feature from Google Docs.

Essentially I'm grabbing the document's content and re-rendering it with a full-page background colour and better mobile support.

Link: https://voltdocs.com

Enjoy!

hey nah I don't (it's a very new blog!). In the future though I'm considering purchasing and writing reviews of specific "dumb phones" like the Nokia 6300 4g. There's an affiliate marketing angle there, and I'm also considering creating Youtube review videos too.

Hey I'm the author. I definitely didn't mean to imply you should remove critical system apps (I don't think that's possible on vanilla iOS). More just that it's worth deleting most apps beyond the basics like calls,text,calendar,maps etc

Thanks for posting OP! (I'm the template author)

I've used Middleman for years to build my personal site(https://harrisonbroadbent.com) and other blogs(https://dumbph.com). I figured it was time I give back to the community; I hope a few of you find this template useful!

Middleman's heyday has long passed, but the tech is still solid and stable. I'm 7+ years into running my personal site with it, and I'm hoping that by modernising it with TailwindCSS, I can keep it chugging along for many more years.

HN has a pretty negative view of Ruby/Rails overall, but I wouldn't let that deter you. Every language/framework has its downsides; If you're enjoying Ruby/Rails then I'd say keep going!

It's brilliant for side-projects and smaller teams; At 50+ devs working in the same Rails codebase, it can start to get pretty chaotic which is potentially where a lot of the HN-negativity comes from.

Sure - https://marketplace.visualstudio.com/items?itemName=elia.erb...

Author here, thanks for sharing!

I'm really excited for where some of the extensions in the article are going - the RubyLSP has been improving slowly and steadily and I'm hoping that this is the year it gets _really good_. Other extensions like the StimulusLSP are niche, but awesome, and on the Twitter thread for this article (https://twitter.com/hrrsnbbnt/status/1759900961760477681) someone even pointed me to a new ERB formatter that looks promising.

TLDR; Rails is alive and well! Ruby has never been a first-class citizen of VS Code, but there's still some awesome extensions out there to give you a decent experience. And it's getting better!

Here's the GitHub milestone I've based this article on — https://github.com/rails/rails/milestone/87

hey HN! I use the mailer previews built into Ruby on Rails extensively, but they're pretty lacking (learn more: https://guides.rubyonrails.org/action_mailer_basics.html#pre...).

I've had the idea for a better version in my head for a while, and over the weekend I found the time to throw it together! The advantage of this gem/engine is that you can live preview your mailers on the index route, test their responsiveness easily, and forward them on to another email.

Let me know what you think! The GitHub README has a bunch more info + a handy GIF, and I've also tweeted about it (https://twitter.com/hrrsnbbnt/status/1731588511533519188) if that's more your thing.

Thanks! -harrison