Case Study

Front-end overhaul simplifies development and deployment of content management system

The client

The client maintains a content management application responsible for collecting and updating data to be presented on public-facing websites.

The problem

The client wanted to be able to rapidly deploy new branded instances of the content management application. In the past, templates for each new instance had been created from scratch by an outside vendor. The existing JavaScript had been written in a way that didn't acknowledge the similarity of various interactions. The CSS didn't take advantage of the cascade; every new instance of the application required major changes. Snippets of HTML were duplicated in multiple templates.

How we met

The client had been seeking a lower-cost developer, but was referred to me by a mutual acquaintance. After we discussed their needs, it was agreed that my higher rate was reasonable considering the higher level of service and technical understanding I would bring to the table.

My solution

I worked with the client's back-end development team to re-envision the interface between the server and front end. Together, we developed a new system that abstracted common module behaviors, standardized the templating structure and hierarchy, and moved frequently-used markup to centralized files. I rewrote the application's JavaScript from the ground up using the jQuery library, creating a single framework that encapsulated common module behaviors (edit, save, etc.). I wrote HTML templates and CSS that leveraged the cascade and utilized standardized, semantic markup.

The outcome

The client now has a robust framework for developing and deploying new features with minimal effort on the front end. Branding and deploying new instances is greatly simplified by the new CSS and the centralization of frequently-used markup.