Skip to content

docs: add multi-page architecture diagram#61

Open
hugosouto wants to merge 9 commits into
Azure:mainfrom
hugosouto:main
Open

docs: add multi-page architecture diagram#61
hugosouto wants to merge 9 commits into
Azure:mainfrom
hugosouto:main

Conversation

@hugosouto

@hugosouto hugosouto commented May 19, 2026

Copy link
Copy Markdown

Adds assets/ContentFlow Diagram.drawio — a 3-page, fully editable draw.io diagram intended as a visual reference for contributors, customers, and new adopters.

# Page name Purpose
1 Overall High-level canvas: all 4 packages, runtime flow cross-cutting infrastructure, executor catalog by category, and a example pipeline
2 Project Packages Per-package breakdown — tech stack, capabilities, and dependency graph
3 Architecture & Executors Full runtime topology with Azure service icons and executor catalog by category

Adds `assets/ContentFlow Diagram.drawio` — a 3-page, fully editable draw.io diagram intended as a visual reference for contributors, customers, and new adopters.

| # | Page name | Purpose |
|---|-----------|---------|
| 1 | **Overall** | High-level canvas: all 4 packages, runtime flow  cross-cutting infrastructure, executor catalog by category, and a example pipeline |
| 2 | **Project Packages** | Per-package breakdown — tech stack, capabilities, and dependency graph |
| 3 | **Architecture & Executors** | Full runtime topology with Azure service icons and executor catalog by category |
@hugosouto

Copy link
Copy Markdown
Author

@microsoft-github-policy-service agree company="Microsoft"

hugosouto added 8 commits July 1, 2026 18:17
Adds `assets/ContentFlow Diagram.drawio` — a 3-page, fully editable draw.io diagram intended as a visual reference for contributors, customers, and new adopters.

| # | Page name | Purpose |
|---|-----------|---------|
| 1 | **Overall** | High-level canvas: all 4 packages, runtime flow  cross-cutting infrastructure, executor catalog by category, and a example pipeline |
| 2 | **Project Packages** | Per-package breakdown — tech stack, capabilities, and dependency graph |
| 3 | **Architecture** | Full runtime topology with Azure service icons |
| 4 | **Executors** | Full executor catalog by category |
…itable draw.io diagram intended as a visual reference for contributors, customers, and new adopters.

| # | Page name | Purpose |
|---|-----------|---------|
| 1 | **Overall** | High-level canvas: all 4 packages, runtime flow  cross-cutting infrastructure, executor catalog by category, and a example pipeline |
| 2 | **Components** | Per-package breakdown — tech stack, capabilities, and dependency graph |
| 3 | **Architecture** | Full runtime topology with Azure service icons |
| 4 | **Executors** | Full executor catalog by category |

Also adds diagram images.
@hugosouto

hugosouto commented Jul 1, 2026

Copy link
Copy Markdown
Author
  • Adds assets/diagram/ContentFlow Diagram.drawio — a 4-page, fully editable draw.io diagram intended as a visual reference for contributors, customers, and new adopters.
# Page name Purpose
1 Overall High-level canvas: all 4 packages, runtime flow cross-cutting infrastructure, executor catalog by category, and a example pipeline
2 Components Per-package breakdown — tech stack, capabilities, and dependency graph
3 Architecture Full runtime topology with Azure service icons
4 Executors Full executor catalog by category
  • Adds architectural overview section in README.md.
  • Adds four diagram images
  • Fixes diagram title to "ContentFlow Solution Accelerator".

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant