Problematic design. It's a static page, and should be served as such; a Raspberry Pi could probably handle that, and it's easy to put behind Cloudflare or similar.

i am not the poster, but i am in a similar situation with my own blog.

just because my blog could be hosted on a static page, i am not going to go through the effort to set up a separate server just for that when i am already hosting a website with dynamic content and my goal is to host my blog with a minimum of effort on the same site. and i am especially not going to buy a raspberry pi just for that. and if i put it behind cloudflare i am just going to annoy the other half of hackernews readers asking why everything has to be behind cloudflare.

I'm not suggesting a separate server or a Raspberry Pi (that was just an example of the low resource needs), just having non-dynamic pages to not be hitting the database, so be cached somewhere (hopefully automatically), or using a server configured to serve them statically.

the platform i use stores everything in a database. it doesn't even support reading static files from disk. and why should that even matter. the filesystem is just a different kind of database. as for purely static pages, i happen to have a small website that is purely static too, served from the same platform. and already maintaining the navigation for a few pages is a pain. i could use a static site generator, but then i'd have to use different tools from the rest of the site. and that also increases the maintenance effort and adds dependency on yet another tool. my current plan is to keep the pages static but use js to create the navigation. that would add the cost of a REST API call to get the list of pages and affect the cacheability for the navigation part. if only html had an <include> tag then maintaining the navigation would be a lot easier without js.