A fashion storefront built for browsing, not just buying.
A fashion storefront built for browsing, not just buying.
Zumers is a clothing storefront — tees, hoodies, knitwear, outerwear, organized into seasonal drops and everyday collections rather than a flat product grid. The build needed a full commerce stack underneath a browsing experience that doesn't feel like a spreadsheet with photos.
The build.
Stack: Next.js on the frontend, Payload CMS managing the product catalog and content, GSAP driving the motion layer. A working cart and checkout flow underneath — full e-commerce, not a catalog-only site with a "contact us to buy" fallback. Catalog structure: products organized two ways simultaneously — by category (tees, hoodies, bottoms, knitwear, outerwear, women's) and by curated collection (seasonal drops, "essentials," a numbered "Chapter" series). The same product can live in a category listing and a themed collection without duplicating data — that's a Payload/CMS structuring decision, not just a frontend display trick. Product presentation: each product card carries a hover-state second image — the piece flat, then the piece styled or shown from another angle. Small detail, but it's the difference between a catalog that feels static and one that invites a second look before the click.
Motion.
GSAP handles the transitions that make scrolling through drops feel considered rather than instant — section reveals, hover states on product cards, movement that responds to scroll position rather than firing once on page load.
Commerce.
A working cart and checkout — the part of an e-commerce build that's invisible when it works and is the entire point of the site when it doesn't. Real transactions, not a mockup of one.
SEO.
Search fundamentals set up from launch — metadata, structured product data, image optimization through Next.js's built-in image pipeline rather than raw unoptimized assets.
What made this one different.
Most storefront builds either lean fully into a no-code platform (Shopify, Tilda) for speed, or go fully custom and lose the content-management ease that a store owner actually needs day to day. This one keeps both: Payload gives non-technical catalog management, Next.js and GSAP give the custom motion and performance a template platform wouldn't allow.
