We shipped the Strug City Sports product page this week. It's our fourth product page using the Aurora design system, and the first time we've felt confident saying: this architecture works.
The first product page is exploration. You're figuring out patterns, establishing conventions, wondering if anything you're building will ever be reusable. The second is validation — you extract a few components, feel clever about DRY principles. The third starts to reveal the edges where your abstractions break down.
The fourth is where you actually learn what you built.
What We Reused (And What That Means)
The Sports page ships with 7 sections. Three of them — BuiltOnAntiStrug, ClosingCTASection, and CarouselFrame — came straight from previous product pages with zero modification. We created 5 new components specific to the Sports product: ProductHero, CoreFeatures, AudienceSection, DesignPhilosophy, and RoadmapPreview.
That 40% reuse rate isn't impressive on its own. What matters is which components reused and which didn't. BuiltOnAntiStrug and ClosingCTASection are structural — they represent our platform positioning and conversion architecture. They should be the same across products. The hero, features, and roadmap are product-specific. They should be different.
We're reusing the right things. That took four iterations to prove.
Aurora-Cyan and Design System Maturity
Each product page gets its own aurora accent color. Sports uses aurora-cyan. The fact that we can drop in a new color variable and have the entire design system adapt — gradients, borders, glow effects, hover states — is proof the system works.
We didn't have to think about it. That's the definition of a mature design system: the decisions you don't have to make anymore.
Server Components Still Feel Like Cheating
The Sports page ships zero client JavaScript for the product marketing sections. Everything is server-rendered React Server Components. The page loads instantly, scores 100 on Lighthouse, and costs almost nothing to maintain.
We've built four product pages in six weeks. If we were still doing this with client-side React and a traditional CMS, we'd still be on page two, fighting hydration bugs and bundle size.
What's Next
The Sports Excellence Hub product is still in active development. The page we shipped this week is the marketing surface — the public promise of what we're building. Now we have to build the actual product to match it.
That's the pattern we've settled into: ship the product page first, let it define the contract, then build to the spec. It forces clarity. You can't hide behind vague roadmaps when the features are listed in production.
We'll add interactive demos and testimonials as the product matures. For now, it's an honest representation of where we are: building in public, one commit at a time, proving the architecture works by using it to build the next thing.