Files
homeassistant-mcp/docs/deployment.md
jango-blockchained 4fff318ea9 docs: Enhance documentation deployment and site configuration
- Update MkDocs configuration with new features and plugins
- Add deployment guide for documentation
- Restructure documentation navigation and index page
- Create GitHub Actions workflow for automatic documentation deployment
- Fix typos in site URLs and configuration
2025-02-05 21:07:39 +01:00

2.3 KiB

Deployment Guide

This documentation is automatically deployed to GitHub Pages using GitHub Actions. Here's how it works and how to manage deployments.

Automatic Deployment

The documentation is automatically deployed when changes are pushed to the main or master branch. The deployment process:

  1. Triggers on push to main/master
  2. Sets up Python environment
  3. Installs required dependencies
  4. Builds the documentation
  5. Deploys to the gh-pages branch

GitHub Actions Workflow

The deployment is handled by the workflow in .github/workflows/deploy-docs.yml:

name: Deploy MkDocs
on:
  push:
    branches:
      - main
      - master

Manual Deployment

If needed, you can deploy manually using:

# Install dependencies
pip install -r docs/requirements.txt

# Deploy to GitHub Pages
mkdocs gh-deploy --force

Best Practices

1. Documentation Updates

  • Test locally before pushing: mkdocs serve
  • Verify all links work
  • Ensure images are optimized
  • Check mobile responsiveness

2. Version Control

  • Keep documentation in sync with code versions
  • Use meaningful commit messages
  • Tag important documentation versions

3. Content Guidelines

  • Use consistent formatting
  • Keep navigation structure logical
  • Include examples where appropriate
  • Maintain up-to-date screenshots

4. Maintenance

  • Regularly review and update content
  • Check for broken links
  • Update dependencies
  • Monitor GitHub Actions logs

Troubleshooting

Common Issues

  1. Failed Deployments

    • Check GitHub Actions logs
    • Verify dependencies are up to date
    • Ensure all required files exist
  2. Broken Links

    • Run mkdocs build --strict
    • Use relative paths in markdown
    • Check case sensitivity
  3. Style Issues

    • Verify theme configuration
    • Check CSS customizations
    • Test on multiple browsers

Configuration Files

requirements.txt

Create a requirements file for documentation dependencies:

mkdocs-material
mkdocs-minify-plugin
mkdocs-git-revision-date-plugin
mkdocs-mkdocstrings
mkdocs-social-plugin
mkdocs-redirects

Monitoring