Lovelybit
[
back
]

Chimera CMS

web_development
laravel
php
php_storm
github
created=2013-01

A Creature Made of Many Parts

In the early days of Holiday Inn Club Vacations (HCV) we had a big problem: we had no real way to manage our websites...and we had a LOT of websites. Each of our business units (marketing, rental, etc) had multiple domains that they ran and it was on our team (Brand Services) to maintain each and every one of them.

We didn't have the budget or backing to pick an off-the-shelf content management system (CMS), and they had no interest in free options like Drupal or Wordpress. Our web needs were ever growing and all we had to use was a copy of Adobe Dreamweaver to do it with.

So I hatched a plan. If I couldn't get budget to buy a professional CMS and I couldn't get approval to use a free system — I would need to start working on building my own CMS from scratch.

If I couldn't get budget to buy a professional CMS and I couldn't get approval to use a free system — I would need to start working on building my own CMS from scratch.

The First Head of the Beast

The first version of Chimera I built by myself outside of work hours and I had to start small. My first goal wasn't to create a full fledged CMS, it was to create something that would make it easier to build new pages on the backend and be able to run multiple domains off of the same code base. I found a framework called CodeIgniter that would give us a model view controller (MVC) system and started to organize and rebuild the sites we had.

There was no "backend" site to log into yet and all changes still required a programmer to do it — but we were able to take our tasks that used to take a full week of manual work to do and get that time down to an hour. I had even figured out a way to take the same concept for web page building and have it build out our emails so we could load it into Salesforce Marketing Cloud (then known as ExactTarger).

Laravel Has Entered the Chat

After the first release, I was able to make a case to management that we needed a full web team and take our online presence more seriously. I was promoted to a Web Development manager and eventually hired on two new developers. Our team was small, but we were scrappy and finally had some additional support to make our CMS even better.

The second version of Chimera would be the start of it becoming a real CMS. We upgraded our tech stack to use Laravel as our framework, upgraded from Dreamweaver to PHP Storm as our IDE, and had starting to use GitHub for the first time so we could work better as a team and keep code backed up and safe.

Laravel let us do a lot as developers. We had a safe way to make and rollback database changes now, and we could finally handle more advanced features like user accounts and a full fledged admin panel. Plus, since it was fully built in-house, we could tailor the backend to very specific needs our company had — such as a gallery system for our resort pages that would allow us to upload a large set of photos, automatically tag them based on the folder structure, and then generate captions for each photo automatically based on the tags.

Achievement Unlocked

Version 3 of Chimera allowed us to use the CMS for more than just marketing sites. We could now manage — even with a small team of 3 developers (including myself) — internal site needs as well.

We built a new company-wide intranet (we had explored third-party options but they were all considered cost-prohibitive due to the large amount of employees we had across resorts) and gave limited access to HR so they could post new blog posts as needed.

We also rebuilt a training system for our Sales Team. This lead to the creation of an "achievement" feature to incentivize team members to log in and use the tool regularly. When users did actions (such as reading articles, logging in daily, etc) they would receive achievement notifications and received points that would rank them on a company-wide leader board.

A Legacy

In 2019, I would help oversee a project working outside agency, Willowtree, to overhaul our web strategy and finally condense our sites down to a consumer and corporate site. This would move us off Chimera and onto a REACT tech stack using Contentstack as the new CMS.

While I ended up leaving HCV sometime after that project wrapped up in 2021, I've been told by a member of my former team that they still actively use Chimera to this day to run legacy sites and the intranet.