Back Home
Nov 2024 — Mar 2025 UX Research UX/UI Design Front-End Development WordPress

Making a Research Facility Easier to Discover and Access

I researched, designed, and developed a responsive content hub for the Toronto NanoFabrication Centre (TNFC) at the University of Toronto's Department of Electrical and Computer Engineering (ECE). The project brought the lab's previously standalone website into ECE's existing digital ecosystem, improving how its facilities, services, and access requirements were organized and presented.

Explore Case Study

From an isolated lab website to

Part of ECE's digital ecosystem.

TNFC's standalone website operated separately from ECE's branding, navigation, and broader digital ecosystem. Its content structure also made important information about the facility and how to access it harder to discover.

Standalone TNFC website
A separate digital property disconnected from ECE's branding and navigation.
TNFC within ECE
A responsive content hub integrated into ECE's website, branding, and navigation.

Key Outcomes

Stronger Digital Integration

Integrated TNFC into ECE’s public-facing website, connecting the facility to the department’s established branding, navigation, and wider digital ecosystem.

Improved Information Discovery

Surfaced TNFC’s two lab facilities on the homepage, making them easier to identify without navigating through nested pages.

Simplified User Access

Consolidated information previously spread across five sub-pages into a single User Access page, bringing forms, training, fees, policies, and compliance information together.

Scalable Interface Components

Created reusable interface patterns that were subsequently applied to the Grid Modernization Centre, extending the work beyond TNFC to another ECE web property.

Defining the information architecture around user needs

The existing site had numerous top-level pages that primarily acted as link aggregators, leaving important information buried within sub-pages.

By assessing the existing content against user needs, I identified two primary flows:

Discover TNFC: Understand what the facility is and what it offers.

Access TNFC: Find the information required to use the facility.

These flows informed how content was organized, prioritized, and connected throughout the new content hub.

Designing information hierarchy for discovery

The Lab's two facilities were presented as a subpage under "About Us", making them harder to discover within the existing site structure.

I recommended surfacing them directly on the homepage. A structured card grid gave each facility a clear place in the information hierarchy, allowing visitors to recognize the available facilities without navigating through multiple levels.

Streamlining the user access journey

Information required to access TNFC's facilities was distributed across five sub-pages covering forms, training, fees, policies, and compliance.

TNFC's User Access Page [Before]
TNFC's User Access Page [Before]
TNFC's Access Forms Page [Before]
TNFC's Access Forms Page [Before]

I consolidated these requirements into a single User Access page, bringing the information needed to understand the process into one place.

For lengthy content that was less suited to the page layout, such as access-fee tables.

I recommended the content team create downloadable PDFs linked directly from the page.

Designing visual hierarchy to prioritize important content

Our Research told us that information about credibility factors and industry connections such as Partner organizations required prominence.

TNFC's Partners Page [Before]
TNFC's Partners Page [Before]
What it looks like now
What it looks like now

The design decision I made guided the broader interface: To prioritize information based on its importance rather than leaving it buried within secondary pages.

I moved the partners section to the homepage and designed a three-column layout featuring an auto-scrolling logo gallery.

This gave the organizations a more visible place within the content hub and made their relationships with TNFC easier to recognize.

Designing reusable components for a scalable system

ECE did not have a shared component library at the time, so interface patterns were often rebuilt across web properties.

I designed TNFC's components as modular, repeatable patterns that could be extended rather than recreated. For eg, the facility and service card grids could accommodate additional content without requiring an entirely new interface pattern.

These components and patterns were subsequently reused when integrating another ECE web property, the Grid Modernization Centre. This extended the value of the work beyond TNFC and demonstrated how its interface patterns could support other facilities within ECE's digital ecosystem.

Designing a responsive experience across devices

I designed and implemented the content hub to adapt across mobile, tablet, laptop, and desktop screen sizes. Layouts and components were adjusted to maintain a coherent experience across viewports rather than treating the desktop design as the only reference.

My Content Hub Design - Tablet (Click to view Full Design)
My Content Hub Design - Tablet (Click to view Full Design)
My Content Hub Design - Mobile (Click to view Full Design)
My Content Hub Design - Mobile (Click to view Full Design)

I moved the partners section to the homepage and designed a three-column layout featuring an auto-scrolling logo gallery. This gave the organizations a more visible place within the content hub and made their relationships with TNFC easier to recognize.

Reflections

I positioned TNFC as a core, high-value research facility within the department.

Every design decision was driven by the need to ensure ease of access to the regulations, including access, training, billing, and safety. At the same time, the pages were designed to feel native to ECE while also expressing TNFC’s identity and values.

After I left, other parts of the site and new integrations such as the Grid Modernization Centre reused patterns that were originally designed for TNFC. The patterns were reused after I left—not only were they well-liked—the structural decisions made sense.

The prototyping for the TNFC homepage and its initial sub-page was done in under two weeks—because I wanted working drafts in front of stakeholders early.

Why? There were a couple of design decisions that non-design stakeholders couldn't envision at first. My working drafts and prototype were instrumental in ensuring they weren't approving something they misunderstood or required major rework late in the process.

The approvals process took much longer than anticipated, which caused the project to be in the final phases of web development during the final week of my contract—causing a slightly rushed production of assets and quick turnaround on responsiveness and visual polish. Most other delays were scheduling related.

Contact Me

I'm in the people business, so get in touch!