Case study

Xperi

The build translated a polished visual direction into a responsive WordPress system without treating motion or the interactive map as isolated effects.

Client

Xperi

Role

WordPress development and interactive frontend implementation

Year

2021

Summary

Rebuilt Xperi’s website on WordPress with custom animation and a bespoke interactive map for a global technology brand.

The brief

Xperi needed a WordPress rebuild that could support a global technology brand and a visually ambitious experience. The implementation included custom animation throughout the site and a bespoke interactive map.

I was responsible for translating those interaction and development requirements into a responsive, maintainable website.

The challenge behind the polish

Animation creates value when it clarifies hierarchy, reinforces transitions, or helps users understand a relationship. It creates friction when it delays content, ignores device constraints, or becomes impossible to maintain outside the original page.

The interactive map introduced another layer of complexity. It needed to connect geographic information and user interaction while still fitting the site’s design language and responsive behavior.

The approach

The WordPress build treated motion and interaction as shared system behavior:

  • develop reusable theme structures rather than isolated page markup;
  • coordinate animation timing with content hierarchy;
  • keep interactions usable across different screen sizes;
  • preserve a meaningful experience when motion was reduced or unavailable;
  • build the map around clear data and interaction boundaries; and
  • keep editorial content separate from the code controlling presentation.

This allowed the site to feel expressive without making routine content changes dependent on rebuilding the animation layer.

Why the CMS still mattered

The public experience was highly visual, but it still needed to function as an operational website. WordPress had to give editors dependable structures, not expose every implementation detail behind the motion.

The custom theme created that boundary. Editors could manage content through the CMS while the frontend applied the interaction model consistently.

The takeaway

Xperi demonstrates my ability to deliver high-fidelity interactive work inside a practical CMS architecture. The goal was not motion for its own sake; it was a polished experience whose underlying system remained responsive, understandable, and maintainable.

Related writing