When I took over the strategy for the AWS Architecture Center, it was fairly disconnected experience that was hard to navigate. It collected a lot of reference architectures, best practices, diagrams, and whitepapers — but these were organized in a way that made discovery difficult, especially for users who weren’t already well‑versed in AWS. It lacked a strong domain structure, so finding architecture guidance for a specific area (say, security or big data) could be tedious.
In the redesign, I reorganized the content around core architecture domains like Security, Compute, Analytics, and more, mirroring how real-world architectures are built and how architects think. Within each domain, I surfaced featured content — reference designs, prescriptive patterns, and curated guidance — so that the most relevant, expert‑recommended architecture materials are front and center.
I also built in user feedback mechanisms, giving visitors the ability to vote on proposed guidance, request new content, and suggest missing architecture patterns. This makes the site more interactive and customer-driven.
By aggregating content in one place — from AWS whitepapers, reference diagrams, and blog content — the redesigned Architecture Center functions as a true one-stop shop for architects.
The result is a more intuitive, domain-led experience that significantly reduces the friction for discovery. Users can now find best practices and reference architectures in a way that maps to their own architectural challenges, rather than having to wade through general documentation. This redesign helps both beginners and experienced architects make better decisions faster, and gives AWS a clearer way to evolve its guidance based on user feedback.
