One of the cooler projects I’ve worked on at Tutor.com was the creation of a simple content management system (CMS) to power our public website. For years, our website had no CMS capabilities. When someone wanted something changed, they asked a developer to change it. And then they usually waited a week for it to get done.
As our company grew, we were creating more pages on the site and making more copy edits than ever before, and it became clear that we were finally ready to integrate some sort of CMS into the site. We evaluated a ton of CMSes out there before deciding that we didn’t need a whole lot of fancy functionality and that we could probably write our own CMS to suit our needs pretty easily. As it turns out, we were right. We built a simple CMS in-house, and it’s been powering our website for many months now with no real hiccups.
To share a little about how we went about it, I put together a short white paper about the Tutor.com CMS describing the architectural design decisions we made, the implementation challenges we faced, and the solutions we came up with. Want to learn more? Read the PDF.