MCP Scope

🚀 Multi-Agent Control Platform (MCP) Documentation Project

This repository contains the documentation for the Multi-Agent Control Platform (MCP) project.

🚀 Quick Start

Deployment Documentation

✨ New Feature: Automatic Deployment via GitHub Actions ✨

The documentation now features automated deployment using GitHub Actions whenever changes are pushed to the main branch!

# Simply make changes, then commit and push
git add .
git commit -m "Update documentation"
git push

# The website will be automatically deployed - no additional commands needed

You can view the deployment progress in the GitHub Actions tab of the repository.

Local Testing

Test the website locally before pushing changes:

# Build the website locally without deployment
hugo server

# Or use the legacy build script
./deploy-docs.sh --build-only

💻 Development Workflow

1. All content changes are made on the main branch.
2. If necessary, test locally using hugo server.
3. Commit and push to main - GitHub Actions will automatically deploy.
4. View the deployed website at your GitHub Pages URL.

🔧 Deployment Architecture

This project uses a modern GitHub Actions workflow for deployment:

• main branch: Contains all source code, content, and configurations.
• GitHub Actions: Automatically build and deploy the website.
• GitHub Pages: Hosts the generated static website.

Important: Do not manually operate the deployment - all deployments are automatically handled by GitHub Actions.

📚 Documentation Structure

• content/: The main content directory, containing all source files for the documentation.
• .github/workflows/: GitHub Actions workflow configurations.
• architecture/: Architecture documentation.
• docs/: Project documentation and guides.

📦 Deployment Resources

• GitHub Actions Deployment Guide
• Deployment Verification Checklist
• Troubleshooting Guide
• GitHub Pages Deployment Solution

🤔 Need Help?

If you encounter issues with the documentation or deployment process:

1. Refer to the Troubleshooting Guide.
2. Check the GitHub Actions logs in the Actions tab of the repository.
3. If the issue persists, open an issue.