Apaxy VS perfectmotherfuckingwebsite

For Apache, there’s Apaxy: https://oupala.github.io/apaxy/ - a theme to make directory listings look nicer.

You could check out Apaxy.

What I need, is a web server handling static content, but with a GUI to fetch said content (for example, https://github.com/oupala/apaxy). It also need to handle PHP, NPM and ASP.NET projects... I'd also like to reuse my experience using these web servers in my job, or to add it to my resume as an extra skill.

You can do this with https://oupala.github.io/apaxy/

A couple of examples https://oupala.github.io/apaxy/ http://ramlmn.github.io/Apache-Directory-Listing/ https://github.com/Vestride/fancy-index

>However, the expectations for a statically generated site have drastically gotten higher over the years. Readers want (rich) content served fast

No, readers just want content served fast. Nothing beyond simple markdown or static html with some images or video embeds inside.

>Writers want dead simple (but expressive) writing and publishing. They want control over how their writing looks.

Who are those "writers"? If you're making a "static site as a service" perhaps that's a concern.

If you're making your own static site, you can use the simplest Markdown or whatever else you prefer, writing it manually, with or without a generator. You could even use the Motherfucking Website standard (https://motherfuckingwebsite.com/) or the Better Motherfucking Website RFC (http://bettermotherfuckingwebsite.com/) or the Best Motherfucking Website recommendations (https://thebestmotherfucking.website/) or go fancy and use the cutting edge Perfect Motherfucking Website ones (https://perfectmotherfuckingwebsite.com/).

Well in that case you may want to see this then this

⁠https://perfectmotherfuckingwebsite.com/