Skip to main content

University Website Design System

I created a reusable web design system for a higher education institution, bringing consistency to its digital presence and laying the groundwork for departments to manage their own content.

Institutional details and imagery have been anonymized for this case study.

Project Overview

Problem

The CMS required developer support for basic updates, leaving departments unable to maintain their own pages. Content grew stale, and inconsistent design weakened usability and the university’s visual identity.

Goal

Pair an accessible design system with a CMS that supported departmental ownership. Prioritize intuitive editing, structured content, role-based permissions, and global updates so editors could work independently within shared standards.

Role

As Senior UX Developer, I led research, CMS evaluation, component design, and front-end development, delivering the design library within three months. I gained leadership support for CMS modernization, partnered with Marketing and Communications on visual direction, and advocated for editor training.

Audience

Prospective students, families, faculty, and other university visitors, along with departmental content editors and the web team maintaining shared standards.

Creating a Scalable Design System

Working with Marketing and Communications, I used mood boards to align stakeholders on a shared visual direction. Movement, rhythm, layered imagery, and warm accent colors informed a consistent approach across pages and components.

Content editors across colleges and departments needed patterns they could reuse without making every page a custom design task. I built a modular library of buttons, tabs, alerts, cards, and layout grids to support different content needs within shared standards.

Reusable layouts and component variants gave teams a consistent starting point. Responsive behavior, accessible interactions, and front-end implementation were part of each pattern, so consistency extended beyond appearance to how pages worked.

Accessibility as a System Requirement

The system’s WCAG 2.1 AA requirements informed component design and development from the start. I checked contrast, heading structure, focus states, and ARIA usage through regular page scans and manual review. Building these checks into reusable patterns gave future pages an accessible starting point.

axe DevTools results showing zero detected accessibility issues for the scanned template.
An axe DevTools scan of the template reported zero detected issues. Automated scans were paired with manual checks during development.

I researched the state resource link requirements in effect during the project. The homepage-link provisions informed my recommendation to group state resources in a homepage ribbon, simplifying interior-page footers and reducing mobile clutter.

Anonymized homepage footer grouping campus resources, audience links, and transparency information above a separate state services ribbon.
State resources sit in a separate homepage ribbon, keeping the main footer focused on visitor needs.

Building a Foundation for Sustainable Growth

Within three months, I delivered the design library and established groundwork for CMS modernization. I moved to another role before implementation. My contribution established a foundation for rollout, editor training, and adoption; those steps were not completed during my involvement.

Delivered During My Involvement

  • A complete design library with reusable components and a visual direction developed with Marketing and Communications.
  • Front-end patterns supported by responsive behavior, accessibility checks, and component documentation.
  • CMS evaluation and planning, with leadership support for modernization and editor needs guiding the recommendation.

Intended Organizational Benefits

  • More ownership for departmental editors and less developer time spent on routine updates.
  • More consistent branding, accessibility, and content maintenance across the university.
  • A framework for rollout, editor training, and ongoing governance as the site grew.