docs: Simplify documentation site configuration and deployment

- Streamline MkDocs navigation structure
- Reduce complexity in GitHub Actions documentation workflow
- Update documentation dependencies and requirements
- Simplify site name and deployment configuration

.github/workflows/deploy-docs.yml

@@ -1,38 +1,26 @@
-name: Deploy MkDocs
+name: Deploy Documentation
 on:
   push:
     branches:
-      - main  # or master, depending on your default branch
-  workflow_dispatch:
-
-permissions:
-  contents: write
+      - main
+    paths:
+      - 'docs/**'
+      - 'mkdocs.yml'
 
 jobs:
   deploy:
     runs-on: ubuntu-latest
+    permissions:
+      contents: write
     steps:
       - uses: actions/checkout@v4
       - uses: actions/setup-python@v5
         with:
           python-version: '3.x'
-      - name: Install dependencies
-        run: |
-          pip install mkdocs-material
-          pip install mkdocs-git-revision-date-localized-plugin
-          pip install mkdocstrings[python]
-      - name: Configure Git
+          cache: 'pip'
+      - run: pip install -r docs/requirements.txt
+      - name: Deploy Documentation
         run: |
           git config --global user.name "github-actions[bot]"
           git config --global user.email "github-actions[bot]@users.noreply.github.com"
-      - name: Build docs
-        run: mkdocs build
-      - name: Deploy to GitHub Pages
-        run: |
-          git checkout --orphan gh-pages
-          git rm -rf .
-          mv site/* .
-          rm -rf site
-          git add .
-          git commit -m "docs: Update documentation"
-          git push origin gh-pages --force 
+          mkdocs gh-deploy --force 

.github/workflows/docs-deploy.yml

@@ -1,32 +0,0 @@
-name: Deploy Documentation
-
-on:
-  push:
-    branches:
-      - main
-    paths:
-      - 'docs/**'
-      - 'mkdocs.yml'
-
-permissions:
-  contents: write
-
-jobs:
-  deploy-docs:
-    runs-on: ubuntu-latest
-    steps:
-      - name: Checkout repository
-        uses: actions/checkout@v4
-
-      - name: Set up Python
-        uses: actions/setup-python@v4
-        with:
-          python-version: 3.x
-
-      - name: Install dependencies
-        run: |
-          pip install mkdocs-material
-          pip install mkdocs
-
-      - name: Deploy documentation
-        run: mkdocs gh-deploy --force 

docs/api/index.md

@@ -232,3 +232,11 @@ The current API version is v1. Include the version in the URL:
 - [Core Functions](core.md) - Detailed endpoint documentation
 - [Architecture Overview](../architecture.md) - System design details
 - [Troubleshooting](../troubleshooting.md) - Common issues and solutions
+
+# API Reference
+
+The Advanced Home Assistant MCP provides several APIs for integration and automation:
+
+- [Core API](core-api.md) - Primary interface for system control
+- [SSE API](sse.md) - Server-Sent Events for real-time updates
+- [Core Functions](core.md) - Essential system functions 

docs/deployment.md

@@ -0,0 +1,141 @@
+# 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`. This is the single source of truth for documentation deployment:
+
+```yaml
+name: Deploy MkDocs
+on:
+  push:
+    branches:
+      - main
+      - master
+  workflow_dispatch:  # Allow manual trigger
+```
+
+## Manual Deployment
+
+If needed, you can deploy manually using:
+
+```bash
+# Create a virtual environment
+python -m venv venv
+
+# Activate the virtual environment
+source venv/bin/activate
+
+# Install dependencies
+pip install -r docs/requirements.txt
+
+# Build the documentation
+mkdocs build
+
+# 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:
+
+```txt
+mkdocs-material
+mkdocs-minify-plugin
+mkdocs-git-revision-date-plugin
+mkdocs-mkdocstrings
+mkdocs-social-plugin
+mkdocs-redirects
+```
+
+## Monitoring
+
+- Check [GitHub Pages settings](https://github.com/jango-blockchained/advanced-homeassistant-mcp/settings/pages)
+- Monitor build status in Actions tab
+- Verify site accessibility 
+
+## Workflow Features
+
+### Caching
+The workflow implements caching for Python dependencies to speed up deployments:
+- Pip cache for Python packages
+- MkDocs dependencies cache
+
+### Deployment Checks
+Several checks are performed during deployment:
+1. Link validation with `mkdocs build --strict`
+2. Build verification
+3. Post-deployment site accessibility check
+
+### Manual Triggers
+You can manually trigger deployments using the "workflow_dispatch" event in GitHub Actions.
+
+## Cleanup
+
+To clean up duplicate workflow files, run:
+
+```bash
+# Make the script executable
+chmod +x scripts/cleanup-workflows.sh
+
+# Run the cleanup script
+./scripts/cleanup-workflows.sh
+``` 

docs/getting-started/index.md

@@ -0,0 +1,8 @@
+# Getting Started
+
+Welcome to the Advanced Home Assistant MCP getting started guide. Follow these steps to begin:
+
+1. [Installation](installation.md)
+2. [Configuration](configuration.md)
+3. [Docker Setup](docker.md)
+4. [Quick Start](quickstart.md) 

docs/index.md

@@ -4,9 +4,18 @@ title: Home
 nav_order: 1
 ---
 
-# 🏠 MCP Server for Home Assistant
+# Advanced Home Assistant MCP
 
-Welcome to the Model Context Protocol (MCP) Server documentation! This guide will help you get started with integrating a lightweight automation tool with your Home Assistant setup.
+Welcome to the Advanced Home Assistant Master Control Program documentation.
+
+This documentation provides comprehensive information about setting up, configuring, and using the Advanced Home Assistant MCP system.
+
+## Quick Links
+
+- [Getting Started](getting-started/index.md)
+- [API Reference](api/index.md)
+- [Configuration Guide](getting-started/configuration.md)
+- [Docker Setup](getting-started/docker.md)
 
 ## What is MCP Server?
 

docs/requirements.txt

@@ -0,0 +1,11 @@
+mkdocs>=1.5.0
+mkdocs-material>=9.0.0
+mkdocs-minify-plugin>=0.7.1
+mkdocs-git-revision-date-plugin>=0.3.2
+mkdocs-mkdocstrings>=0.24.0
+mkdocs-social-plugin>=0.1.1
+mkdocs-redirects>=1.2.1
+mkdocs-glightbox>=0.3.4
+pillow>=10.0.0
+cairosvg>=2.7.0
+pymdown-extensions>=10.0 

mkdocs.yml

@@ -1,6 +1,6 @@
-site_name: Advanced Home Assistant MCP
-site_url: https://jango-blockchained.github.io/advanced-homeassitant-mcp
-repo_url: https://github.com/jango-blockchained/advanced-homeassitant-mcp
+site_name: Project Documentation
+site_url: https://jango-blockchained.github.io/advanced-homeassistant-mcp
+repo_url: https://github.com/jango-blockchained/advanced-homeassistant-mcp
 
 theme:
   name: material
@@ -28,6 +28,9 @@ theme:
     - search.suggest
     - search.highlight
     - content.code.copy
+    - content.tabs.link
+    - content.tooltips
+    - toc.integrate
 
 markdown_extensions:
   - pymdownx.highlight:
@@ -39,36 +42,31 @@ markdown_extensions:
   - pymdownx.details
   - attr_list
   - md_in_html
+  - pymdownx.emoji
+  - pymdownx.tasklist
+  - footnotes
+  - tables
 
 plugins:
   - search
-  - git-revision-date-localized:
-      type: date
+  - minify:
+      minify_html: true
+  - git-revision-date-plugin
   - mkdocstrings:
       default_handler: python
-      handlers:
-        python:
-          options:
-            show_source: true
+  - social
+  - tags
+  - redirects
+  - gh-deploy
 
 nav:
   - Home: index.md
+  - Getting Started: getting-started.md
+  - API Reference: api.md
   - Usage: usage.md
-  - API: api.md
   - Configuration:
     - Claude Desktop Config: claude_desktop_config.md
-    - Cline Config: cline_config.md
-  - Getting Started:
-    - Overview: getting-started.md
-    - Installation: getting-started/installation.md
-    - Configuration: getting-started/configuration.md
-    - Docker Setup: getting-started/docker.md
-    - Quick Start: getting-started/quickstart.md
-  - API Reference:
-    - Overview: api/index.md
-    - Core API: api.md
-    - SSE API: api/sse.md
-    - Core Functions: api/core.md
+    - Client Config: client_config.md
   - Tools:
     - Overview: tools/tools.md
     - Device Management:
@@ -94,6 +92,7 @@ nav:
     - Interfaces: development/interfaces.md
     - Tool Development: development/tools.md
     - Testing Guide: testing.md
+    - Deployment Guide: deployment.md
   - Architecture: architecture.md
   - Contributing: contributing.md
   - Troubleshooting: troubleshooting.md