About the Client
The client is a leading international university with operations across South Asia, East Africa and beyond. It works across education, examination and healthcare through three distinct institutional entities, each with its own audiences, stakeholders and priorities. All three shared one web estate of more than 3,000 pages, serving users across multiple regions and languages.
The Ask
The university came to Tricension looking to refresh its web presence. The site no longer reflected the institution it represented: it was out of step with the university’s content strategy and brand, and it didn’t serve its audiences well. The university needed a website that would:
- Align with its content strategy and brand identity
- Represent three institutions coherently, without losing each one’s voice
- Reach audiences across regions, in their own languages
- Give prospective students, patients and exam candidates an online experience that reflects a world-class institution
Renew or Replatform?
Before redesigning anything, Tricension assessed the existing setup to understand why the site had fallen behind. The assessment found several bottlenecks:
- Developer Dependency: Every content update, however small, had to go through developers on SharePoint, so the site couldn’t keep pace with the institution.
- Content Sprawl: Duplication had spread across 3,000+ pages, making the site harder to maintain and harder to navigate.
- Inconsistent Conversion Paths: Calls to action varied from section to section, with no consistent journey for prospective students, patients or candidates.
- No Performance Visibility: There was almost no data on what content was working.
These weren’t separate issues. They all came back to the platform. A redesign on SharePoint would look better at launch, but within months the site would fall behind again, because the content team still couldn’t update it without a developer.
The timing helped. The SharePoint renewal was coming up, which gave the university a natural point to change direction. Instead of refreshing the site on the same platform, Tricension recommended using that window to move to Storyblok, a headless CMS that would let the content team keep the site current long after launch.
The university agreed, and the refresh became a re-platform.
What Tricension Delivered
Application modernization is at the core of what Tricension does. We help organizations move off legacy platforms that limit what their teams can do, and onto architecture built for how they work today.
We brought that same approach to this engagement. Our experts re-platformed the university’s full web estate on Storyblok, a headless CMS that separates content management from the front end entirely.
Key components of the solution:
- Headless Architecture: Content is managed independently of the front end, so editors can publish without touching code and developers are no longer the gatekeepers for content.
- Multi-Entity Content Model: A component-based structure lets each institution own its content while sharing common elements across all three, all on one platform.
- Visual Editing With Guardrails: Editors build and preview pages in real time, using components that keep brand and structure consistent.
- Migration as Cleanup: Thousands of pages were consolidated and restructured during migration, so duplication was resolved on the way in rather than carried over.
- Custom Language Packs: Storyblok didn’t support Urdu, Swahili or Amharic out of the box. Tricension worked directly with Storyblok to add all three.
- Structured Handover: The content team was trained and running the site independently from launch.
Addressing Delivery Challenges
This was not a single-stakeholder project. Approvers sat in different countries, each institution had its own priorities, and content strategy was developed alongside design. Scope shifted, feedback cycles were long, and the direction changed significantly more than once.
Here’s how Tricension kept the program on track:
- Parallel Workstreams: Strategy, design and migration ran at the same time, so the new site reflected how the university actually communicates rather than how the old site was organized.
- Layered Governance: Working sessions handled daily delivery, weekly check-ins kept teams aligned, monthly reviews tested strategic direction, and a steering committee made decisions that needed senior sign-off.
- Early Risk Escalation: Risks went to PMOs and sponsors while they were still small, before they could become blockers.
The Impact
With Storyblok in place, the university now has a website its team can actually run:
- Publishing Time Cut From Days to Minutes: The content team updates the site directly, with no request cycle.
- Engineering Capacity Freed: Routine content changes no longer reach IT.
- One Coherent Platform: Content is consolidated and consistent across three institutions and multiple regions.
- Visibility Established: Performance tracking is in place for the first time, so content decisions can be based on data.
- Reach Extended: Urdu, Swahili and Amharic open the site to audiences it previously underserved.
- Future-Ready Foundation: The headless architecture scales with the university rather than limiting it.
Is Storyblok Right for Your Organization?
Storyblok is a strong fit for organizations that need their digital presence to move as fast as the business does. Its headless, composable architecture separates content from code, so marketing teams can create and publish independently while developers focus on building and integrating. The same content can feed websites, apps and other channels, and the platform scales without needing to be rebuilt as needs grow.
Tricension helps organizations decide whether Storyblok is the right platform for them and, if it is, plan and deliver the move. That covers architecture, content modeling, migration and integration, all aimed at leaving teams with a platform they can own long after launch.
Considering Storyblok for your organization?
Let’s talk through your current platform and whether a headless CMS makes sense for where you’re heading.
Talk to Our Team






.webp)