queen.raae.codes · a developer’s logbook
← The log
1 min read

finally started styling our site with Tailwind

Originally sent as a newsletter.

Written in 2021, 5 years ago. Tools and advice may have moved on since.

Hello there,

Yesterday’s unauthorized and rum-fueled treasure hunts in the sharky waters around the Gatsby islands tiny-task was style one component.

It was time for our nattermob.dev to look like it belongs in the 21st century. Paul suggested we reach for Tailwind. Since I knew Ineza has worked on Tailwind we asked him to join as well.

Screenshot of the show!

Personally I have either gone with MaterialUI for the utility web apps I’ve made, or just hand yolo’d my own css 🤪

I was pleasantly surprised!

It didn’t feel as wrong as I thought it would… We followed the Gatsby Tailwind docs and went from there.

The biggest benefit I see is how lovely the default styling is. Often you are not looking to make something special, you are just looking to make something good enough.

Another benefit, especially for those with no design chops, are all the great examples. Especially if you pony up for the paid version of their component playground.

Not so interesting for us Gatsby folks, but since Tailwind is not dependent on Javascript you may use the same solutions for styling for projects on all stacks.

Screenshot of tweet from @dan_abramov (React core team) on Tailwind.

Interesting thread/discussion on Tailwind by Rect Team Member Dan Abramov.

All the best,
Queen Raae

PS. The code can be found on github and we are not done styling! Grab an issue/component and style with us (after we document how to get the keys you need or find a work around) 👩‍🎨🧑🏽‍🎨👨🏻‍🎨

PPS: The website style I mentioned was popular a fairly recently was “Brutalist”, check out this showcase.

Join the crew!

All the shenanigans from me and my piratical family, straight to your inbox.

Search the log

↑↓ to move · Enter to open · Esc to close All entries →