Zips Car Wash
Procedural Email, Landing Pages
Content Delivery Network
Zips Car Wash is a business that has seen explosive growth in the last few years. Pleth has been their web services since the early stages, and scaling their current site to meet their growth demands has been a challenge.
Platform: WordPress
AWS Services: EC2, RDS, CloudFront, S3
Getting Everything Straight
When I took over D&D of this website, it was five years old. There were *Thirty Six* WordPress plugins installed on the site. Needless to say, it was running a tad bit sluggish. My first task was to clean this up a bit.
The client needed several landing pages developed, and when they needed them, they needed them very quickly. They also had to package up the fields and send them to their CRM. Using the Gravity Forms plugin (I’m a huge fan) and PHP, I was able to grab the submitted info from the form submission and package it into a JSON object, where it was then posted to their CRM’s API.
On-the-fly Customization & Personalization
The Client wanted to start selling car wash memberships, gift cards, and plans on their website. Naturally, this means that WooCommerce became involved. Our team got to work on creating products and variations for over 100 stores and we trained the client on how to effectively update these items and location information.
For the memberships, however, there was a completely different process for the customer to redeem their purchase, and this meant that there needed to be special instructions and imagery included in the emailed receipts based on which products were present in the order. The client also required that the regional manager receive an emailed notification so that they could verify that the purchase was legit. All of this required digging into the back-end and making custom WooCommerce templates.
Email Image Hosting Through CDN
At this point, through many meetings and conversations where I recommended that they upgrade their setup, the client was starting to see the benefits of moving to a more robust system such as Drupal to meet their ever-scaling needs. They were also interested in having their own dedicated server for various reasons. One of those reasons was having a place to host images that a third-party graphic designer was making for their email campaigns. Since they were on a shared hosting environment, we needed to find an interim solution.
That solution came in the form of a string of AWS services. The graphic designer straight-up required that he have SFTP access to upload his images, and no other method would work for him. So, I delivered. A t3.nano EC2 instance was used as an intermediary between the designer and an S3 bucket, providing the interface desired. A CloudFront distribution was put in front of the S3 bucket to serve the files, and Route53 was used to give each image a more digestible URL.
Looking for my resume?
Look no further!