feat: content restructure phase 2 — remove Solutions/Use-cases, honest sitewide language#35
Merged
Merged
Conversation
…s, fix AI-pipeline overclaim sitewide Phase 2 of the content restructure (follows #34). Delete /solutions/* (fintech, saas, ecommerce, enterprise, ai-companies) and /use-cases — five generic industry-vertical marketing pages for a solo-maintained 0.x project, replaced by the honest /platforms page from phase 1. Every inbound link (Nav, Footer, two blog CTAs, a quickstart card) repointed to /platforms or /system instead. Docs sidebar gains two sections that reuse existing content instead of forking a duplicate copy: "Governance Model" deep-links to the Spec-Driven Development section already on /docs/concepts (now anchored), and "Embed Traverse" deep-links to the five platform rows on /platforms (now anchored per-platform: rust-embedding, browser, swift-ios, kotlin-android, dotnet-winui). /roadmap gets the fourth status this project actually has: a Shipped / Next / Blocked / Exploring legend under the hero, a new "Blocked" phase between "Shipping now" and "Next" surfacing the Swift/iOS certification blocker explicitly (previously invisible on this page), and a fifth principle summarizing the ten explicit v1.0 milestone gates with a link to the source doc. Also fixes a stale "9 governing specs" claim to the real 73. Sitewide fix: "browser, edge, cloud, and AI pipelines" is repeated across the homepage hero/features/stats, about, two compare pages, and five /questions pages as if all four were real, current placement targets. They aren't — native and browser are shipped, edge is planned-not-started, cloud is an explicit v0.1 non-goal, and "AI pipeline" isn't a placement target at all (it's how an agent already reaches the native or browser target over MCP). Corrected every present-tense capability claim to match /platforms; left blog posts alone as dated artifacts and left compare-page problem-framing narratives alone since those describe motivating scenarios, not shipped capability. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
3 tasks
enricopiovesan
added a commit
that referenced
this pull request
Jul 21, 2026
…est examples (#36) Follow-up to the content restructure (#34, #35), which only touched one overclaiming table row per compare page. A full pass turned up more: Fabricated code samples: all three pages had "integration" code importing a package that has never existed (@traverse-framework/runtime) with an invented TraverseRuntime.init()/.execute() API. A developer copying any of these would hit a wall immediately. - vs-function-calling: the "using them together via MCP" section invented a hand-rolled MCP tool wrapper. The real story is simpler and better — traverse-mcp -- stdio already exposes every governed capability as an MCP tool, no wrapper code needed. Replaced with the real invocation and a link to /agents.html. Also fixed an example contract's placement array, which listed ai-pipeline as a valid value. - vs-microservices: replaced the fake Rust sample with the real traverse-embedder crate API (BundleEmbedder::init, .submit, .subscribe). - vs-serverless: the sample was a Cloudflare Worker, i.e. edge — a placement Traverse hasn't shipped. Reframed as a Rust AWS Lambda handler using the same real traverse-embedder crate, which sidesteps the unverified edge-WASM question entirely by being a real, ordinary Rust process. Malformed HTML: all three pages' CTA bands had a stray </section> landing mid-block (evidently copy-pasted), closing the section early and leaving the button row and final closing tags orphaned outside it. Browsers silently recover from this, but it's invalid structure that happened to look fine by accident. Fixed the tag order in all three so the section actually closes where the markup says it does. Co-authored-by: Claude Fable 5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Phase 2 of the content restructure (follows #34). Removes the pages that were actively hurting credibility and fixes a factual overclaim that turned out to be repeated across the whole site.
Delete Solutions/Use-cases
/solutions/*(fintech, saas, ecommerce, enterprise, ai-companies) and/use-cases— five generic industry-vertical marketing pages for a solo-maintained 0.x open-source project — are gone, replaced by/platformsfrom phase 1. Every inbound link (Nav dropdown, Footer, two blog CTAs, a quickstart card) is repointed to/platformsor/system, not left dangling.Docs sidebar wired to real content, not a fork
Two new sections, both deep-linking into content that already exists rather than duplicating it:
/docs/concepts.html#spec-driven-development(added an anchor to the existing section)/platforms(#rust-embedding,#browser,#swift-ios,#kotlin-android,#dotnet-winui)/roadmapgets its fourth statusAdded the Shipped/Next/Blocked/Exploring legend under the hero, a new Blocked phase between "Shipping now" and "Next" that surfaces the Swift/iOS certification blocker explicitly (it existed nowhere on this page before), and a fifth principle summarizing the real ten v1.0 milestone gates with a link to the source doc. Also fixed a stale "9 governing specs" claim to the real 73.
Sitewide: the "browser, edge, cloud, and AI pipelines" overclaim
This exact phrase, or a close variant, was repeated as a present-tense capability claim across the homepage (hero, a feature card, a stat card),
/about, both compare pages, and five/questionspages. It isn't accurate: native and browser are shipped, edge is planned-but-unstarted, cloud is an explicit v0.1 non-goal per the constitution (not a "coming soon"), and "AI pipeline" isn't a placement target at all — it's how an agent already reaches the native or browser target over MCP. Corrected every instance to match what/platformsnow honestly states. Left blog posts alone as dated artifacts, and left compare-page problem-framing narratives alone (those describe a motivating scenario, not a claim that Traverse does it today).Test plan
npm run build— 86 pages (93 − 7 deleted), cleandist/output has zero stray escape artifacts and every new/platformslink renders as a real<a href>, not literal text🤖 Generated with Claude Code