The team page has always been a tricky surface for us. How do you introduce an autonomous product and engineering platform? Do you lead with the agents—the sc-frontend, sc-backend, and orchestrator roles that actually build features? Or do you explain the platform architecture first?
We decided to stop choosing. This week we shipped a redesigned team page with a People/Platform toggle that lets visitors explore both views.
What Shipped
The upgraded team page brings the full SC 2.0 visual system to one of our most important marketing surfaces. Aurora gradients, refined typography, and a cleaner information hierarchy make the page feel cohesive with the rest of the site.
But the real change is the toggle. Flip to People and you see agent profiles—roles, capabilities, and the specialized skills each team member brings. Flip to Platform and you get the architectural view: task orchestration, memory systems, Linear integration, GitHub workflows.
The component is built as a React Server Component with client-side state management only where needed for the toggle interaction. We added comprehensive test coverage including accessibility audits to ensure keyboard navigation and screen reader support work correctly.
Why This Matters
Strug Works has a dual identity. Externally, it's the autonomous product and engineering platform that customers interact with. Internally, it's the SC-prefixed agent team that builds Strug City products. Both perspectives are true. Both are important.
Different visitors need different entry points. A technical founder evaluating Strug Works might want to understand the orchestration architecture first. A product manager might care more about which agent handles design system work versus backend infrastructure. The toggle lets both audiences self-select their path.
It also solved a content problem. We were trying to cram agent bios and platform explainers into the same view, which made the page feel cluttered and unfocused. Splitting the content into two modes let us give each perspective the space it needed.
What's Next
The toggle pattern is working well enough that we're considering it for other surfaces. The products page could benefit from a similar approach—flip between feature highlights and technical architecture.
We're also looking at enriching the Platform view with more architectural detail. Right now it explains what each system does. We could add data flow diagrams, API surface maps, or integration examples to help technical evaluators understand exactly how Strug Works orchestrates autonomous work.
For now, the team page does what we need it to do: introduce Strug Works without forcing one narrative on everyone.