In partnership with

👋 Hi Devs,

Welcome to issue #65! 😅

Recently, I stumbled upon Tailwind CSS—and honestly,
my first thought was: “Great, another CSS framework on top of regular CSS.”

But while scrolling through Scrimba (my go-to platform for learning to code), I noticed they had a Tailwind CSS crash course that was only 2 hours long.

I told myself, “Let’s just give it 15 minutes.”

Fast forward—two hours later, not only had I completed the course and earn the certificate for that day,

but I was already recommending Tailwind CSS to every developer I knew.

This framework completely changed the way I think about styling in frontend development—faster, cleaner, and more intuitive than I expected.

OVERVIEW:

My recent three certifications that I did, planning to do more and sharing here

  • My first take on Tailwind CSS

  • How a 2-hour Scrimba course hooked me

  • Why I recommend Tailwind to devs

Prerequisites for learning Tailwind CSS:

I think these are must before starting out with the Tailwind

  1. Basic HTML (especially Classes and Ids)

  2. Basic CSS

  3. The below I think can be optional but required later

    1. Platform responsiveness

    2. NodeJS should be pre-installed

    3. Little knowledge about npm packages

My first take on Tailwind CSS

No separate styles CSS

The best thing that I liked about Tailwind is that you don’t have to make a separate styles file instead you can do all inside the HTML document

The reason it worked for me because I’m kind of person who likes everything inside one document and I can access everything through from there, Kind of like having one master file

Easy to learn

Tailwind is utility first framework that means It provides a vast collection of small, single-purpose utility classes (e.g., flex, pt-4, text-center, bg-blue-500) that can be combined to style elements. This eliminates the need to write custom CSS for every element or component.

The other thing is this that Tailwind is straight forward just like kind of python, I know that CSS is kind of straightforward too but the thing that bug me with the CSS is that you have to write custom CSS for every element

Here we too have to write but it is kind of straight forward,

EXAMPLE:

<p class="text-green-600">
Hello harman
</p>

In the above code I can directly write within the declared class of the html tag <p> that I want the “Hello harman“ to be green color

Easy right?

I believe Time is everything in software engineering and Tailwind CSS saves a lot of time.

This was one of the thing that I liked about Tailwind when starting out and building projects as your portfolio for the projects

Tailwind Documentation

One of the highlights for me was the Tailwind documentation. It’s super easy to read, well-structured, and packed with examples.

Through it, I quickly learned:

  • Styling with utility classes

  • Using hover, focus, and other states

  • Building responsive designs

Honestly, the docs alone make the learning curve way smoother.

FROM OUR PARTNERS:

The World’s Most Wearable AI

Limitless is your new superpower - an AI-powered pendant that captures and remembers every conversation, insight, and idea you encounter throughout your day.

Built for tech leaders who need clarity without the clutter, Limitless automatically transcribes and summarizes meetings, identifies speakers, and delivers actionable notes right to your fingertips. It’s securely encrypted, incredibly intuitive, and endlessly efficient.

Order now and reclaim your mental bandwidth today.

How a 2-hour Scrimba course hooked me

(First of all it is not SPONSORED by Scrimba)

I have to say—I love Scrimba because of its live, interactive video courses.

Why? Because before Scrimba, I was stuck in tutorial hell. You know the feeling—watching endless tutorials without actually building anything.

The great thing about Scrimba is that, just like all their other courses, this Tailwind CSS course jumps straight into the content. No fluff, just hands-on learning.

The course is split into two parts:

  1. Building a blog site with Tailwind CSS

  2. Practicing the concepts learned in the first part

Although it took me around 3.5 hours to finish (instead of the advertised 2 hours 😅), I found it to be an excellent way to learn Tailwind’s core concepts while actually building something useful.

Why I recommend Tailwind to devs

After using Tailwind CSS, I can confidently say it’s worth adding to your toolkit. Here’s why: (Quick bullet points)

  • Speed & Productivity → You spend less time writing custom CSS and more time actually building.

  • Utility-First Approach → Classes like flex, mt-4, or bg-blue-500 make styling quick and consistent.

  • No Context Switching → You style directly in your HTML, which keeps everything in one place.

  • Scales Well → From small projects to production apps, Tailwind helps keep your codebase clean and maintainable.

  • Great Docs & Community → The documentation is clear, and the dev community is super active with plugins, tips, and examples.

In short: Tailwind saves time, reduces frustration, and makes frontend development feel smooth.

I also started to complete the whole scrimba so i review that too

Want to be featured?

Send us email → [email protected] to get featured

How was today Issue?

Login or Subscribe to participate

If you like today’s issue, consider subscribing to us.

That’s a wrap! Catch you in next edition. 👋

—Harman

🔥 IN CASE YOU MISSED IT…

Reply

or to participate

Keep Reading

No posts found