Migrating a Dynamic Website to Static Markup
This week, I finish one the longest projects I took on since joining the 8th Light team back in November: migrating our website to static markup. The current website was built on Clojure, using a set of homemade tools, and it’s beginning to show its age. It’s time to move on and iterate.
While working on the static rewrite, I got the opportunity to shape the foundation of a flexible codebase. Ensuring it’s friendly to everyone updating it involves knowing the system inside and out, and leveraging all that your tools have to offer. Along the way, I learned a few lessons on what it takes to achieve this sort of flexibility, and some ways to take advantage of a new environment.
No Database? No Problem.
Moving from a dynamic website to a set of a static files presented an obvious drawback: the lack of a database. For the new website, we settled on Middleman as our static site generator. Middleman—and other generators like it—come with support for data files, which allow you to extract plain data away from your markup and reuse it throughout.
With data files, we were able to extract things like our list of team members and the availability of careers in our various offices, without needing complex databases and SQL queries. Instead, we write our data in plain text files—and those can be easily read and edited by anyone on our team.
Choosing Your Battles
When taking the liberty to rewrite certain pieces of the codebase, it became very tempting to want to rewrite everything, and ensure the new release was as maintainable as possible. However, I knew this would take a considerable amount of time, and the clock was ticking—the longer I took on the rewrite, the more catching up I would have to do with changes made to the existing codebase.
In the end, I decided give up on some of these battles, and improve them in smaller iterations after the initial launch. That’s the beauty of software.