
Web
Eleven Looks
A Next.js fashion storefront with a separate WordPress content site, sharing one brand and one product story.
elevenlooks.com
2
Surfaces, one brand
SSR
Indexable product pages
Self-serve
Marketing publishes alone
The challenge
Fashion retail needs two things that pull in opposite directions: a fast, tightly controlled shopping experience, and a content surface the marketing team can publish to daily without a developer. Forcing both into one system usually compromises one of them.
Our solution
We built the storefront as a full-stack Next.js application — server-rendered product and collection pages for search visibility, REST endpoints and Neon Postgres through TypeORM for catalogue and orders, Cloudinary for imagery, and Redux for cart state. Alongside it, a separate WordPress site gives the marketing team a familiar editor for campaign and editorial content, so neither side blocks the other.
The results
Shoppers get server-rendered, indexable product pages on a fast storefront, and the marketing team publishes content independently in WordPress. Both surfaces deploy separately, so a content change can never break checkout.
Client
Project type
Discipline
What we did
Related services
elevenlooks.com
Technology
What it's built on
The stack behind this build, grouped by the concern it owns.
Frontend
Backend
Content site
Data & storage
Integrations
Delivery
How it ships
Hosting, source control, and the release path from a merged branch to production.
Frontend hosting
Vercel
Backend hosting
Vercel
Source control
GitHub
Frontend hosting
Vercel
Backend hosting
Vercel
Source control
GitHub
Engineering & operations
The parts you only see from the inside
Environments, flags, tooling, and the safeguards that keep a live platform shippable.
Storefront and content site deploy independently — content cannot break checkout
Server-rendered product and collection pages for search visibility
Imagery served and transformed through Cloudinary
Gallery