The Challenge
Sinclair needed a central destination for current DINOPAY promotions, redemption instructions, and answers to frequently asked questions. The offers change regularly and include specific activation periods, promotional artwork, calls to action, and legal details. Managing every launch and expiration manually would create unnecessary work and increase the risk of outdated offers remaining visible. The page also had to be developed within an established legacy Drupal website with limited documentation and no access to the original development team.
What I Owned
The Approach
Make frequently changing promotions easier to manage—and easier for customers to understand.
A flexible DINOPAY destination that gives Sinclair a more reliable way to manage changing promotions and gives customers one clear place to understand available offers. The scheduled content system reduces repetitive campaign maintenance and helps prevent expired promotions from remaining online. The categorized FAQ turns a large support library into an approachable self-service resource. The project also demonstrates my ability to step into an unfamiliar legacy codebase, understand how it works, and add meaningful new functionality without rebuilding the entire system.
Inside the Build
Scheduled Promotional Offers
I developed custom Drupal entities with configurable publish and unpublish dates for each promotion.
This allows Sinclair to prepare campaigns ahead of time while reducing the manual work and risk involved in launching and removing time-sensitive offers.
Categorized FAQ Experience
I built an interactive FAQ system that organizes a substantial amount of support content into selectable categories.
Visitors can quickly focus on the topic they need, while Sinclair can continue managing the questions and answers through Drupal.
AI-assisted Legacy Development
I used ChatGPT as a technical research and troubleshooting partner while working through the lightly documented legacy Drupal build.
The AI-assisted process helped me interpret existing development patterns, understand unfamiliar entity and template relationships, and evaluate possible solutions more efficiently. Every change was still reviewed, implemented, and tested within the actual website environment.