Multi-Property Website System.

One shared theme. Thirteen mall websites. A common foundation.

Theme architectureStructured contentSetup & rollout tools

Thirteen sites. Thirteen versions of the work.

The websites had drifted apart in structure, design, and upkeep. A fix or new page type meant repeating the work across the portfolio.

The strongest existing site became the starting point for a shared theme, with a common content model and a repeatable way to set up each property.

Shared where it helps. Local where it matters.

Across the portfolio

The foundation.

A WordPress theme built on Genesis. Page layouts and Advanced Custom Fields organized into a structure every site can use.

  • Theme & page templates
  • Content field definitions
  • Setup & verification tools
At each property

The details.

Property content stays with the property: its stores, events, hours, homepage information, and branding details.

  • Tenants & events
  • Hours & visiting information
  • Branding & homepage content

A rollout you can repeat.

The theme is only part of the system. Custom plugins and a written runbook give each site a consistent path onto the foundation.

  1. Set up.

    Configure the property site using shared setup tooling.

  2. Sync.

    Match each site’s content to the shared fields.

  3. Verify.

    Check the configuration before moving through the rollout.

  4. Repeat.

    The same documented steps, property after property.

A better page type. A fix to the theme. One place to make it.

The shared architecture lets improvements travel across the portfolio, instead of being rebuilt separately for every property.

Project notes

Scope
Thirteen mall websites across the United States. The theme and tools are in place on staging copies, with content migration underway ahead of launch.
Our role
Theme architecture, content model, setup and verification tooling, and the rollout on each site.
Built with
WordPress, Genesis, Advanced Custom Fields, custom plugins, and a written rollout runbook.