Repository navigation
ci(docs) Revise the Workspace and MCP pages - #128
Merged
Merged
Conversation
why: A port's Workspace page showed no workspace file that its tests load and its MCP page listed no tool its server advertises, so a reader had to open the reference to see what either product does, and the pages were not named by their language. what: - Title the Workspace and MCP pages of a port by its language, for example "tmux workspace manager, forged in Rust" and "tmux MCP, built in Rust", in place of the title each had (`workspace/index.md`, `product-copy.ts`) - Open each Workspace and MCP overview with a sentence about the product that names only the verbs, formats and MCP SDK the port's own sources show, and links the port's libtmux library (`ProductIntro.astro`, `product-copy.ts`, `product-copy.json`) - Give the Workspace page a shorter title, such as "Rust-based tmux workspace manager", for the browser tab, the social tags and the agent files llms.txt and docs.json, and keep the longer title as the page's heading (`DocPage.astro`, `DocsLayout.astro`, `llms.ts`) - Say on the Workspace page that tested example workspace files are coming, as no test of the port loads one yet (`DocPage.astro`) - List the tools the server advertises on the MCP page, each as a link to its reference page with a one-line purpose from its own description (`McpShowcase.astro`, `mcp-showcase.ts`) - Group those tools as Inspect, Manage, Execute and Teardown from the toolset the server declares for each, with a tier badge on every tool, tell the reader that the toolsets setting offers only some tiers, and say in the opening sentence that the server groups its tools (`McpShowcase.astro`, `mcp-showcase.ts`, `product-copy.ts`) - Show a worked example on the MCP page: a prompt and the calls an agent makes for it, in the server's own tool names (`McpShowcase.astro`, `mcp-showcase.ts`) Shared source: libtmux/docs From: 9be37754afdeb80f043f6ef615254e0315fd2071 To: 84937633ac63297d2be2a71c7719d41109be5c63
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
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.
Pin only the shared port builder and publisher to
84937633ac63297d2be2a71c7719d41109be5c63from9be37754afdeb80f043f6ef615254e0315fd2071. All other workflow bytes, library contents, triggers, permissions and language/source/version inputs remain unchanged.Title the Workspace and MCP pages of a port by its language, for example "tmux workspace manager, forged in Rust" and "tmux MCP, built in Rust", in place of the title each had (
workspace/index.md,product-copy.ts)Open each Workspace and MCP overview with a sentence about the product that names only the verbs, formats and MCP SDK the port's own sources show, and links the port's libtmux library (
ProductIntro.astro,product-copy.ts,product-copy.json)Give the Workspace page a shorter title, such as "Rust-based tmux workspace manager", for the browser tab, the social tags and the agent files llms.txt and docs.json, and keep the longer title as the page's heading (
DocPage.astro,DocsLayout.astro,llms.ts)Say on the Workspace page that tested example workspace files are coming, as no test of the port loads one yet (
DocPage.astro)List the tools the server advertises on the MCP page, each as a link to its reference page with a one-line purpose from its own description (
McpShowcase.astro,mcp-showcase.ts)Group those tools as Inspect, Manage, Execute and Teardown from the toolset the server declares for each, with a tier badge on every tool, tell the reader that the toolsets setting offers only some tiers, and say in the opening sentence that the server groups its tools (
McpShowcase.astro,mcp-showcase.ts,product-copy.ts)Show a worked example on the MCP page: a prompt and the calls an agent makes for it, in the server's own tool names (
McpShowcase.astro,mcp-showcase.ts)A port's Workspace page showed no workspace file that its tests load and its MCP page listed no tool its server advertises, so a reader had to open the reference to see what either product does, and the pages were not named by their language.
The exact required CI and root merge receipts of the shared checkpoint must be verified before this operator runs. This PR does not claim an owner build or publication pass. Root reviews this exact caller diff, actual repository-required checks and reviews before merge; optional native estate checks are not a new universal gate.
Execution route:
controlled_real_pin_merge_push. Root separately schedules reviewed merges and exact source requests from the actual workflow state. If the current active workflow already publishes the intended source on merge, retain that actual event and do not issue a duplicate request. Future source/native/run identities will be bound to actual events.