I am rebuilding a small brochure site: home, services, about, contact and one FAQ page. There is a contact form, but otherwise almost everything is static.
My default at work is a component framework, so I started there out of habit. After an hour I realized I had a build step, routing and dependencies for a site that could probably be plain HTML, CSS and a tiny bit of JavaScript.
The main argument for keeping the framework is reuse between pages. The main argument against it is that this site may sit mostly untouched for years. For something this small, where do you personally stop adding tooling?
1 reply
I stop when the tooling starts feeling bigger than the site. Five pages and one form is very much in the “don’t overthink it” zone for me.
I stop when the tooling starts feeling bigger than the site. Five pages and one form is very much in the “don’t overthink it” zone for me.
Same. I’d maybe use a tiny bit of JS for the form, but not a whole framework just to repeat a header five times.
1 reply
For that kind of site, I’d skip the framework unless you already know you need it. Plain HTML and CSS are usually enough, and a contact form...
For that kind of site, I’d skip the framework unless you already know you need it. Plain HTML and CSS are usually enough, and a contact form can be handled without dragging in a full app setup.
I’d keep the build step only if it’s buying you something concrete. If all it does is add another thing to maintain, it’s kind of paying rent for no reason.