How to add a page to the tdmcp VitePress docs site so it builds, gets a clean URL, and lands in the right nav — including the repo's partial-translation convention (only the artist guide is EN+PT; reference/legal pages are English). Use when authoring the privacy policy or any new docs page for tdmcp.
The English summary is being prepared. Showing the original description.
Run score Not tested
See how to installReview the instructions the agent will receive before you install.
The site lives under docs/, config in docs/.vitepress/config.ts
(base: "/tdmcp/", cleanUrls: true, deployed to
https://pantani.github.io/tdmcp/).
Only the artist guide track is translated (EN + PT-BR). Everything else is English-only. The config encodes three nav groups:
artistGuide(base) / artistGuidePt → docs/guide/*.md and
docs/pt/guide/*.md. This is the only mirrored track.devReference → docs/reference/*.md (English only).operations → standalone pages like docs/DEPLOYMENT.md, docs/ROADMAP.md
(English only), plus external GitHub links.So a privacy / legal page is NOT an artist-guide page. It belongs as a standalone page, English as the canonical version (legal text is fine in EN; the form needs exactly one privacy URL). Add a PT mirror only if the spec asks — do not force it just because the guide is bilingual.
docs/privacy.md → clean URL https://pantani.github.io/tdmcp/privacy.title: (used by transformHead) and consider
aside: false for a legal page.operations array in config.ts:
{ text: "Privacy", link: "/privacy" }. (It's the legal/ops group, not the
artist sidebar.) Put it near the end, before/after Changelog.docs/pt/privacy.md + a { text: "Privacidade", link: "/pt/privacy" } entry in the PT-side nav config.The site uses
cleanUrls, so link to/privacy, never/privacy.html. For a page that needs a non-default URL (like DEPLOYMENT→deployment) you'd add arewritesentry — a lowercaseprivacy.mdneeds none.
.md file exists at the path whose URL you put in the nav.link matches the clean URL (no .md, no .html).npm run docs:build passes — VitePress fails the build on dead internal
links, so a typo'd nav link or a broken in-page link is caught here. This is
the gate; always run it after adding a page.localhost, 127.0.0.1) in prose are ignored by the dead-link
checker (see ignoreDeadLinks), so you can mention the bridge address freely.Match the existing docs voice — pull product framing from docs/index.md and
docs/guide/what-is-tdmcp.md rather than inventing new copy. Keep legal pages
plain and direct; artists are the audience, so avoid dense legalese.
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Write operator-facing and public documentation plans for AI-Controlled Party mixer/Soundcraft Ui24R scene arming. Use for runbooks, rehearsal checklists, show-day checklists, EN/PT docs updates, demo scripts, safety wording, and follow-up documentation revisions.
The English summary is being prepared. Showing the original description.
Authoritative reference for submitting tdmcp to the Anthropic Connectors Directory as a Codex Desktop Extension (MCPB). Use whenever drafting, checking, or fixing the submission — it defines the two submission paths, why tdmcp is a Desktop Extension (never a remote connector), every form field, the rejection-causing gates, and the local-only compliance story. Read this before writing any submission deliverable.
The English summary is being prepared. Showing the original description.
Authoritative reference for submitting tdmcp to the Anthropic Connectors Directory as a Claude Desktop Extension (MCPB). Use whenever drafting, checking, or fixing the submission — it defines the two submission paths, why tdmcp is a Desktop Extension (never a remote connector), every form field, the rejection-causing gates, and the local-only compliance story. Read this before writing any submission deliverable.
The English summary is being prepared. Showing the original description.
How to migrate the tdmcp Claude Desktop bundle from legacy .dxt to .mcpb (MCP Bundle) and keep it building — covers the manifest schema (verify against the installed packer, never hardcode), the build-mcpb.mjs packer/zip-fallback flow, the npm scripts, and the full .dxt→.mcpb reference sweep across docs and scripts. Use when packaging or migrating the tdmcp desktop bundle.
The English summary is being prepared. Showing the original description.
How to migrate the tdmcp Codex Desktop bundle from legacy .dxt to .mcpb (MCP Bundle) and keep it building — covers the manifest schema (verify against the installed packer, never hardcode), the build-mcpb.mjs packer/zip-fallback flow, the npm scripts, and the full .dxt→.mcpb reference sweep across docs and scripts. Use when packaging or migrating the tdmcp desktop bundle.
The English summary is being prepared. Showing the original description.
Review, harden, and test the safety policy for AI-Controlled Party mixer/Soundcraft Ui24R scene arming. Use for approval gates, blocked mixer operations, hazardous request handling, venue validation, bypass attempts, QA, risk review, or follow-up safety changes.
The English summary is being prepared. Showing the original description.