arlenness.com
This project was a complete build. A move from aspDotnet to a more stable / optimized content management system. Starting with the store, my team began to fine tune and refine our product's descriptions, imagery, and up sell features. New functionality, UX and UI were all introduced.
Overview
My team started with condensing, organizing, re-writing and re-imaging over 4000 product SKU's. From there, a (B2B) "Dealer Toolbar" was introduced in order to give our dealers and distributors an online space to access account history, top seller lists, specials, and all brand standard marketing materials (Ad's, Press Releases, Logos..ect).
Impact at a Glance
Process
Problem
Teams frequently chose an over-powered multi-select component even when it was unnecessary, leading to friction, inconsistency, and code sprawl across the platform.
- Multiple inconsistent implementations
- Overuse of complex multi-select patterns
- Lack of clear usage guidance
- Code duplication and maintenance burden
Approach
A systematic methodology to unify patterns and create a scalable framework that teams could easily adopt and implement consistently.
- Audit legacy prompt implementations across repos
- Define atomic → compound variant taxonomy
- Tokenize interaction + visual states
- Ship docs, decision trees, and examples
Project Gallery
