Do you need a build step at all?
For a site of a dozen pages, a folder of HTML files is a legitimate architecture.
Every few months I help move a small site off a toolchain that nobody on the team can update any more. The site has twelve pages. The dependency tree has nine hundred packages.
A build step earns its place when it removes real repetition: shared layout across hundreds of pages, content written by non-developers, assets that need hashing. Below that threshold it is mostly a liability with a lock file.
The alternative is not heroic. Plain HTML files, one stylesheet, a short script that stamps a header and footer onto each page. The whole generator for this site is a single file and runs in well under a second.
What you give up is convenience features such as hot reload and component libraries. What you get is a site that will still build in five years on whatever machine happens to be at hand.
My rule of thumb: if the build configuration is longer than the content it produces, something has gone wrong.