In practice most static websites aren't static because they include a bunch of stuff from elsewhere. But if you stay away from that pitfall and focus for a bit it is perfectly possible to have a really static website, my blog has been based on that for a couple of years now and I've never looked back after making that decision. It doesn't even have an analytics tracker, no outside fonts or anything that could slow it down. The end result is lightning fast performance, minimal memory footprint for the pages and rock solid because serving files over the web is a 'solved problem'. As an extra bonus by not including a bunch of eye candy and other unnecessary items I don't waste resources on the side of the viewer(s), and there is next to no chance of this setup developing a security hole in a framework.
Highly recommended if you want a low maintenance rock solid transmit only website.
Besides my blog, Pianojacq.com is set up much along the same lines, but there is a major difference, it interacts heavily with peripherals (MIDI) and needs a database (locally, not remotely), the end result is a highly interactive but still 100% static website.
Highly recommended if you want a low maintenance rock solid transmit only website.
Besides my blog, Pianojacq.com is set up much along the same lines, but there is a major difference, it interacts heavily with peripherals (MIDI) and needs a database (locally, not remotely), the end result is a highly interactive but still 100% static website.