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 MCP Server

The DCS Model Context Protocol (MCP) server provides AI-powered tooling for partners:

• list_pending_changes — View uncommitted text overrides
• suggest_content_improvements — Get AI recommendations
• preview_release_impact — Assess deployment impact
• generate_release_notes — Auto-generate changelogs

CLI Tools

Command-line utilities for common tasks:

# Sync blog content
pnpm run blog:sync --site=my-site

# Health check
pnpm run cms:health

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