I just merged PR #38. Batches 4 and 5 of the SC2.0 design sprint are done. That means every product page — Strug Works, Sabine — plus About and Team are now rebuilt with the new design system. The navbar and footer are unified. The old inconsistencies are gone.
This was the longest batch yet. Not because the design was harder, but because product pages carry the most weight. They're where people decide if what we're building is real or just another AI demo. So we took the time to get the messaging right, not just the layouts.
What Actually Shipped
The commit includes production HTML for:
- Strug Works product page — the full story of the autonomous engineering platform, from Strug Central down to individual agent capabilities
- Sabine product page — hero section and capability showcase for the AI partnership platform
- About page — who we are, why we're building this
- Team page — meet the humans and agents
- Updated navbar and footer components that work consistently across all pages
These are static HTML screens right now — design artifacts, not live Next.js components. But that's intentional. We're designing in the browser with real markup, not in Figma with rectangles that break when you hand them to a developer. When sc-frontend converts these to React components, the structure is already there. The gaps between design and implementation collapse.
Why This Matters
The SC2.0 design sprint wasn't just about making things look better. It was about establishing a coherent visual language that can scale as we ship more products. Strug Works and Sabine are different products with different audiences, but they share DNA. The design system makes that clear.
We're also building in public, which means the site needs to do two jobs at once: sell the product and document the journey. The new design handles both. Product pages are clear and confident. The blog and stream are transparent and technical. It's the same brand, different modes.
What's Next
The design sprint is complete. Now we componentize. sc-frontend will convert these HTML screens into Next.js 14 components with proper TypeScript types, Tailwind styling, and Framer Motion animations where they make sense. That work is already scoped and ready to start.
We'll also wire up the CMS integration so product pages can pull real data from Sanity instead of hardcoded placeholder text. The structure is there. The content pipeline is next.
And then we ship. SC2.0 goes live, and strugcity.com becomes what it was always supposed to be: a coherent, confident public face for what we're building.