Our company website has been powered by Drupal since Resonance Development was incorporated and this domain was registered on December 18, 2008. Fortunately for me, Drupal 6 had been released earlier in the year, and with lots of runway ahead of us, upgrading hasn’t been a necessity. This site would have been supported until Drupal 8 is released sometime in 2014, as long as I kept the server online and stayed on top of Drupal security updates.
It goes without saying that I should spend more time creating new content, updating our portfolio (stale for years by times), adding team members, etc. But even given a modest blogging habit and other content changing a few times a year, the features of a full-blown CMS are somewhat lost on us.
There are a few benign realities of maintaining a mostly-static web site in Drupal:
Yet, we find ourselves of maintaining brochureware site in a CMS because we desire to keep our content structured (often in a database), we need a templating solution, require some degree of content reuse across pages and sections, we need some web forms, RSS feeds, and it looks like a nail, damnit. And we’re left with something that does need ongoing care and feeding because the Internet can be an unforgiving place for unmaintained software.
The truth is, it’s not a big jump for those already comfortable with a few basic tools of web development. Git and GitHub are used for versioning and distribution (and in this case, free hosting). Site data is stored in YAML and content formatted with Markdown. Working knowledge of front-end concerns (HTML/CSS/JS) is assumed. You can use Prose.io for editing content if you like, but we don’t bother.
Going static means working within a tighter set of constrains than we’re used to, but it makes for cheap or free hosting, zero security concerns ever, no threat of CMS obsolescence, and a codebase that is simple enough almost anyone could modify or extend. You could say the exact opposite about our former Drupal site.