12 websites.
135 fewer pages.

I redesigned 12 Texas A&M student organization websites using the university's Aggie UX design system, focusing on organizing content, reducing unnecessary pages, and making navigation easier.

Role

Part-Time Student Web Designer

Company

Texas A&M University

Division of Student Affairs,

Marketing & Communications

duration

Dec 2025 – May 2026

Tools

WordPress, Aggie UX, Photoshop, Canva, Spreadsheets

Back

Less clutter. Clearer navigation.

12

Websites redesigned & launched

47%

Fewer pages across 12 sites

135

Pages consolidated or removed

I reorganized content, combined related pages, updated outdated information, and created custom graphics to reflect each organization's identity.

The challenge: fragmented pages and outdated content

Texas A&M was transitioning student organization websites to Aggie UX, its university-wide design system built around WCAG 2.1 Level AA accessibility standards, to improve digital accessibility and consistency.

However, many websites had problems beyond their appearance. Information was scattered across numerous pages, some containing only a paragraph or a handful of links. Outdated content and inconsistent navigation made it harder for visitors to find what they needed.

FEATURED REDESIGN

Simplifying the Student Senate website

84 → 26

pages · 69% reduction

pages · 69% reduction

The Student Senate website had meeting records and committee information spread across many nested pages, making related content difficult to find. I used my content inventory to identify pages that could be combined while keeping the information organized and easy to navigate.

Two examples show how I approached these changes: consolidating archived meeting records and bringing committee information together, each with its own navigation solution.

Organizing Senate archives by session

55 → 13

archived session pages

Senate sessions previously separated agendas, minutes, legislation, voting records, and other documents into individual pages. The 73rd Senate Session alone had eight pages, many containing only links.

I grouped each session’s documents on one page under distinct headings, then added a left sidebar for switching between archived sessions.

Before

Records scattered across separate pages

After

Documents grouped under clear headings with sidebar navigation

Why this structure

Grouping documents by Senate session kept related records together, while clear headings made it easier to distinguish between document types. Sidebar navigation also let visitors move between sessions without returning to the main archive page.

Before & After: 73rd Session Page Structure

I combined related Senate records into one session page, using clear headings to organize documents and sidebar navigation to move between archived sessions.

Bringing Senate committees together on one page

9 → 1

committee pages

Each Senate committee had its own page with a short description, member information, and a photograph. Since these pages contained similar types of content, I combined them into one page with separate sections for each committee.

I added a right sidebar linking to each section, allowing visitors to browse all committees or jump directly to the one they were looking for.

Before

Nine separate committee pages

After

One page with right sidebar navigation to each committee

Why this structure

Having all committees on one page lets visitors compare their roles, while sidebar links help them find a specific committee without scrolling through the page.

Mapping page hierarchies before redesigning

I mapped each website's existing pages and navigation structure before redesigning it.

My spreadsheet inventory documented page titles and nesting, helping me identify pages with limited, outdated, or overlapping content.

I considered how closely pages were related, how much content they contained, and whether keeping them separate would make future updates easier.

This led to different decisions: consolidating the Senate's short committee profiles while keeping OPAS subcommittee pages separate because their content needs varied.

Content inventory: page titles and hierarchy informed what to keep, combine, update, or remove.

Keeping OPAS subcommittee pages separate

Fewer pages weren’t always the better solution.

For MSC OPAS, I considered combining nine subcommittee pages, as I had done for Student Senate.

Unlike the Senate committee profiles, these pages varied significantly in content length and needed room for future updates.

I kept the individual pages so each subcommittee could update its content without creating one overly long page that would be harder to navigate and maintain.

Keeping the subcommittees separate allows their content to evolve independently.

Giving each organization an identity within Aggie UX

I used custom graphics and image treatments to give organizations a recognizable visual identity within an established design system.

Aggie UX provided reusable WordPress components and a consistent university color palette. While these helped maintain consistency across websites, they also limited how much I could customize each organization's appearance.

Organizations like The Big Event and MSC Freshmen in Service and Hosting had recognizable brand colors, including green and turquoise, that weren't represented in the standard palette.

To incorporate these colors, I used Photoshop and Canva to create custom image overlays and decorative corner graphics. These details helped distinguish each organization's website while keeping the layouts and components consistent with Aggie UX.

The Big Event

MSC Freshmen in Service and Hosting

Adapting layouts to video and accessibility constraints

Some Aggie UX components offered limited layout flexibility. For example, the video component sometimes displayed videos so large that they occupied nearly the entire screen.

Because resizing options were limited, I adjusted the surrounding layouts and positioned videos where they wouldn't disrupt related content.

I also added descriptive alt text to images that lacked it on the original websites. These experiences taught me how to work within design system constraints while balancing layout flexibility, accessibility, and consistency.

Balancing stakeholder needs and user experience

I worked with organization advisors and student leaders to verify content, request photographs, and review redesigned websites before launch.

Most revisions were straightforward, but some requests required considering whether the proposed content would actually benefit visitors.

Why I recommended waiting to publish a volunteer page

Why I recommended waiting to publish a volunteer page

The 12th Can wanted to publish an external volunteer page before it had information to share, which would have left visitors with only a “coming soon” message.

After discussing the request with my manager, I recommended waiting until the organization had useful information to share rather than publishing an otherwise empty page.

What I learned

Improving a website isn’t always about adding features or changing how it looks.

Some of the most important decisions involved understanding how information was organized, deciding when to combine or separate content, and working within an existing design system.

I also gained experience collaborating with stakeholders, adapting to technical limitations, and independently redesigning and implementing websites for real student organizations.

Although I didn’t conduct formal usability testing, the project resulted in measurable changes to website structure. Given the opportunity, I would test the redesigned navigation by observing how visitors find specific information and identifying where they encounter difficulties.