You can still just use HTML.
If you can get a modern text editor that can use SSH or something to mount a remote directory you can easily have an HTML party like it's 1999. That's easier than ever. But the surrounding issues are worse than they were in 1999, unfortunately.
The problem of warez is certainly no worse than it was 30 years ago, and there are much better tools to address it. A simple storage quota probably goes a long way.
It's simpler for us software engineers, less simple for the snot-nosed webmaster wannabes we were.
If all you want is to host static html, then any free hosting service will suffice. I.e. let them create a GitHub account and show them git add / git commit / git push and you're done.
It doesn't get much easier than signing up for e.g. Glitch.
Even the simple matter of port forwarding assumes you have access to the router you're using, and that's a major barrier for a lot of people.
I run the programming club at my high school (I'm a high schooler), and we use Github pages to host all of our stuff for this very reason.
I've used some old laptops to run servers within the network, but my school doesn't want us hosting anything public, and running everything through a free tunneling service like localtunnel is possible, but it scales so much better when students can just follow some friendly instructions to host a static site themselves.
It's not hard for the people with the privileges of (1) having a budget > $0 and (2) not having the adults tell you 'no' every time you want to try learn something.
Am I missing something? Even hosting static content on a server seems like a layer of complexity that is frequently unnecessary for basic use-cases.
You can do this in an hour with brand new coders. https://syllabus.codeyourfuture.io/fundamentals/week-1/sessi...