Skip to content

fix: remove hero tag clutter, correct core architecture description#22

Merged
enricopiovesan merged 1 commit into
mainfrom
fix/hero-clutter-and-accuracy
Jul 9, 2026
Merged

fix: remove hero tag clutter, correct core architecture description#22
enricopiovesan merged 1 commit into
mainfrom
fix/hero-clutter-and-accuracy

Conversation

@enricopiovesan

Copy link
Copy Markdown
Collaborator

Summary

  • Removed the homepage hero-meta badge row — duplicated "Apache 2.0" from the eyebrow pill directly above it and read as generic filler tags.
  • Corrected the site's core placement description, which previously implied the runtime picks a fixed deployment target ahead of time. The real model: capabilities are device-independent and run on the client by default; the client decides, heuristically, whether to delegate a subset to the server. Updated the homepage meta description + JSON-LD, the "What is Traverse?" question (body + FAQPage JSON-LD — the page most likely to feed external AI summaries), and the docs concepts page's Placement Targets section.
  • Added a link to the live GitHub Projects board to the roadmap page and footer.

Test plan

  • 0 broken internal links across all 89 pages
  • Confirmed hero-meta fully removed from build output
  • Confirmed "device-independent" framing present on homepage, what-is-traverse question, and concepts page
  • Confirmed GitHub Projects link present in footer and roadmap
  • Screenshot: homepage hero ends cleanly at the CTAs

🤖 Generated with Claude Code

- Removed the hero-meta badge row (Rust + WASM / MCP protocol / JSON
  Schema contracts / Apache 2.0) from the homepage. It duplicated
  "Apache 2.0" from the eyebrow pill directly above it and read as
  generic filler tags rather than real content.

- Corrected the site's core description of how placement actually
  works. Previous copy framed placement as a fixed target the contract
  declares and the runtime resolves ahead of time ("the same binary
  runs in your browser, on an edge node, in a cloud function... without
  modification"). The real model: capabilities are device-independent
  and run on the client by default; the client evaluates the contract
  against its own context and, based on its own heuristics, can
  delegate a subset of the capability to the server. Updated the
  homepage meta description, homepage JSON-LD, the "What is Traverse?"
  question page (both visible body and FAQPage JSON-LD -- this is the
  page most likely to feed external AI summaries), and the docs
  concepts page's Placement Targets section.

- Added a link to the live GitHub Projects board
  (github.com/orgs/traverse-framework/projects) from the roadmap page
  and the footer, so "what we're working on right now" isn't limited
  to the static roadmap snapshot.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
@enricopiovesan enricopiovesan merged commit 64cd3fd into main Jul 9, 2026
2 checks passed
@enricopiovesan enricopiovesan deleted the fix/hero-clutter-and-accuracy branch July 9, 2026 04:25
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant