Shiny Object Syndrome?
drodol • 6 Dec 2023 •
So I don’t know why, but for the past two days, I’ve felt like I have really started to understand CSS.
Don’t get me wrong. I am talking about understanding it at the most basic level.
There is still a bunch that I don’t know.
But I feel like I understand enough to be dangerous.
It was almost as if I started literally seeing things “click” together in my head.
I fixed tiny CSS annoyances on the “dev” version of DfE today -the one live at dfe.fly.dev
BUT, yesterday (and the day before yesterday) I came across a couple TailwindCSS tutorials, which I watched.
I started watching them but not really. They were playing in the background, and while I was paying attention, it felt like when we had FM radios and music was playing in the background, kinda.
The point is that TailwindCSS then started to make a lot of sense. And while I am torn between many ideas now, like separation of concerns, that I don’t like messy classes in my html, or that using it requires an extra build and tooling I don’t need, I have this pull to just build with it (or maybe rebuild DFe with TailwindCSS!)
I just think that with my knowledge of CSS basics, building something with TailwindCSS + DaisyUI or something like Flowbite would be super fast (and look really nice).
Here are the two tutorials I watched:
-This one by the mythical and really good teacher, Net Ninja:
Tailwind CSS Tutorial
-and this short one by another good guy, Traversi Media:
Tailwind Crash Course | Project From Scratch
Should I stick to vanilla css or should I maybe just try to rebuild a tiny bit of DfE with TailwindCSS?
Comments
I am also not a fan of those, but I’ve also come to understand that it’s not as complicated and frequent as I thought. In fact, it is just in the initial installation. Almost like a set it and forget it deal.
I have actually started playing with the CDN in Codepen and built the header and the card layout. It was a good experience.
That mix you talk about is also good!
Yeah the find CDN approach so underrated. It sacrifices performance a bit but I love how easy it is to try things on a small scale, slowly move things over if I want.
I assume that TailwindCSS would be quite large to be used via the CDN in production, but for testing purposes, the CDN approach is just fine.
Not a fan of extra build steps and tooling for those too! But to rebuild a small part, how about trying the CDN version of tailwind perhaps? A mix of vanilla CSS and Tailwind?