feat(homepage): reposition around MCP / AI gateway wedge#9
Closed
feat(homepage): reposition around MCP / AI gateway wedge#9
Conversation
Lead the homepage with the MCP + AI gateway story. Spec-first becomes the "how" in the second fold, not the primary pitch. - Hero: "Turn any OpenAPI spec into an MCP tool server" - Update title tag, default meta description, and badge (MCP native) - Primary CTA now jumps to the new MCP quickstart section - New "Your OpenAPI becomes an MCP server" section with an OAS example showing root-level enable plus per-operation opt-out, three short explainers on tool discovery, middleware pass-through, and opt-out - New "AI governance, built in" section with four cards: prompt guard, token limits, cost tracking, response guard - Feature grid header reframed to "One gateway for your APIs and your agents"; MCP card promoted from position 15 to position 1 Technical copy verified against docs.barbacane.dev/guide/mcp.html: opt-out semantics, JSON-RPC 2.0 endpoint at /__barbacane/mcp, tool name from operationId, input/output schemas merged from parameters and responses, full middleware pipeline on tool calls. Note: AI governance claims depend on gateway PR #67 landing. This branch should not be deployed to production until #67 is merged and released.
9 tasks
Contributor
Author
|
Superseded by #10, which contains the same homepage repositioning plus /mcp/, /platform/, audience-oriented nav, and the AI cards in the homepage feature grid. Closing to avoid duplicate review. |
4 tasks
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
Leads the homepage with the MCP + AI gateway story instead of spec-first-as-product. Contract-first becomes the "how" in the second fold. Implements §1 of the website-lift plan driven by the strategic audit (Audit §6.2 #3 and §9 Phase 1).
Technical copy cross-checked against docs.barbacane.dev/guide/mcp.html: opt-out semantics, JSON-RPC 2.0 endpoint at
/__barbacane/mcp, tool name fromoperationId, input and output schemas merged from parameters and responses, full middleware pipeline on tool calls.Deploy coupling
The AI governance section and the corresponding line in the hero sub-copy claim features from gateway PR #67, which is still open. Do not deploy this branch to production until PR #67 is merged and released, otherwise the homepage overclaims. This is the deliberate launch-coordination strategy from Audit Phase 1.
Test plan
npm run buildpasses locally (verified: 12 pages built, no errors)npm run dev: hero, MCP quickstart, AI governance section, reordered feature grid#mcp-quickstartanchor jumps to the right section