Doing this as a consumer and doing this as a webmaster are different processes. As a webmaster, if it's at all possible to go static (whatever your flavor of t

Doing this as a consumer and doing this as a webmaster are different processes. As a webmaster, if it's at all possible to go static (whatever your flavor of that is), then do that. A static website is easy to host and keep forever, and it's usually easy for consumers to archive too. Not to hate on PHP, but keeping older PHP sites around securely has become a major undertaking. You can't safely run a wordpress site that hasn't been updated in 5 years because your security vulnerabilities are exposed to the wide web. If your static site generator has security flaws.. well that doesn't affect your current build artifacts and you can still run the thing in secure ways.