# Deployment Architecture

This diagram shows the deployed runtime and operational topology for the Kell Creations platform documentation, automation, and connected business services.

## Purpose

This view explains how the Windows authoring workstation, Forgejo source control, Forgejo runners, Ubuntu documentation host, PlantUML server, docs publishing service, and connected external platforms work together in the live environment.

## Diagram Source

The source for this diagram is maintained as architecture code in:

`architecture/workspace/deployment-architecture.puml`

## Diagram

![Deployment Architecture](../../images/deployment-architecture.svg)

## Included Deployment Nodes

- Windows 11 Workstation
- `git.kellsupport.com` Forgejo Server
- `kellsupport.com` Ubuntu 24.04.4 LTS documentation host
- Docker host and documentation support containers
- External business platforms and publishing targets

## Included Runtime Elements

- VS Code
- Local Git Working Copy
- Forgejo
- Forgejo Runner - Docker
- Forgejo Runner - Docs Host
- MkDocs Build Process
- PlantUML Server
- Docs Web Service
- Published Site Directory
- WordPress / WooCommerce
- Mail Server
- n8n
- Facebook
- Instagram
- X

## Notes

This deployment view establishes the runtime topology for authoring, validation, publishing, diagram rendering, and live documentation delivery across the Kell Creations platform. Future refinements should distinguish between internal-only services, externally published endpoints, reverse-proxy routing, and operational resilience considerations for the production environment.