Over the past few years, most of the development projects we've worked on have been built on some sort of content management system. When a project comes across our desks, one of the first things we do is take a look at the goals, strategy, and requirements, and begin a discussion of what kind of tools we need to use to best get the job done. Having often used Drupal and Wordpress in the past, this has typically been a discussion of what type of CMS is best suited for the project. But on a recent project, we found ourselves questioning whether we needed a CMS at all.
The project involved presenting research and interviews that took place in the course of producing an academic book. There was a fixed amount of content, and the site wouldn't be edited or updated after it was launched. The site also needed to be responsive, adapting its layout and functionality to mobile and desktop displays.
Here's to thinking outside the CMS.