Back in 1994 we started out with plain old static HMTL. Websites were created by either coding them by hand or by using a GUI application such as Microsoft Frontpage (RIP) or Adobe Dreamweaver. The web was fast, it had to be, the last mile Internet at that time was largely built out of 28k dial-up modems. But sites were difficult to maintain and without a “webmaster” (webmaster@yourdomain was a thing) you were left with site you couldn’t update.
Enter the Content Management System (CMS). A CMS provided an easier way for sites to be built and maintained, either by an individual or team. But honestly, for most websites a full blown CMS like WordPress is a lot more engine and associated maintenance than is needed. A CMS needs a database and some type of server side scripting support. In addition to the CMS itself you’ll need several plugins and a theme. All of these things (PHP, MySQL DB, WordPress, WP Plugins, WP Themes, etc.) require complex configuration and significant ongoing maintenance. Each of them also presents a point of attack and resource constraints (i.e. performance issues). All complexities you probably didn’t expect when you decided to launch your website.
Without the need for complicated setups these new static sites load extremely fast and are immune to attack. Let me say that again. They are immune to attack. Static sites are safe, fast and the only thing that needs to be updated is your content.
A New Simple Model For Static Sites (and sleep)
- Host and distribute your site using a CDN (like Site CDN).
With no database, no server side scripting and distributed content you can sleep knowing your site will be running when you awake.