Most sites do not need a framework. Semantic markup, a few styles, and a working contact link already get you further than another build step.

The default stack for a new site now includes a bundler, a component model, and a hydration story. That is a lot of machinery for a page that explains who you are and how to reach you. HTML already does that. It has headings, paragraphs, links, and forms. Browsers have been excellent at those for a long time.

Start with the document

Write the page as if CSS and JavaScript might fail. Use a real h1. Put the logo in an img with an alt. Wrap posts in article. Give the contact action an actual destination, even if you dress it up later.

When the markup is honest, the rest of the work gets smaller. You style what is there instead of inventing structure in a render function.

Frameworks are a choice, not a baseline

A framework is the right tool for an app with shared state, auth, and a dashboard that never sits still. A brochure site that changes twice a year is not an app. Shipping it as one means you now maintain a build, a lockfile, and a major-version calendar for a few paragraphs of copy.

VanillaHTML is the bet that you can publish without that overhead. Open a file, change the words, reload. If you outgrow that, you will know — the site will tell you. Until then, HTML is enough.