Partner Overview

Partner Documentation

This section is for development partners who build and maintain sites on the DCS platform. If you're a site owner looking to manage your content, see the Portal Guide.

What is a DCS Partner?

Partners are developers, agencies, or technical teams who:

• Build websites that integrate with DCS
• Configure and onboard new sites to the platform
• Provide ongoing development and maintenance
• Support site owners with technical requests

Partner Capabilities

As a partner, you can:

Capability	Description
Onboard Sites	Add new customer sites to DCS
Configure Integration	Set up text keys, pages, and APIs
Manage Releases	Control version deployments
Access GitHub	Work directly with site repositories
View All Analytics	Cross-site analytics access

The Partner Workflow

1. Initial Site Development

Build the site using VitePress (or compatible framework) with DCS integration points:

Create Site → Add DCS SDK → Configure Text Keys → Set Up Pages

2. DCS Onboarding

Register the site with DCS:

Create Site Record → Configure Azure Resources → Set Up GitHub Secrets → Test Integration

3. Ongoing Management

Support the site through its lifecycle:

Handle Dev Requests → Review Deployments → Manage Releases → Support Site Owners

Partner Tools

DCS remote MCP server

DCS exposes a per-site, read-only Model Context Protocol (MCP) endpoint you can point a compatible MCP client at (for example the MCP Inspector or a hosted agent). It is built on the official MCP Go SDK and served over streamable HTTP.

• Endpoint: POST /api/v1/mcp/{siteSlug} — the site is the URL path and only the URL path; it is never a tool argument or session state.

• Auth: a bearer token minted by the DCS CLI. The token must carry the mcp scope (in addition to cli); a legacy cli-only token is rejected so the MCP surface is never silently enabled without re-consent.

• Per-request authorization: every request re-runs the full auth and site-resolution chain, so a client can only reach a site the token holder actually owns. Requests for a site you don't own are rejected before any tool runs.

• Owner-scoped, read-only tools: the endpoint exposes six tools, all of which read your own site's data:

  Tool	What it returns
  site_info	Site identity and configuration — name, slug, domain, description, status, enabled features (optionally with a recent analytics summary)
  analytics_summary	A recent analytics summary for the site
  list_submissions	Contact-form or resume submissions (owner-only; contains personal data)
  content_search	Search across your company's content
  recommend_blog_topics	Blog-topic suggestions drawn from high-impression, low-CTR search queries
  site_changes	Change activity — pending draft changes, version-change history, content edits, and release notes

CLI

The @duffcloudservices/cli tool handles authentication and site management from the command line (dcs login, dcs sites list, dcs init, dcs validate, dcs plans, dcs capture-snapshots).

Partner Best Practices

1. Use Consistent Text Keys

Follow the naming convention:

{page}.{section}.{element}

Good:

• home.hero.title
• about.mission.description

Avoid:

• homePageMainTitle
• text-1

2. Document Your Sites

Maintain a .github/copilot-instructions.md file that describes:

• Site architecture
• Custom components
• Development workflows
• Known limitations

3. Test Before Deploying

Always verify changes in the development environment before approving for production.

4. Communicate with Site Owners

Keep site owners informed about:

• New features being deployed
• Breaking changes
• Maintenance windows

Next Steps

• Onboarding a Site — Step-by-step site setup
• Site Configuration — Detailed configuration guide
• Site Setup Guide — Technical integration details