I've been pondering this for awhile now, as one of my clients makes 99%-static websites for their marketing campaigns. They currently use Drupal as their CMS, but I see that as overkill, as most of the site is static and the layout shouldn't be changed by anyone with publishing rights. However, you wouldn't believe how hard it is to break through the "$CMS can do it all, easier, faster, and cheaper" thinking that has been sold to executives.<p>In my client's case, the only "content" that changes are blog posts, media (screens/videos) and, possible, promos on the front page. Everything else stays the same, 24/7/365. There is little reason spend money on using a CMS that can do everything, when a simple HTML/CSS/JS and a clean web framework (Django/Rails/Symfony) will do.<p>What I've attempted to explain to higher-ups is that website development should be built on progressive enhancement, because it is easy to start with something bare and add the features (models, callouts to external services) fairly easily and with little code. The flip side is that if you start with a kitchen-sink approach (a la Drupal/Joomla) you will need to take away features because the administrators will have too much power to change the site, increasing risk that something bad will happen.