This site took about an hour to build. No framework, no build system, no week-long deliberation about which static site generator to use. Just HTML, CSS, and agit push.
I've watched engineers (myself included) spend more time choosing tools than building the thing the tools are supposed to help build. There's always a better framework, a cleaner architecture, a more scalable solution. And there's always a reason to wait until you've figured out the "right" approach.
The problem is that the right approach usually reveals itselfafteryou've built something wrong. You can't architect your way to understanding. You have to build, see what breaks, and fix it.
This site will probably get rebuilt at some point. Maybe I'll want a proper blog engine when I have fifty posts. Maybe the CSS will get unwieldy. Maybe I'll regret not using a templating system. That's fine. I'll fix it when it's actually a problem, not when it's a hypothetical one.
The best code you'll write tomorrow is worse than the okay code you ship today. Because the code you ship today teaches you what you actually need. The code you plan to write tomorrow is just guessing.
Ship it. Learn. Ship again.