Why is Rice moving to a unified web design and platform approach?

As Rice continues to grow in reputation and complexity, our digital ecosystem must evolve alongside it. This initiative is driven by long-term institutional priorities rather than short-term design trends.

Over time, Rice’s web ecosystem has grown organically across different platforms, templates, and custom implementations. While this allowed flexibility, it has resulted in inconsistent user experiences, duplicated content, accessibility gaps, uneven performance, and rising maintenance costs.

A unified approach allows us to:

  • Establish a consistent and recognizable Rice digital presence
  • Improve accessibility compliance and reduce institutional risk
  • Strengthen security and performance standards
  • Align web storytelling with Rice’s strategic priorities
  • Reduce technical debt and long-term operational costs

Ultimately, this effort ensures that Rice’s digital presence reflects the excellence of the institution itself.


What does “unified” actually mean in practice?

The term “unified” can sometimes raise concerns about uniformity or restriction. In reality, it refers to shared foundations rather than identical outcomes.

“Unified” does not mean every website will look identical. It means we share a common system of design principles, components, and technical standards.

In practice, this includes:

  • A shared design system (colors, typography, layout patterns, components)
  • A common content strategy framework focused on audience needs
  • A composable technical architecture (headless CMS + modern frontend)
  • Clear governance and publishing standards
  • Units maintain flexibility in how they tell their stories, structure their content, and prioritize messaging — but within a cohesive institutional framework that ensures quality and consistency.

This balance enables both institutional cohesion and academic individuality.


What platform and technology are we moving to — and why?

Technology decisions are being made with long-term sustainability, flexibility, and omni-channel delivery in mind. The goal is to future-proof Rice’s digital infrastructure so that our content is not locked into a single website experience.

Rice is transitioning from Drupal Site Factory to a composable, headless architecture built on:

  • Storyblok (headless CMS for structured content management)
  • Astro (modern frontend framework for performance and scalability)
  • Tailwind CSS (utility-first framework aligned with a design system)

In a headless system, content is created once in a structured format and delivered via APIs to multiple front-end experiences. This means Rice content is no longer tied to a single website template. Instead, it can power:

  • The primary rice.edu web experience
  • School and department sites
  • Microsites and campaign landing pages
  • Mobile-optimized experiences
  • Digital signage or kiosk displays
  • Future platforms we have not yet adopted

This omni-channel capability allows Rice to publish content once and distribute it consistently across channels while maintaining brand and accessibility standards.

This architecture offers:

  • Faster page load speeds and improved performance
  • Greater flexibility in content modeling
  • Stronger separation between content and presentation
  • Easier integration with third-party systems
  • Long-term scalability and sustainability

This shift positions Rice to innovate more rapidly, respond to new communication needs, and deliver cohesive digital experiences across platforms — not just on a traditional website.
 


How does this specifically benefit my department or unit?

Modernization must deliver tangible value to schools, departments, and centers. The benefits are both technical and strategic.

At the unit level, benefits include:

  • Faster site performance and improved SEO visibility
  • Built-in accessibility standards at the component level
  • Flexible, reusable content blocks for storytelling
  • Better support for multimedia, research narratives, and feature content
  • Reduced reliance on custom development or ad-hoc fixes

Rather than spending time troubleshooting templates or patching accessibility issues, teams can focus on strategic messaging and high-impact content.

In short, this initiative helps units operate more efficiently while increasing their digital impact.


Will we lose control over our website content?

Autonomy is an important value across campus, and this question is both reasonable and expected.

Units will continue to control:

  • Messaging and voice
  • Editorial priorities
  • Key landing pages and campaigns
  • Academic and research narratives

The alignment occurs at the design system and technical standards level — not at the message level. This ensures institutional consistency while preserving academic autonomy.

The goal is shared infrastructure, not centralized storytelling.


How will branding and visual identity be managed?

Rice’s brand is one of its most valuable institutional assets. A unified approach strengthens rather than diminishes it.

The unified design system incorporates Rice’s official brand standards and ensures visual cohesion across schools, centers, and administrative units.

Where appropriate, units may have room for differentiation within established guidelines. Branding governance will be coordinated with University Marketing and Communications to maintain institutional integrity while supporting unit-level expression.

This ensures Rice presents a confident and consistent identity to global audiences.


What about accessibility and compliance?

Accessibility is not optional — it is a legal, ethical, and strategic responsibility.

Instead of retrofitting accessibility after launch, the new framework builds compliance into components by default.

This includes:

  • WCAG-aligned components and templates
  • Reduced risk through standardized patterns
  • Governance and review workflows
  • Training and documentation for editors

This approach improves usability for all audiences and mitigates institutional legal and reputational risk.

By embedding accessibility at the foundation, we create a more inclusive and resilient web ecosystem.


How will content migration be handled?

Migration represents an opportunity for improvement, not simply replication.

Migration will be phased and strategic — not simply a content transfer.

Each unit will:

  • Conduct a content audit
  • Identify outdated or redundant pages
  • Archive low-value material
  • Rewrite or optimize high-priority content
  • Align messaging with audience goals and Rice’s strategic priorities

The goal is modernization and refinement, not duplication of legacy structures.

This process ensures higher-quality content and stronger alignment with the audience moving forward.


What is the timeline for implementation?

Spring 2027


What training, certification, and community support will be provided?

Sustainable modernization depends not only on technology, but on people. Training, professional development, and community-building are central pillars of this initiative.

Support will include structured onboarding and ongoing enablement opportunities such as:

  • Comprehensive documentation and evolving style guides
  • CMS training workshops for content editors
  • Accessibility and inclusive design training sessions
  • Web writing and content strategy workshops
  • Technical training for developers working within the design system
  • Office hours and one-on-one consultation support

In addition to baseline training, we will introduce role-based certification pathways to ensure quality and consistency across campus. These may include:

  • Certified Content Editor training
  • Certified Web Publisher training
  • Design System Contributor certification for developers
  • Accessibility Steward training for designated unit representatives

Certification programs help clarify expectations, establish shared standards, and elevate professional expertise across the university.

Community engagement will also be strengthened through:

  • Quarterly Web Community Meetings for knowledge-sharing and updates
  • Working groups and committees under the Web and Digital Strategic Committee (WDSC)
  • Cross-functional collaboration opportunities (communications, IT, marketing, research units)
  • An annual Rice Web Summit / Digital Conference to showcase best practices, innovation, and institutional progress

These recurring touchpoints ensure transparency, peer learning, and continuous improvement rather than one-time rollout training.

The objective is not only to deploy a new platform, but to cultivate a connected, skilled, and forward-thinking web community at Rice.


How does this align with Rice’s strategic plan?

Digital presence is directly connected to institutional ambition.

Rice’s strategic plan emphasizes global visibility, research excellence, innovation, and institutional distinction. The university website is a primary channel through which prospective students, faculty, donors, partners, and media experience Rice.

The modernization effort supports these goals by:

  • Enhancing digital visibility and search performance
  • Elevating research and academic storytelling
  • Improving digital infrastructure resilience
  • Enabling multilingual and personalized experiences

The web must reflect Rice’s ambition and academic excellence in every interaction.


What about specialized functionality (labs, databases, forms, integrations)?

Some units require advanced tools and technical integrations, and flexibility remains important.

The composable architecture supports integration with external systems and the addition of custom functionality when strategically justified.

Options include:

  • API-driven integrations
  • Custom components within the design system
  • Secure connections to research tools or data sources

The focus is on flexibility within sustainable technical standards that protect long-term viability.


How will governance work long term?

Sustainability depends on clarity and shared responsibility.

Governance ensures quality, sustainability, and alignment. It includes:

  • Defined ownership roles for content and design
  • Clear accessibility and brand standards
  • Component review and approval processes
  • Content lifecycle management practices

The Web and Digital Strategic Committee (WDSC) will provide strategic guidance and cross-campus coordination.

This structure supports accountability while encouraging collaboration.


What are the risks of maintaining the current ecosystem?

Understanding the risks of inaction is as important as understanding the benefits of change.

Maintaining fragmented systems increases:

  • Security vulnerabilities
  • Accessibility exposure
  • Brand inconsistency
  • Technical debt
  • Operational inefficiency
  • Long-term costs

Modernization is both proactive risk mitigation and strategic advancement.

Choosing not to evolve would ultimately cost more — financially and reputationally.


How can our unit engage proactively?

Partnership and participation strengthen the overall outcome.

Units can:

  • Volunteer as pilot or early adopter participants
  • Participate in workshops and listening sessions
  • Contribute feedback during design and content development phases
  • Engage with the WDSC for representation and guidance

Early collaboration helps shape a system that meets diverse campus needs while strengthening Rice’s unified digital presence.

Engagement today ensures smoother transitions tomorrow.


What is the role of the Web and Digital Strategic Committee (WDSC) and related committees?

Strong governance ensures that modernization is collaborative, transparent, and sustainable. The WDSC serves as a cross-campus strategic body that provides guidance, oversight, and alignment for Rice’s digital ecosystem.

The WDSC and its related working groups will:

  • Establish and maintain web governance standards
  • Guide design system evolution and component approvals
  • Align digital initiatives with Rice’s strategic priorities
  • Provide representation from schools and administrative units
  • Review major web initiatives for institutional impact
  • Support accessibility and compliance oversight

In addition to the WDSC, specialized working groups (e.g., accessibility, branding, development and content strategy) will help operationalize standards and ensure subject-matter expertise informs decision-making.

This structure ensures that modernization is not centrally imposed but collaboratively stewarded across the university.


How will quality assurance and continuous improvement be managed?

Modern web governance requires ongoing measurement and accountability — not just launch readiness.

Rice will incorporate tools such as Siteimprove into the publishing workflow to support:

  • Accessibility monitoring (WCAG 2.2 AA alignment)
  • Broken link detection
  • Content quality checks
  • SEO optimization insights
  • Policy compliance tracking

Siteimprove will serve as a diagnostic and monitoring layer that complements training and governance, helping units proactively identify issues rather than reactively correcting them.

Combined with structured governance, quarterly web community meetings, certification programs, and ongoing audits, this ensures continuous improvement rather than one-time compliance.


For additional questions or to discuss your unit’s transition planning, please contact the Office of Public Affairs or the Web and Digital Strategic Committee.

Downloads

Useful tools, files and templates to help you bring the identity to life.

 

Get started

Questions

In need of support or have a custom request?

 

Find answers

Rice Public Affairs

We’re available to help you effectively use the Rice brand in your communications.

 

Meet the team