Website Production Management
My role: Source of truth for a large-scale website redesign & rebrand. Annotated, interactive, and ready for implementation.
/* Consultant*/
Desktop hover states for card components.
Desktop hover states for card components.
Building a website for a content management approach requires a very different production strategy than designing individual pages.
On our large team of engineers, designers, PMs, QA, and content strategists, it became clear that even though we had a design language and were working with a visual system—we designers were not delivering the components with consistent precision across the dozens of use-cases we were outputting.
Building a website for a content management approach requires a very different production strategy than designing individual pages.
On our large team of engineers, designers, PMs, QA, and content strategists, it became clear that even though we had a design language and were working with a visual system—we designers were not delivering the components with consistent precision across the dozens of use-cases we were outputting.
Building a website for a content management approach requires a very different production strategy than designing individual pages.
On our large team of engineers, designers, PMs, QA, and content strategists, it became clear that even though we had a design language and were working with a visual system—we designers were not delivering the components with consistent precision across the dozens of use-cases we were outputting.
Building a website for a content management approach requires a very different production strategy than designing individual pages.
On our large team of engineers, designers, PMs, QA, and content strategists, it became clear that even though we had a design language and were working with a visual system—we designers were not delivering the components with consistent precision across the dozens of use-cases we were outputting.
And neither were the engineers!
And neither were the engineers!
And neither were the engineers!
And neither were the engineers!
Since the design comps were not articulating the system, the engineers were not building systematically. Each individual was building components as they came across them, referencing design comps that were imperfect in different ways. This caused myriad issues as we realized our global rules, styles and methodology were not making it into the build.
With my experience designing for CMS-based websites, I was able to identify this issue and I knew how to fix it. I set about creating a single source of truth where collaborators could reference intentional and systematized designs with confidence. A component kit was born; and our team was able to share a common vocabulary for the building blocks, categories, and patterns needed to build out a very complex redesign.
Since the design comps were not articulating the system, the engineers were not building systematically. Each individual was building components as they came across them, referencing design comps that were imperfect in different ways. This caused myriad issues as we realized our global rules, styles and methodology were not making it into the build.
With my experience designing for CMS-based websites, I was able to identify this issue and I knew how to fix it. I set about creating a single source of truth where collaborators could reference intentional and systematized designs with confidence. A component kit was born; and our team was able to share a common vocabulary for the building blocks, categories, and patterns needed to build out a very complex redesign.
Since the design comps were not articulating the system, the engineers were not building systematically. Each individual was building components as they came across them, referencing design comps that were imperfect in different ways. This caused myriad issues as we realized our global rules, styles and methodology were not making it into the build.
With my experience designing for CMS-based websites, I was able to identify this issue and I knew how to fix it. I set about creating a single source of truth where collaborators could reference intentional and systematized designs with confidence. A component kit was born; and our team was able to share a common vocabulary for the building blocks, categories, and patterns needed to build out a very complex redesign.
Since the design comps were not articulating the system, the engineers were not building systematically. Each individual was building components as they came across them, referencing design comps that were imperfect in different ways. This caused myriad issues as we realized our global rules, styles and methodology were not making it into the build.
With my experience designing for CMS-based websites, I was able to identify this issue and I knew how to fix it. I set about creating a single source of truth where collaborators could reference intentional and systematized designs with confidence. A component kit was born; and our team was able to share a common vocabulary for the building blocks, categories, and patterns needed to build out a very complex redesign.
How to make a component kit:
Animation and motion elements included as well.
View more projects
Stitch House BreweryRestaurant branding
Girard & FaireRetail Identity
PreclearanceAnimated Video
TennCare ConnectHealth Benefits Mobile App
Corporate IntranetEnterprise Web Tool Redesign
TabithaProgressive Web App
Tech FluencyMobile Game
Connected VoicesiOS App & Data Visualization
Bag heroFeature Flow
World Wildlife FundiPad App
Funk ParadeHybrid Mobile App
Fly DeltaNative Mobile App
National Geographic MagazineEditorial
Copyright 2022 all rights reserved
Visit my cargo site
Washington, D.C.
Copyright 2020 all rights reserved
Visit my cargo site