Skip to content

Learning Frontend in the AI Era: Why Bother When AI Can Build a Website in 5 Minutes?

By 5 min read

AI can build a website in five minutes, but the result is often almost right and hard to fix if you don't know the basics. Here's why learning frontend still matters, plus a series map that goes straight to Tailwind CSS.

id
Learning frontend web dev in era of AI

Learning frontend in the AI era still matters, and if you ask me, it matters more than ever. AI can build you a web page in minutes, but the person who can check it, fix it, and steer it is still the one who understands HTML and CSS.

In the Stack Overflow Developer Survey 2026, 48% of respondents said they only trust AI when they can easily check the answer themselves.

This happens all the time.

Someone asks AI to build a website, and five minutes later the page is done and looks great.

Then they want to change the color of one button, and suddenly the navbar is hidden on mobile.

They ask the AI again, the navbar gets fixed, and now the footer is the one that moved.

That's what got me thinking about this series.

Why is building websites with AI so tempting?

Because it's fast. Type one sentence like "build me a landing page for a coffee shop", and a few seconds later you have a full page with buttons, images, and testimonials.

If you've never written code before, it feels like magic.

Even for me, someone who's been coding for a while, it's the same.

Tempting.

I use AI almost every day at work. You could call me AI native.

But this series isn't asking you to drop AI. It's actually the opposite: so you can use AI with more confidence, because you understand what it writes.

The problem only shows up after the page is done

file 00000000ae4c821199714d3f6374b2c2
Hafidz nc

Here's the interesting part. Pages built by AI are rarely completely wrong. What usually happens is that they're almost right.

In the Stack Overflow 2025 survey results, 66% of developers said their biggest frustration is AI solutions that are "almost right, but not quite", and 45% said debugging AI-generated code takes them longer.

In frontend, "almost right" shows up in small but annoying ways. A button cut off on mobile, white text on a white background, a menu that opens but won't close.

If you don't understand the basics, there's only one way to fix it: ask the AI again and hope it works this time.

Sometimes it does. Sometimes a new problem pops up somewhere else.

The 2026 survey shows another interesting pattern. 67% of respondents use AI for code they're already familiar with, while for design, only 49% find AI useful.

In other words, the more you understand, the more useful AI becomes for you.

Agree?

Learning frontend doesn't have to follow the old-school order

The classic order goes something like this: learn HTML completely first, then plain CSS from selectors all the way to floats, and only later meet a framework.

Nothing wrong with that, it's just long.

A lot of people quit before they ever build something they can show off.

And frontend people love to show off their work. Show off anything, really.

Meanwhile in the industry, a lot of teams now write their UI with Tailwind CSS.

According to State of CSS 2025, Tailwind is the most used CSS framework: 2,041 out of 3,977 people who answered that question.

Way ahead of Bootstrap, used by 1,194 people.

So the idea behind this series is simple.

We learn straight away with the tools the industry actually uses, and pick up the CSS basics when we need them, instead of piling them all up front.

Pile too many basics at the start and you'll probably forget them. So we still practice the basics, just not all at once.

Tailwind is still CSS, not a shortcut

Tailwind is a set of small classes, each one representing a single CSS property.

So when you write Tailwind classes, you're actually writing CSS, just with shorter names.

Take this button:

HTML, XML
<button class="rounded-md bg-stone-900 px-4 py-2 text-white">Save</button>

Written in plain CSS, it looks roughly like this:

CSS
.button {
  border-radius: 0.375rem;
  background-color: var(--color-stone-900);
  padding-inline: 1rem;
  padding-block: 0.5rem;
  color: #fff;
}

px-4 is 1rem of padding left and right, py-2 is 0.5rem top and bottom, and so on. The full list is in the Tailwind utility class docs.

That said, some people prefer starting with plain CSS, and that's totally fine.

If you're the type who wants to understand things from the roots, that path is great too.

In this series I'll slip in the CSS version every time we hit a new concept, so you can still read the docs and debug on your own.

What's in the Learning Frontend in the AI Era series

The whole series works on one project: your own profile website, from a blank page all the way to being online at your own URL.

Each article adds one piece, and ends with a result you can open right away in your browser, plus a few small challenges to try yourself.

Hehe, challenge accepted?!

  1. Setting up HTML and Tailwind CSS, which gives you a profile website skeleton on your laptop.
  2. Box model, which gives you the profile section (photo, name, bio).
  3. Flexbox, which gives you the navbar and social links.
  4. Grid, for your collection of project cards.
  5. Responsive, of course, so the page feels good on mobile.
  6. The navbar the industry actually uses, which gives you a mobile menu that opens and closes.
  7. Typography, colors, and dark mode, which gives you your own visual identity.
  8. Forms and accessibility, which gives you a contact form.
  9. Deploy, which puts your profile website online.
  10. Polishing before you show it off, which gives you a final version for your CV.

Once you're comfortable, the usual next step is a framework like Next.js. I covered that in Learning Next.js 16, but that comes later.

Try it now, no install needed

Before we get into setup, you might want to get a feel for writing Tailwind in five minutes. Open Tailwind Play, clear the left panel, and paste this code:

HTML, XML
<div class="mx-auto mt-10 max-w-sm rounded-xl border border-stone-200 bg-white p-6">
  <p class="text-sm text-stone-500">Hi, I'm</p>
  <h1 class="mt-1 text-2xl font-bold">Your Name</h1>
  <p class="mt-3 text-stone-600">Learning frontend, and this time I actually get the code.</p>
  <a href="#" class="mt-5 inline-block rounded-md bg-stone-900 px-4 py-2 text-sm font-medium text-white hover:bg-stone-700">See projects</a>
</div>

Replace "Your Name" with your own name.

Then try changing bg-stone-900 to bg-sky-700, or p-6 to p-10, and watch what changes in the right panel.

That way you get a feel for it.

And congrats, you just wrote CSS without opening a single CSS file.

Oh, and AI will still be a useful work buddy.

The difference is, after this series you won't just be able to give it orders, you'll be able to check and fix its results yourself.

In the next part we move to your laptop: setting up HTML and Tailwind CSS from scratch, until your profile website skeleton is running. Thanks for reading.

Hafidz Nc

Fractional Head of Digital

Discussion