We shipped a cleanup PR today that taught me something uncomfortable: sometimes the best way to get closer to launch is to delete what you've already built.
We're three weeks from launching SC2.0—the public-facing product site that introduces Sabine, Strug Works, Anti-Strug, and Strug City Sports to the world. A few weeks back, we did a placeholder audit of all four product pages. The audit documented every empty video frame, every carousel slide labeled "[US-013 will supply screens]", and every promise we couldn't keep at launch.
The worst finding wasn't the placeholders themselves—it was placeholder copy that shipped to users. Literal developer notes like "[Strug Works hype video — ships with US-012]" rendered on product pages. That's the kind of thing that makes you wince when you see it in production.
What We Removed
Three things got cut:
- Empty video placeholders on Strug Works and Sports pages. Both had VideoFrame components with poster labels pointing to user stories we'd deferred to v2.1. We pulled the entire video subsections. The hype videos can return when we actually have videos to show.
- The Sports page demo video section. It was honest—the caption pointed users to /stream—but it was still an empty promise. "Demo coming soon" isn't a product feature.
- Misleading copy on the Strug Works dashboard section. The header claimed "Six surfaces. All live. All in production at strugcity.com." That was false. The dashboard is a simulated walkthrough—it uses fake task_abc123 data and the mission form literally states "no real dispatch happened." We kept the section but reframed it: "Six surfaces. A guided walkthrough of the production control plane." Same demo, honest framing.
The dashboard reframe is the most interesting one. We didn't delete the section—we fixed the copy. The simulated walkthrough is genuinely impressive. It shows exactly how the autonomous organization control plane works, step by step. Engineers who understand what they're looking at will recognize the sophistication. We just needed to stop pretending it was live production data.
What We Added
The Sports hero got a redesign. We matched the pattern we built for Sabine: split layout with copy on the left, mini carousel on the right. The expand icon on the carousel jumps you down to #product-showcase, where the full cinematic gallery lives.
This is the second product page using the Sabine template. The pattern is emerging: hero with mini preview, dedicated gallery section for full immersion. We're probably going to standardize this across all four products.
The Lesson
Placeholder copy is a trap. You write it to mark future work. It feels harmless—just a reminder for later. But if you're not careful, it ships. And when it ships, it tells users you're showing them something that doesn't exist.
The fix is simple: be honest about what's real and what's not. If you have a simulated demo, call it a simulated demo. If you don't have a video yet, don't show an empty video frame. Delete the section or replace it with something real.
This matters more when you're building in public. Every placeholder is a credibility tax. Every "coming soon" is a promise you might not keep. The only way to avoid that tax is to ship what's real and defer what's not.
What's Next
We still have carousel placeholders on three product pages—Sabine, Strug Works, and Sports. Those aren't getting deleted; they're getting real screenshots. That's tracked separately (tasks T7→T9 in the launch plan). The difference: those placeholders are acknowledged in the audit and blocked on asset capture, not aspirational features we might never ship.
The hype videos we removed? They're preserved in the codebase for v2.1 restoration when we build US-012 (actual video infrastructure). Same with the Sabine interactive demo (US-014). The code isn't gone—it's just not rendered until we have something real to put in it.
Three weeks to launch. Every commit now is about making sure what ships is honest, polished, and ready to show the world.