A static site turns a web request into a file lookup. That sounds modest, but it removes an entire class of runtime problems: database connection pools, application processes, migrations, and session state.
The trade is that content must be generated before it is served. For a personal blog or project notebook, that is usually an advantage. The build becomes a reproducible artifact, and the production server only needs to deliver files.
I like to keep the boundary visible. Source content lives in version control. The build output is generated in a clean directory. The web server points at the output, not at the source tree. A deployment is then a copy plus a service reload, and rollback means pointing the server at the previous directory.
Static delivery also works well with an edge cache. HTML can remain short-lived while images, stylesheets, and scripts use long cache lifetimes with fingerprinted filenames. Even without elaborate infrastructure, this gives a small site fast global delivery and a pleasantly small failure surface.
The important part is not the framework. It is the discipline of treating the generated site as an immutable release.