Camp Registration System

Challenge

Every year there were features that were added, modified, and in some cases removed. This client operates 17 different centers with unique dates, age ranges, regulations, and individual requirements. Each time a new feature was needed, a determination would need to be made. Is this a "one-off"? a new global feature? something that should be bandaided in for times sake, and re-addresses?
Keeping the system maintainable over 6 years of registrations was an interesting and rewarding challenge.

Functionality Screenshots

Technologies Used

Javascript

Local storage of family information (parents x2 and children x5), child age range verification, form validation, AJAX loading of location information.

PHP

Processing submissions, calendar rendering, and more.

MySQL

Storage of processed inventory/records, filtering of locations/data.

CCCRM API

Integration into clients CRM for entry of data into client's sales funnel.

CSS Flexbox

Frontend Layout & Responsive Design