The story in 30s
The problem. Before this project, theme customization relied heavily on predefined layouts. This limited flexibility for merchants, slowed iteration, and made it difficult to scale across industries: high dependency on predefined themes, slow theme creation and adaptation, and difficulty maintaining consistency at scale.
What I did. I designed a modular theme system composed of configurable, reusable sections, hero, product grids, navigation, footer, and a visual editor that let merchants assemble and customize stores without code, while preserving system rules. Decisions were informed by competitive analysis, qualitative customer insights, and Baymard Institute UX guidelines.
What changed. The MVP launched and was validated through pilots with two retail brands, on a foundation built to scale to 2,000+ stores across multiple sectors from day one.
The thinking: four rules that scale
The real risk wasn't any single screen, it was building system design instead of screen design. Four principles guided every decision:
- → Modularity. Pages built from reusable, interchangeable sections.
- → Constraints by default. Limiting options to prevent broken layouts.
- → Predictability. Components behaving consistently across contexts.
- → Progressive control. Exposing customization gradually, not all at once.
Solution overview
A modular theme system, applied directly against the constraints above:
- → 14 section types merchants could combine and reconfigure without touching code.
- → 80+ configuration properties exposed progressively, not all at once.
- → 6 theme presets giving merchants a fast starting point before customizing further.
- → A visual editor that preserved system rules, so customization couldn't break a layout.
Theme examples
Results
- → MVP validated through pilots with two retail brands
- → Built on a foundation designed to scale to 2,000+ stores across multiple sectors
- → Meaningfully more layout flexibility than the previous static-template approach
Reflection
- 1 The real impact came from the rules, not the screens. Defining components and constraints that could scale with the business mattered more than individual screen decisions.
- 2 System-level design compounds in a platform meant to serve thousands of merchants with different needs, one consistent set of rules scales in a way that one-off screen decisions never could.