Documentation Reorganization (v2.0)

Multi-platform structure for Cromwell + TES deployment

The documentation has been reorganized into a cloud-agnostic core with platform-specific implementations.


πŸ“‚ New Directory Structure

/
β”œβ”€β”€ index.md                              ← Root: Cromwell + TES on Kubernetes (any cloud)
β”œβ”€β”€ quick-reference.md                    ← All platforms
β”œβ”€β”€ _config.yml, .nojekyll               ← Jekyll config
β”‚
β”œβ”€β”€ /tes                                  ← Platform-agnostic TES section
β”‚   β”œβ”€β”€ index.md                          (overview)
β”‚   β”œβ”€β”€ architecture.md                   (design patterns, DaemonSet)
β”‚   β”œβ”€β”€ container-images.md               (custom builds, dependencies)
β”‚   β”œβ”€β”€ configuration.md                  (runtime options - TEMPLATE)
β”‚   └── troubleshooting.md                (common issues - TEMPLATE)
β”‚
β”œβ”€β”€ /cromwell                             ← Platform-agnostic Cromwell section
β”‚   β”œβ”€β”€ index.md                          (overview)
β”‚   β”œβ”€β”€ configuration.md                  (backends, options - TEMPLATE)
β”‚   β”œβ”€β”€ workflows.md                      (submission, monitoring - TEMPLATE)
β”‚   β”œβ”€β”€ tes-integration.md                (Cromwell-TES communication - TEMPLATE)
β”‚   └── troubleshooting.md                (common issues - TEMPLATE)
β”‚
β”œβ”€β”€ /karpenter                            ← Platform-agnostic Karpenter section
β”‚   β”œβ”€β”€ index.md                          (overview)
β”‚   β”œβ”€β”€ configuration.md                  (NodePool tuning - TEMPLATE)
β”‚   β”œβ”€β”€ cloud-providers.md                (provider-specific setup - TEMPLATE)
β”‚   └── troubleshooting.md                (scaling issues - TEMPLATE)
β”‚
β”œβ”€β”€ /ovh                                  ← OVH-specific section
β”‚   β”œβ”€β”€ index.md                          (OVH overview, 7-phase guide)
β”‚   β”œβ”€β”€ installation-guide.md             (copied from Installation_Guide.md)
β”‚   β”œβ”€β”€ cli-guide.md                      (copied from OVH_CLI_GUIDE.md)
β”‚   β”œβ”€β”€ cost-and-infrastructure.md        (TEMPLATE)
β”‚   β”œβ”€β”€ troubleshooting.md                (OVH-specific issues - TEMPLATE)
β”‚   └── README.md                         (OVH section overview)
β”‚
└── /aws                                  ← AWS-specific section (template)
    β”œβ”€β”€ index.md                          (AWS overview)
    β”œβ”€β”€ installation-guide.md             (AWS-specific steps - TEMPLATE)
    β”œβ”€β”€ cli-guide.md                      (AWS CLI reference - TEMPLATE)
    β”œβ”€β”€ cost-and-capacity.md              (AWS pricing - TEMPLATE)
    β”œβ”€β”€ troubleshooting.md                (AWS-specific issues - TEMPLATE)
    └── README.md                         (AWS section overview)

🎯 Organization Principles

1. Root (/) β€” Universal Information

  • Project goal: Cromwell + TES on any cloud Kubernetes
  • Platform choices comparison
  • General architecture
  • Quick reference (all platforms)

2. Component Sections (/tes, /cromwell, /karpenter)

Platform-agnostic, work on any cloud:

  • TES: Funnel architecture, images, configuration
  • Cromwell: Backend setup, workflow management
  • Karpenter: Auto-scaling configuration

These sections have NO cloud-specific content.

3. Platform Sections (/ovh, /aws)

Cloud-specific implementations:

  • OVH: Tested, production-ready
  • AWS: Template available
  • Each points to component sections for detailed info

These sections link to /tes, /cromwell, /karpenter for deep dives.


πŸ“š Navigation Flow

I want to deploy on OVHcloud

Root (/)
  └─> Choose Platform
      └─> OVH (/ovh/)
          β”œβ”€> 7-Phase Installation
          β”œβ”€> Links to TES (/tes/)
          β”œβ”€> Links to Cromwell (/cromwell/)
          └─> Links to Karpenter (/karpenter/)

I want to deploy on AWS

Root (/)
  └─> Choose Platform
      └─> AWS (/aws/)
          β”œβ”€> AWS Installation (template)
          β”œβ”€> Links to TES (/tes/)
          β”œβ”€> Links to Cromwell (/cromwell/)
          └─> Links to Karpenter (/karpenter/)

I want to understand TES

Root (/)
  └─> TES Section (/tes/)
      β”œβ”€> Overview
      β”œβ”€> Architecture
      β”œβ”€> Images
      β”œβ”€> Configuration
      └─> Troubleshooting

πŸ”„ Migration from Old Structure

Old Files (Root Level)

Old File New Location Status
index_old.md Archived Replaced by new multi-platform index.md
Installation_Guide.md /ovh/installation-guide.md Copied (OVH-specific)
CONTAINER_IMAGES.md /tes/container-images.md Copied (TES-specific)
OVH_CLI_GUIDE.md /ovh/cli-guide.md Copied (OVH-specific)
README_DOCUMENTATION.md Archived (old navigation) Replaced by new index.md
GITHUB_PAGES_SETUP.md Root level Still available for setup
QUICK_REFERENCE.md Root level Universal reference

Files at Root Level (Platform-Agnostic)

Remain at root for easy access:

  • index.md β€” Main landing page
  • quick-reference.md β€” Command cheat sheet
  • _config.yml β€” Jekyll configuration
  • GITHUB_PAGES_SETUP.md β€” Setup instructions

βœ… Current Status

Completed

  • Root index.md (multi-platform landing page)
  • /tes/index.md (overview)
  • /tes/architecture.md (design patterns, DaemonSet)
  • /tes/container-images.md (copied from CONTAINER_IMAGES.md)
  • /cromwell/index.md (overview)
  • /karpenter/index.md (overview)
  • /ovh/index.md (OVH production guide)
  • /ovh/installation-guide.md (copied from Installation_Guide.md)
  • /ovh/cli-guide.md (copied from OVH_CLI_GUIDE.md)
  • /aws/index.md (AWS template)

In Progress / Templates

  • /tes/configuration.md (TEMPLATE)
  • /tes/troubleshooting.md (TEMPLATE)
  • /cromwell/configuration.md (TEMPLATE)
  • /cromwell/workflows.md (TEMPLATE)
  • /cromwell/tes-integration.md (TEMPLATE)
  • /cromwell/troubleshooting.md (TEMPLATE)
  • /karpenter/configuration.md (TEMPLATE)
  • /karpenter/cloud-providers.md (TEMPLATE)
  • /karpenter/troubleshooting.md (TEMPLATE)
  • /ovh/cost-and-infrastructure.md (TEMPLATE)
  • /ovh/troubleshooting.md (TEMPLATE)
  • /aws/* (all AWS templates)

πŸš€ Deployment with New Structure

mkdir docs
cp -r tes cromwell karpenter ovh aws docs/
cp index.md quick-reference.md _config.yml .nojekyll docs/

Then set GitHub Pages:

  • Settings β†’ Pages β†’ Source: β€œDeploy from a branch”
  • Branch: β€œmain”, Folder: β€œ/docs”

Option B: Deploy from root

# Files already at root:
index.md
quick-reference.md
_config.yml
.nojekyll

# Subdirectories at root:
tes/
cromwell/
karpenter/
ovh/
aws/

Then set GitHub Pages:

  • Settings β†’ Pages β†’ Source: β€œDeploy from a branch”
  • Branch: β€œmain”, Folder: β€œ/” (root)

Page URL
Home /
TES /tes/
Cromwell /cromwell/
Karpenter /karpenter/
OVHcloud /ovh/
AWS /aws/
Quick Reference /quick-reference/

πŸ“ Contributing

To add content:

  1. Platform-agnostic info β†’ Add to /tes/, /cromwell/, or /karpenter/
  2. OVH-specific info β†’ Add to /ovh/
  3. AWS-specific info β†’ Add to /aws/
  4. General docs β†’ Add to root level

πŸ’‘ Benefits of New Structure

Aspect Before After
Clarity Mixed cloud-specific & agnostic Clearly separated
Reusability OVH docs tied to OVH TES/Cromwell work anywhere
Extensibility Hard to add new platform Easy to add /gcp/, /azure/
Navigation Manual cross-linking Semantic URL structure
Maintenance Updates everywhere Update once in component section

🎯 Future Platforms

Easy to add new cloud providers:

/gcp/
β”œβ”€β”€ index.md
β”œβ”€β”€ installation-guide.md
β”œβ”€β”€ cli-guide.md
└── troubleshooting.md

/azure/
β”œβ”€β”€ index.md
β”œβ”€β”€ installation-guide.md
β”œβ”€β”€ cli-guide.md
└── troubleshooting.md

Each points to /tes/, /cromwell/, /karpenter/ for core components.


Status: βœ… Reorganization Complete
Last Updated: March 13, 2026
Version: 2.0 (Multi-platform structure)