Southern Nazarene University

The brief

Southern Nazarene University needed more than a visual refresh. The project required a full rethink of how the website was structured, how editors would manage it, and how multiple site areas could live together without becoming a maintenance problem.

Institutional websites tend to accumulate complexity differently than a typical marketing site. They have more stakeholders, more recurring requests, more distributed content ownership, and more structural pressure from subdomains, departments, and academic programs. That makes them less forgiving of weak architecture.

So while the redesign mattered, the deeper question was whether the rebuilt system would actually reduce operational drag for the teams responsible for it.

The real challenge

Higher-ed sites create a specific kind of complexity. The problem is not only scale. It is the combination of scale and distributed responsibility.

Different groups need to publish confidently, but the institution still needs the platform to feel coherent. Shared patterns need to exist without making every section identical. Subdomains and adjacent site surfaces need enough flexibility to serve different audiences without becoming disconnected systems.

That meant the project had to solve for more than launch output. It had to solve for governance, reuse, and clarity after launch.

The approach

I treated the work as a platform problem first and a redesign second. That meant sorting content architecture, deciding where shared patterns belonged, and making sure the rebuild would improve speed and consistency instead of just changing the paint.

• Reworked the site structure so content teams could manage sections with less duplication.
• Built the project around HubSpot CMS patterns that supported long-term editing instead of one-off templates.
• Coordinated migration planning across the main site and connected subdomain experiences.

That approach matters because a university site will test every shortcut eventually. If the content model is weak, teams duplicate. If the template system is too page-specific, exceptions multiply. If the editorial workflow is unclear, people work around the platform instead of through it.

The build needed to reduce those failure modes, not just postpone them.

How the platform got stronger

The useful outcome was not only a cleaner front end. It was a better operating system for the institution's web presence.

The structure became easier to reason about. Shared content patterns became more reusable. Editorial teams got a system better suited to repeated updates rather than one-time migration energy. That matters because universities do not just launch and stop. They continuously publish, reorganize, campaign, recruit, and adjust.

If the platform does not make those routines cheaper, the redesign only solved the most visible part of the problem.

Why it worked

The final result created a cleaner operating system for the marketing and content team. That lowered the cost of change after launch, which is usually where these projects either prove themselves or start accumulating debt immediately.

The rebuild worked because it treated migration, information architecture, and editorial usability as parts of the same system. That produced something more durable than a cosmetic refresh.

It also made the project a strong example of the kind of HubSpot work I care most about: the kind where architecture choices directly shape whether the platform stays manageable under real institutional pressure.

The takeaway

For institutions, a migration only counts as successful if the new platform is easier to operate than the old one. That was the standard here.

The point was never only to move the university into HubSpot CMS. It was to give the institution a structure that could support future publishing, governance, and change with less friction. That is what makes this more than a redesign story. It is a platform story.