Why I Still Start With Raw HTML Before Any Framework

It’s 2025. You’ve got tools like Tailwind, Bootstrap, React — entire ecosystems built to help you move fast. So why do I still open a blank .html file and start from scratch?

Because every great building starts with a blueprint — and HTML is mine. Before I think about color, layout, or interactivity, I build the bones. The foundation. The raw markup that gives every pixel a purpose.

HTML Is Not Outdated — It’s the Bedrock

No matter what toolchain you use — React, Vue, Astro, or Liquid — it all compiles down to HTML. If your structure is wrong, the rest of your stack is sitting on sand. When I teach junior developers, this is the first lesson: understand your structure before you style it.

I treat HTML like an architect treats blueprints:

  • <header> — for navigation and identity
  • <main> — for the story you’re telling
  • <section> and <article> — to chunk ideas and flow
  • <footer> — for attribution, next steps, and wrap-up

Everything else — classes, styles, scripts — comes after. And when the HTML is clear, those things get easier to manage, not harder.

The Benefits of Starting With HTML

1. It Exposes Bad Ideas Early
If your layout doesn’t make sense in plain markup, no amount of CSS magic or JavaScript wizardry will fix it. Writing HTML first forces clarity.

2. It Boosts Accessibility by Default
Screen readers, keyboard navigation, and assistive tech all rely on semantic HTML. A <nav> means something. So does <main>. So does heading hierarchy. Good HTML speaks for itself, even without styles.

3. It Helps You Scale Smarter
Solid markup becomes reusable components. It adapts to CMS templates. It works across teams. You don’t waste time debugging class soup or rethinking layouts that were never sound to begin with.

Frameworks Don’t Replace Thinking

I love Tailwind. I use it often. But even with all its convenience, it doesn’t tell me why a section exists, what’s important, or how content flows.

HTML does. And when I write markup before utility classes, I can answer critical questions:

  • What’s the actual purpose of this content?
  • Does the hierarchy make sense?
  • Can a screen reader follow the story?
  • Would I understand this without styles?

Tools don’t erase the need for clarity. They multiply the impact of whatever structure you start with — good or bad.

For Recruiters, PMs, and Collaborators

If you’re hiring a web developer or reviewing a build, ask how they approached their HTML. Did they structure it with care? Or is it div soup covered in CSS Band-Aids?

Clean HTML prevents 80% of what usually goes wrong: broken layouts, poor SEO, accessibility complaints, and wasted hours in QA. A solid foundation saves money and time — and protects your brand across devices and updates.

How I Work in Real Life

Here’s my process:

  • I start in a blank browser tab. Just HTML. No classes. No assumptions.
  • I navigate using a keyboard and a screen reader emulator.
  • I test content hierarchy before color or spacing enters the conversation.
  • I ask: can this document stand on its own without CSS?

Only when the answer is yes do I reach for frameworks, animations, or advanced layout patterns. Because by then, the structure is solid. The house is ready for furniture.

This Is Not Nostalgia — It’s Strategy

HTML is light. It’s fast. It’s evergreen. Every framework builds on top of it, but none of them replace it. If you respect the structure, everything else becomes easier to debug, extend, and scale.

So no, I’m not being old-school. I’m being smart. HTML is my foundation because everything that comes next relies on it.

Want to build something stable, scalable, and sane? Contact me here and let’s start it the right way — from the roots up.