The website that didn't need a framework
A website can be simple without being simplistic. If all it needs to do is present information, answer a few questions, and give someone a way to get in touch, adding an application framework can create more work than value.
Start with what the website actually does
A typical marketing website might have a handful of pages, some images, a navigation menu, and a contact form. There may be no accounts, no dashboard, no data fetching in the browser, and no meaningful application state.
That is not a problem waiting for a framework. It is a website. HTML is already very good at being a website.
Less code can be a feature
A static site can ship almost everything the browser needs as plain HTML and CSS. There is no client-side runtime to download before the page can become useful, and no large dependency tree to maintain just to render a heading and a paragraph.
That usually means faster pages, fewer things that can break, and a much smaller surface area to maintain.
Frameworks still have their place
This is not an argument against frameworks. Once a project needs authentication, complex interactions, real-time data, dashboards, or substantial application state, the equation changes quickly.
The useful question is not 'Which framework should we use?' It is 'What does this project actually need?' Sometimes the answer is a framework. Sometimes it is a few HTML files and a stylesheet.
Need this done on your project?
We build static sites, web applications, and WordPress — and we are happy to talk through the tradeoffs before you commit to anything.