I like static sites for personal technical work because the structure stays visible. HTML, CSS, a little JavaScript, JSON indexes, assets, and routes.

That does not make static sites inherently better. It just fits this case. A small technical site with projects, notes, CV, and contact routes does not need a larger stack before the content itself has grown enough to justify it.

The useful part is that edits stay close to the files. A route changes. A paragraph changes. A JSON entry changes. The repository keeps the history, and the page remains simple enough to inspect without starting another project around the project.

This also makes writing harder to hide. If the copy is weak, the site has nowhere to bury it. If a project page is vague, the structure will not rescue it.

The current site should stay small until the work itself demands more structure.