If Markdown formatting is enough for you, I would look into using a static site generator, like Hugo or Jekyll.
If you want to keep your existing content as static files but same website skeleton and layout instead of copying and editing files you'll copy one and create the layout template. Then content and new posts and pages can be generated from Markdown files. If you set up CI they won't need to run Hugo or what you're using, only push the Markdown files to your Git repository.
Whatever you want to do primarily depends on: Your formatting, styling, functionality, and interfacing needs for the editor, and what you're willing to use or invest for setup.
Hugo runs from a single binary. The source layout is reasonable. With a single layout the folder structure doesn't have to be complex.
I'm not very familiar with alternative [Markdown] static site generators.
I found it hard to follow despite C# being my main driver.
Using
ref, in the past, has been about modifiable variable references.All these introductions, even when following C# changes across recent versions, were never something I actively used, apart from the occasional adding ref to structs so they can contain existing ref struct types. It never seems necessary.
Even without ref you use reference and struct types, where reference content can be modified elsewhere. And
IDisposablefor object lifetimes with cleanup.