As part of a new CMS that I'm planning, I'm going to be caching the HTML output of some "static" content. I say "static" because no content stored in a database is really static, but it's close enough. The system will MD5 hash the request URL and save a minified version of the HTML output in a cache folder. The next time the page is requested, the CMS will check if a cached version exists, then it'll check the age of the file and then serve up the cached version, thus saving a lot of resources (especially when it comes to DB calls).As part of a new CMS that I'm planning, I'm goi