I led a mobile-first redesign of IAGD’s resource site for a 15,000+ person geoscience community. The work replaced inconsistent page structures with six reusable, accessible page types that are easier to navigate and maintain.
Reusable Page Types
Shared structures for recurring content
Field Trip Template
Three inconsistent formats standardized into one
Responsive System
One structure across screen sizes
Shared Interaction Rules
Across navigation, components, and content
The site was difficult
to navigate and maintain.
Dense pages, unclear navigation, and inconsistent structures made it harder for users to find resources and harder for a volunteer team to keep the site consistent.
Dense content and unclear pathways gave users no obvious place to start.
Similar pages followed different structures, so volunteers had to manage them page by page.
How I approached
the redesign.
I used research and content audits to define shared rules for navigation, page structure, accessibility, and content.
Site and competitive audits, stakeholder discovery, interviews, affinity mapping, and personas identified recurring user and content needs.
Progressive disclosure, breadcrumbs, external-link signals, and icon-plus-label patterns were built into the shared components.
Each page type was structured around what users needed to understand or do at that level.
Comparing the existing pages revealed repeated content patterns that could share one hierarchy.
The final system.
Five design outcomes show how the new structure works across page types and screen sizes.
Three resource page types using the
same structure with different content.
Navigating the nested hubs: parent
to category to resource.
Field trip archive to a standardized detail page.
Desktop view of the same page structure used on mobile.
Accordions, breadcrumbs, and labeled-link patterns
applied within the resource hierarchy.
What this project
taught me.
Defining each page type’s purpose and hierarchy before designing layouts made it easier to reuse components and keep content order consistent.
For a volunteer-run site, accessibility depends on what happens after handoff. A system that is difficult to update will become less consistent and harder to use.
Comparing legacy pages side by side exposed repeated structures and exceptions. That showed what could be standardized and what needed to stay flexible.
