I have been dabbling in the web recently out of necessity. A good approach for my case (my personal website
) was custom static site generation. This was done with just a simple C program
that parses my own text format that tries to be as close to a natural description of the static content as possible.
This approach has two notable benefits (among others):
I actually have the ability to separate the content from the web entirely, and can export directly to different formats, like BBCode or Markdown (any other format would just a different backend for the content transpiler).
I was also surprised to hear from Ben Visness and Asaf Gartner that there is quite a bit of interesting server-side
work that can be done in a handmade fashion. Some of the options that I heard about were CGI programs, where a webserver is configured to run an arbitrary command when it receives a particular HTTP request, then the command is expected to produce HTTP output in stdout (this command could be, for example, your own C program), and additionally the concept of a custom reverse-proxy HTTP server (which only communicates with the main outward-facing web server locally server-side, so there isn't the concern of security), which seems like it could be up and running in a relatively short amount of time.