Multi-location senior living platform
BUILT created a WordPress multisite platform for Avista Senior Living that gave every community its own identity, services, lead routing, and virtual tours while keeping the entire network connected through one shared technical foundation.
Visit Avista Senior Living
The problem
Avista Senior Living needed one platform for communities with different names, branding, services, and local experiences. The challenge was preserving those differences without maintaining separate websites, while still keeping every location connected to the broader Avista network.
The response
BUILT created a WordPress multisite network around one shared theme and component system. The underlying website structure could be maintained centrally while each community controlled the details that needed to remain local, including branding, services, forms, tours, and content.
Create one multisite network and shared theme for the entire Avista organization.
Allow each community to apply its own branding, colors, services, and location-specific content.
Connect inquiries, contact forms, and virtual tours directly to the appropriate community.
Automatically surface every community throughout the corporate website, navigation, and location map.
The platform
Avista’s communities needed to share infrastructure without being forced into identical websites. A central theme handled layouts, components, responsive behavior, and functionality across the network. Location-level configuration then controlled the elements that needed to change from one community to another. That created a repeatable system Avista could use across its entire portfolio while allowing each community to retain its own identity.
01
Each Avista community could use its own name, logo, and color scheme while remaining on the same shared theme. Instead of creating separate designs for every location, branding settings were applied throughout each community site automatically.
02
Not every Avista community offers the same services. The platform allowed services to be configured independently by location so each website accurately reflected the care options available at that specific community.
03
Contact experiences were configured at the community level so inquiries could be routed directly to the appropriate location. Each community could also feature its own virtual tours, giving prospective residents and families an experience specific to the property they were considering.
04
Individual communities weren’t isolated websites. Locations in the multisite network automatically fed into Avista’s main navigation and community discovery experience. The primary location map pulled communities from across the network and displayed them across four states, eliminating the need to maintain a separate location directory manually.
More of the system
Common functionality lived in the shared platform, while location-specific details remained configurable at the community level. That reduced duplication without limiting what individual communities could control.
Shared architecture
One central WordPress theme powered the layouts, components, responsive behavior, and functionality used throughout the network.
Location branding
Community-level settings controlled logos and color schemes, allowing each location to maintain its own visual identity within the shared system.
Service management
Services could be enabled or changed independently for each community without affecting the rest of the network.
Lead routing
Forms and contact routing were configured by location so prospective residents and families reached the community they were actually interested in.
The work
The multisite network, shared theme, community configuration, service architecture, forms, virtual tours, navigation, and location discovery were designed as parts of one connected system.
Avista needed consistency across the organization, but forcing every community into the same branding and service structure would have created its own limitations. The shared theme standardized the underlying system while allowing meaningful differences at the location level.
Branding, services, forms, and tours weren’t treated as exceptions that required development work every time something changed. They were built into the system as information that naturally varied by community.
Community information already existed inside the multisite network. Rather than maintaining a separate corporate location directory, the primary site used that same network to power navigation and map-based community discovery.
BUILT created the WordPress multisite architecture and shared front-end system that powered Avista’s network of community websites.
Instead of managing a collection of disconnected websites, Avista had one platform designed around the way a multi-location organization actually operates.
Start a conversation
When every location has its own services, branding, content, and local teams, separate websites create unnecessary duplication. But forcing every location into the same experience creates a different set of problems. BUILT creates multi-location platforms that centralize what should be shared while giving individual locations control over what needs to remain local.
A Pando company
