Lovelytics

Photo by Conny Schneider on Unsplash

Role: Primary Developer

Collaboration: Development, Design, Project / account management

Project summary:

  • Served as the primary developer on a full site build focused on editor experience and repeatable page assembly: I introduced a component + module system so admins could publish structured pages without fighting one-off templates (this was the first site where I built that pattern end-to-end).
  • Implemented a broad set of front-end modules, including multiple card variants, a tabbed content module, and accordions, with substantial motion/animation on key marketing surfaces.
  • Built a Featured News module that reads admin-configured settings for what surfaces on the front end, with a sensible fallback when selections or content availability don’t line up.
  • Delivered a Resources experience with AJAX-powered filtering and pagination so users could explore a large library without full page reloads.
  • Beyond launch, led a major content migration moving a large volume of legacy Gutenberg block posts into the new IA and module model so the new system could actually be adopted day-to-day.

- Updated: May 1st, 2026 -

Lovelytics is a team of elite data and AI professionals who know how to make complex problems feel manageable—and even enjoyable. We bring clarity, speed, and heart to every project, partnering with clients to solve real problems with smart, sustainable solutions.

Lovelytics was a large build-and-migration project where I was the primary developer. The product goal wasn’t just a fresh theme: it was a publishable system. I built a module/component architecture that gave admins consistent building blocks (cards, tabs, accordions, and other layout modules) while keeping the front end cohesive as pages scaled.

On the marketing side, I added meaningful animation throughout the main experience where it supported storytelling without turning the site into a performance liability, and implemented a Featured News pattern that respects editorial controls from the admin while still behaving predictably with fallback content when needed.

The Resources section was the “heavy browsing” surface: AJAX filtering plus pagination so visitors could narrow results quickly and keep moving through deep content. Finally, a big slice of the effort was migration: translating a substantial backlog of Gutenberg-authored posts into the new structure so the organization wasn’t stuck maintaining two publishing eras at once.