Redesigning cas.org

The problem

The migration moved cas.org onto Webflow Enterprise. It did not change what the site was like to use. People inside CAS had their own views on what was not working for customers, but those views were scattered across teams and conversations, not collected anywhere a redesign could act on them.

The research

I went to internal stakeholders and gathered their ideas and observations about what was not working. Then I broke that research down into a clear list of what should change, why, and how each change would serve customers better.

That list is what the design work answers to.

The process

Page layouts are prototyped in Claude Design and Figma first. That is where the arguments happen and the decisions get made, while changes are still cheap.

Once a layout is approved, I build it in Webflow through MCP. Building against settled decisions keeps the Webflow work about execution instead of rework.

Systems thinking

The redesign is built as a set of components, not a set of pages. Each one has to earn its place: meaningful, accessible, performant, and reusable across the site.

The test is how the site holds up in three years. On a site this size, a one-off section becomes a maintenance cost the moment it ships. A good component lets the next page come together faster, and lets the next person pick up the work without reverse-engineering it.

Status

The redesign is in progress. No results to report yet, and I won't claim any until there are some.