CoursesAI WorkshopCompaniesPricingBlogNewsletter
  • Courses
  • AI Workshop
  • Companies
  • Pricing
  • Blog
  • Newsletter
Subscribe

Subscribe to our newsletter

Don't miss the news that are truly worth it:

By subscribing you agree to the privacy policy
  • Courses
  • Companies
  • Communities
  • Blog
  • Gift card
  • Newsletter
  • Help
  • Shop
  • ConfAiBot
  • Contact
  • Legal notice
  • General conditions
  • Privacy policy
  • Cookies policy
Does CSS Architecture make sense with Tailwind?

Does CSS Architecture make sense with Tailwind?

15 January 2026

Subscribe to our newsletter

Don't miss the news that are truly worth it:

By subscribing you agree to the privacy policy

Hey there!

Summary of this email:

  • Does it make sense to apply CSS Architecture with Tailwind? (+ course published on Codely Pro)
  • Last chance to sign up for next week's Workshop

⏱️ Estimated reading time: 1 quick minute.


🤔 Does it make sense to apply CSS Architecture with Tailwind?

Before Tailwind came along, one of the typical questions was how to organize our CSS so it would be maintainable.

The CSS Zen Garden website was created as a response to using CSS when and how it was needed.

From there, little by little, standards emerged to better scale CSS code like BEM or Atomic CSS, but at the same time, a movement arose that didn't like these kinds of architectures at all.

After going through the era of complex frameworks like Bootstrap or Material Design, which were fast to prototype with but slow to customize, Tailwind came along. You could do everything with utility classes.

The best part is that at a time when React and Vue were gaining traction and we were going from having one mega HTML to splitting it into components, utility classes made even more sense.

But here's where the problem comes in. We start adding those utility classes, everything stays pretty simple... until we start to:

  • 🎨 Add dark theme
  • 📱 Support responsive
  • 💫 Add animations
  • ✨ Think about accessibility

Suddenly, with Tailwind, we need a 100" monitor just to see all the utility classes we've added.

This (and not before) is the moment where introducing architecture concepts can help our styles scale much better. Just by introducing BEM, we recover a lot of readability.

And the best part is that you can do it with Tailwind, getting the best of both worlds: The Tailwind ecosystem and the scalability of BEM.

This goes against the opinion of Tailwind's creator, Adam Wathan, who recommends not giving semantics to classes.

Even so, in the situations we mentioned earlier, we believe it makes a ton of sense. Plus, this way we decouple ourselves quite a bit from Tailwind in case a better framework comes along in the future.

A while ago, at a conference, we ran into Paco Castelló, Tech Lead Front End Developer at S2 Grupo.

Chatting with him about frontend, we really liked how they were applying all these concepts in production. So much so, that we recorded a course with him covering all of it. Tailwind CSS: Architecture and Best Practices. Now available for Codely Pro Premium. 😊


🚨 Last chance to sign up for next week's Workshop

Next Tuesday we'll be holding the 6th edition of the AI for Programming Workshop. It will be the last public edition we'll run, at least for a while.

So this might be your last chance to attend.

In the workshop we cover how to code better using AI and lots of up-to-date tips on how to use it. One of the most interesting new features is the Tool Search Tool launched in Claude Code, which will significantly lighten the context if you use MCPs. 🙌

You can buy your spot right here. 😊


And since you've made it to this part of the newsletter, here's the joke of the week, which I know you were waiting for:

> Why is Redis the most respected database? Because it has so much cache! 😂 😂 😂

Cheers!

SubscribeSign in