Well, it's "relatively simple", as the alternatives either demand a superset of the requirements of static sites or replacements that are more complex.

Once you have the main mental model, you realize that git (the main/core features, not fancy stuff like submodules or worktrees etc) is basically the simplest thing that is fit for purpose.

Version control can be very simple. Not everything requires the full power of git.

Use ci from RCS, and that's about it. It makes a single file in the same directly as the file, no need to checkout files, or keep track of, well, anything. Just check in new versions as you make them.

It's not the right answer in many cases (especially if you need multiple files), but for a single file? The simplicity can't be beat.

Keep it simple, standard,