Reshuffle deployment docs: new pages, sidebar restructure, messaging updates (#644)

* Reshuffle deployment docs structure

- Move pipelines doc from get-started to deployment section
- Move manifest-format under deployment/azure with deprecation notice
- Create new Deploy to Docker Compose page
- Create new Deploy to Kubernetes page
- Create new Azure Developer CLI (azd) page (legacy/alternative path)
- Create new Customize Azure Container Apps page
- Remove stale preview labels (aspire deploy and Docker are GA)
- Update Docker package version from preview to 13.1.0
- Remove manifest references from general-purpose docs
- Position aspire deploy as primary Azure deployment path
- Trim integration pages (Docker, K8s) to link to deployment pages
- Update sidebar, redirects, and cross-references
- Update stale aspire-8.0.json schema reference

Addresses: #354, #331, #335, #358, #359

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

* Move Japanese pipelines translation to match new slug

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

* Fix localized pipeline links to new deployment path

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

* Fix duplicate K8s sidebar entry and remove pipelines from docs.topics.ts

- Remove duplicate 'Deploy to Kubernetes' sidebar entry
- Remove pipelines from get-started sidebar (already in deployment sidebar)

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

* Add TypeScript AppHost tabs to all deployment pages

- Add C#/TypeScript tabs to 14 AppHost code blocks across 4 pages
- Add 'not yet available' notes for 3 APIs without TS support:
  ConfigureEnvFile, WithImagePushOptions, ConfigureCustomDomain
- Fix Docker package version to 13.2.0
- Add Preview badge to Kubernetes deployment page
- Remove manifest schema ref from hosting-integrations

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

* Fix TypeScript API examples to match actual compiler-verified signatures

- addProject needs 3 args (name, path, launchProfile)
- addContainer uses single image:tag string
- Callbacks must be async (publishAsDockerComposeService, etc.)
- Properties use .set() pattern (service.name.set, k8s.helmChartName.set)
- ImagePullPolicy uses enum import, not string literal
- addContainerRegistryFromString for string args
- publishAsExisting takes strings, not ParameterResource
- withResourceGroup removed from TS (takes ParameterResource)
- publishAsAzureContainerApp callback simplified (ContainerAppHandle)

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

* Reorder deployment sidebar: group targets, add Advanced section

- Move deploy targets (Docker, K8s, Azure) right after Pipelines
- Move azd to bottom of Azure section (legacy)
- Move Deploy JavaScript apps below targets
- Group state caching + custom pipelines under collapsed Advanced

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

* Fix 3 critical issues found by doc-tester

- K8s: Remove invalid resource.Deployment reference (use comment placeholder)
- ACA: Fix PublishAsExisting to require 2 params (name + resourceGroup)
- ACA: Fix WithResourceGroup — it's on AzureEnvironmentResource, not individual resources

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

* Add TypeScript tab to pipelines page with 'not yet available' note

Follow existing pattern: show TS tab with :::note when API isn't in TS SDK.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

* Use tab pattern for unavailable TS APIs instead of standalone Aside

Convert ConfigureEnvFile, WithImagePushOptions, and ConfigureCustomDomain
to show a TypeScript tab with :::note inside, matching the established
pattern used in container-files.mdx and other docs.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

* Move app lifecycle guide to deployment section

- Move fundamentals/app-lifecycle.mdx to deployment/app-lifecycle.mdx
- Add to deployment sidebar as 'App lifecycle (CI/CD)'
- Update slug in docs.topics.ts
- Add redirect from old path

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

* Clean .NET-centric language from app lifecycle guide

- Frame example as C# with note that TS AppHosts follow same pattern
- Replace AppHost.cs references with generic 'AppHost'
- Change '.NET process' to 'local process'
- Add tip about TypeScript AppHost equivalence
- Note --project flag purpose in CI/CD example

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

* Fix doc-tester final round issues

- Remove app-lifecycle from docs.topics.ts (fixes wrong prev/next nav)
- Fix WellKnownSteps → WellKnownPipelineSteps (8 occurrences in prose)
- Add missing using/pragma to pipelines code example
- Add missing 'using Aspire.Hosting.Docker' to ConfigureEnvFile example
- Add missing ASPIRECOMPUTE003 pragma to AddContainerRegistry example
- Add missing ASPIREACADOMAINS001 pragma to ConfigureCustomDomain example

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

* Fix K8s deploy column: no aspire deploy support for Kubernetes

Kubernetes uses aspire publish + Helm/kubectl, not aspire deploy.
Addresses review feedback.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

* Address PR review feedback from @JamesNK

- docker-compose: mention AddDockerComposeEnvironment in prose, highlight key lines
- docker-compose: change example resource name to avoid 'docker-compose-down-compose'
- kubernetes: rename to 'Publish to Kubernetes', clarify no aspire deploy support
- kubernetes: mention AddKubernetesEnvironment in prose, highlight key lines
- kubernetes: replace plaintext tree with FileTree component
- kubernetes: update sidebar label to match
- redirects: add missing Japanese locale redirect for pipelines
- deploy-first-app: fix lowercase 'when' at sentence start
- customize-container-apps: add TS tab to Resource groups section
- docker-compose: margin-bottom issue is a site-wide CSS concern (noted for @IEvangelist)

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

* Address round 2 PR feedback from @JamesNK

- kubernetes: make TS samples match C# scope (snippet-only, not full builder)
- kubernetes: remove ASPIRE_RESOURCE_SERVICE_ENDPOINT_URL caution (dashboard-only)
- azd: make TS sample match C# scope
- customize-aca: make all TS samples match C# scope (5 blocks fixed)
- customize-aca: link 'Azure Container Apps' to ACA about page
- customize-aca: add TS tab to Resource groups with :::note pattern

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

* Revert Kubernetes rename — keep 'Deploy to Kubernetes' in deployment section

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

* Fix C#/TypeScript sample parity across deployment pages

- docker-compose: remove builder boilerplate from registry TS sample
- customize-aca: clarify ContainerAppHandle scaling in TS comment
- customize-aca: clean up publishAsExisting TS sample (strings, not params)

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

* Use 'env' as Docker Compose resource name in examples

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

* Fix 'front end' -> 'frontend' consistency in deploy-first-app

Addresses review feedback: standardize on 'frontend' (one word) throughout
prose and mermaid diagram labels.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

* Fix remaining C#/TS sample mismatches

- docker-compose: use addParameterFromConfiguration to match C# config binding
- customize-aca: use publishAsExistingFromParameters with parameters to match C#
- ACA scaling: genuine API gap (ContainerAppHandle), comment is accurate

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

* Clean up content, fix issues with C# APIs being incorrect, link to aspire.dev API ref - instead of MS Learn, fix #645

---------

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Co-authored-by: David Pine <david.pine@microsoft.com>

Author: 3 people

.gitignore

@@ -450,4 +450,5 @@ FodyWeavers.xsd
 
 
 bin/
-obj/
+obj/
+tmp-ts-validation/

src/frontend/config/redirects.mjs

@@ -72,4 +72,8 @@ export const redirects = {
   '/reference/cli/commands/aspire-mcp-start/': '/reference/cli/commands/aspire-agent-mcp/',
   '/reference/cli/commands/aspire-exec/': '/reference/cli/commands/aspire-resource/',
   '/get-started/configure-mcp/': '/get-started/ai-coding-agents/',
+  '/get-started/pipelines/': '/deployment/pipelines/',
+  '/ja/get-started/pipelines/': '/ja/deployment/pipelines/',
+  '/deployment/manifest-format/': '/deployment/azure/manifest-format/',
+  '/fundamentals/app-lifecycle/': '/deployment/app-lifecycle/',
 };

src/frontend/config/sidebar/deployment.topics.ts

@@ -64,71 +64,16 @@ export const deploymentTopics: StarlightSidebarTopicsUserConfig = {
       slug: 'deployment/overview',
     },
     {
-      label: 'Deploy JavaScript apps',
-      slug: 'deployment/javascript-apps',
+      label: 'Pipelines (aspire do)',
+      slug: 'deployment/pipelines',
     },
     {
-      label: 'Deployment manifest format',
-      translations: {
-        da: 'Udrulningsmanifestformat',
-        de: 'Bereitstellungsmanifestformat',
-        en: 'Deployment manifest format',
-        es: 'Formato de manifiesto de despliegue',
-        fr: 'Format de manifeste de déploiement',
-        hi: 'तैनाती मैनिफ़ेस्ट प्रारूप',
-        id: 'Format manifes penyebaran',
-        it: 'Formato del manifesto di distribuzione',
-        ja: 'デプロイマニフェスト形式',
-        ko: '배포 매니페스트 형식',
-        'pt-BR': 'Formato de manifesto de implantação',
-        ru: 'Формат манифеста развертывания',
-        tr: 'Dağıtım bildirimi biçimi',
-        uk: 'Формат маніфесту розгортання',
-        'zh-CN': '部署清单格式',
-      },
-      slug: 'deployment/manifest-format',
-    },
-    {
-      label: 'Deployment state caching',
-      translations: {
-        da: 'Cachelagring af udrulningstilstand',
-        de: 'Zwischenspeichern des Bereitstellungsstatus',
-        en: 'Deployment state caching',
-        es: 'Almacenamiento en caché del estado de despliegue',
-        fr: "Mise en cache de l'état de déploiement",
-        hi: 'तैनाती स्थिति कैशिंग',
-        id: 'Caching status penyebaran',
-        it: 'Memorizzazione nella cache dello stato di distribuzione',
-        ja: 'デプロイ状態のキャッシュ',
-        ko: '배포 상태 캐싱',
-        'pt-BR': 'Cache de estado de implantação',
-        ru: 'Кэширование состояния развертывания',
-        tr: 'Dağıtım durumu önbelleğe alma',
-        uk: 'Кешування стану розгортання',
-        'zh-CN': '部署状态缓存',
-      },
-      slug: 'deployment/deployment-state-caching',
+      label: 'Deploy to Docker Compose',
+      slug: 'deployment/docker-compose',
     },
     {
-      label: 'Custom deployment pipelines',
-      translations: {
-        da: 'Brugerdefinerede implementeringspipelines',
-        de: 'Benutzerdefinierte Bereitstellungspipelines',
-        en: 'Custom deployment pipelines',
-        es: 'Canalizaciones de despliegue personalizadas',
-        fr: 'Pipelines de déploiement personnalisés',
-        hi: 'कस्टम तैनाती पाइपलाइन',
-        id: 'Pipeline penyebaran kustom',
-        it: 'Pipeline di distribuzione personalizzate',
-        ja: 'カスタム デプロイ パイプライン',
-        ko: '사용자 지정 배포 파이프라인',
-        'pt-BR': 'Pipelines de implantação personalizados',
-        ru: 'Пользовательские конвейеры развертывания',
-        tr: 'Özel dağıtım işlem hatları',
-        uk: 'Користувацькі конвеєри розгортання',
-        'zh-CN': '自定义部署管道',
-      },
-      slug: 'deployment/custom-deployments',
+      label: 'Deploy to Kubernetes',
+      slug: 'deployment/kubernetes',
     },
     {
       label: 'Deploy to Azure',
@@ -172,6 +117,10 @@ export const deploymentTopics: StarlightSidebarTopicsUserConfig = {
           },
           slug: 'deployment/azure/aca-deployment-aspire-cli',
         },
+        {
+          label: 'Customize Azure Container Apps',
+          slug: 'deployment/azure/customize-container-apps',
+        },
         {
           label: 'Azure security best practices',
           translations: {
@@ -193,6 +142,42 @@ export const deploymentTopics: StarlightSidebarTopicsUserConfig = {
           },
           slug: 'deployment/azure/azure-security-best-practices',
         },
+        {
+          label: 'Azure Developer CLI (azd)',
+          collapsed: true,
+          items: [
+            {
+              label: 'Overview',
+              slug: 'deployment/azure/azure-developer-cli',
+            },
+            {
+              label: 'Deployment manifest format',
+              slug: 'deployment/azure/manifest-format',
+            },
+          ],
+        },
+      ],
+    },
+    {
+      label: 'Deploy JavaScript apps',
+      slug: 'deployment/javascript-apps',
+    },
+    {
+      label: 'App lifecycle (CI/CD)',
+      slug: 'deployment/app-lifecycle',
+    },
+    {
+      label: 'Advanced',
+      collapsed: true,
+      items: [
+        {
+          label: 'Deployment state caching',
+          slug: 'deployment/deployment-state-caching',
+        },
+        {
+          label: 'Custom deployment pipelines',
+          slug: 'deployment/custom-deployments',
+        },
       ],
     },
   ],

src/frontend/config/sidebar/docs.topics.ts

@@ -529,27 +529,6 @@ export const docsTopics: StarlightSidebarTopicsUserConfig = {
               },
               slug: 'get-started/app-host',
             },
-            {
-              label: 'Pipelines and app topology',
-              translations: {
-                da: 'Udrulning og apptopologi',
-                de: 'Bereitstellung und App-Topologie',
-                en: 'Pipelines and app topology',
-                es: 'Despliegue y topología de la aplicación',
-                fr: 'Déploiement et topologie de l’application',
-                hi: 'परिनियोजन और ऐप टोपोलॉजी',
-                id: 'Penyebaran dan topologi aplikasi',
-                it: 'Distribuzione e topologia dell’applicazione',
-                ja: 'パイプラインとアプリのトポロジー',
-                ko: '배포 및 앱 토폴로지',
-                'pt-BR': 'Implantação e topologia do aplicativo',
-                ru: 'Развертывание и топология приложения',
-                tr: 'Dağıtım ve uygulama topolojisi',
-                uk: 'Розгортання і топологія застосунку',
-                'zh-CN': '部署与应用拓扑',
-              },
-              slug: 'get-started/pipelines',
-            },
             {
               label: 'Understanding resources',
               translations: {
@@ -571,27 +550,6 @@ export const docsTopics: StarlightSidebarTopicsUserConfig = {
               },
               slug: 'get-started/resources',
             },
-            {
-              label: 'Aspire app lifecycle guide',
-              slug: 'fundamentals/app-lifecycle',
-              translations: {
-                da: 'Guide til Aspire app-livscyklus',
-                de: 'Leitfaden zum Aspire-App-Lebenszyklus',
-                en: 'Aspire app lifecycle guide',
-                es: 'Guía del ciclo de vida de la aplicación Aspire',
-                fr: 'Guide du cycle de vie des applications Aspire',
-                hi: 'Aspire ऐप जीवनचक्र गाइड',
-                id: 'Panduan siklus hidup aplikasi Aspire',
-                it: 'Guida al ciclo di vita delle app Aspire',
-                ja: 'Aspire アプリのライフサイクル ガイド',
-                ko: 'Aspire 앱 수명 주기 가이드',
-                'pt-BR': 'Guia do ciclo de vida do aplicativo Aspire',
-                ru: 'Руководство по жизненному циклу приложения Aspire',
-                tr: 'Aspire uygulama yaşam döngüsü kılavuzu',
-                uk: 'Посібник з життєвого циклу застосунку Aspire',
-                'zh-CN': 'Aspire 应用生命周期指南',
-              },
-            },
             {
               label: 'Glossary',
               slug: 'get-started/glossary',
@@ -1340,4 +1298,4 @@ export const docsTopics: StarlightSidebarTopicsUserConfig = {
       ],
     },
   ],
-};
+};

src/frontend/src/content/docs/app-host/container-registry.mdx

@@ -629,4 +629,4 @@ The explicit container registry configuration introduced in Aspire 13.1 provides
 - [Configure Azure Container Apps environments](/integrations/cloud/azure/configure-container-apps/)
 - [`aspire do` command](/reference/cli/commands/aspire-do/)
 - [External parameters](/fundamentals/external-parameters/)
-- [Pipelines and app topology](/get-started/pipelines/)
+- [Pipelines and app topology](/deployment/pipelines/)

src/frontend/src/content/docs/da/index.mdx

@@ -97,7 +97,7 @@ import LanguagesSupported from '@components/LanguagesSupported.astro';
 
 ## Lokal-først, produktionsklar
 
-**Bygget til lokal udvikling**, Aspire spejler produktionsmiljøer på din maskine, eliminerer "virker på min maskine" problemer for glatte deployments. [Lær om deployment og app-topologi](/da/get-started/pipelines/).
+**Bygget til lokal udvikling**, Aspire spejler produktionsmiljøer på din maskine, eliminerer "virker på min maskine" problemer for glatte deployments. [Lær om deployment og app-topologi](/da/deployment/pipelines/).
 
 import LocalVsProdEnvironments from '@components/LocalVsProdEnvironments.astro';
 

src/frontend/src/content/docs/de/index.mdx

@@ -99,7 +99,7 @@ Aspire unterstützt viele Sprachen & Frameworks und lässt dich mit deinen Favor
 
 ## Lokal zuerst, produktionsbereit
 
-**Für lokale Entwicklung gebaut**, Aspire spiegelt Produktionsumgebungen auf deiner Maschine und eliminiert „Works on my machine“-Probleme für reibungslose Deployments. [Mehr über Deployment & App-Topologie](/de/get-started/pipelines/).
+**Für lokale Entwicklung gebaut**, Aspire spiegelt Produktionsumgebungen auf deiner Maschine und eliminiert „Works on my machine“-Probleme für reibungslose Deployments. [Mehr über Deployment & App-Topologie](/de/deployment/pipelines/).
 
 import LocalVsProdEnvironments from '@components/LocalVsProdEnvironments.astro';
 

…tent/docs/fundamentals/app-lifecycle.mdx …ontent/docs/deployment/app-lifecycle.mdxsrc/frontend/src/content/docs/fundamentals/app-lifecycle.mdx renamed to src/frontend/src/content/docs/deployment/app-lifecycle.mdx src/frontend/src/content/docs/fundamentals/app-lifecycle.mdx renamed to src/frontend/src/content/docs/deployment/app-lifecycle.mdx

@@ -6,7 +6,7 @@ description: Understand the lifecycle of Aspire applications from development to
 import { Aside, FileTree, Steps } from '@astrojs/starlight/components';
 import LearnMore from '@components/LearnMore.astro';
 
-This guide provides a high-level overview of the lifecycle phases of an Aspire application, from development through local deployment to production release. By using the same `AppHost` configuration across all phases, you ensure consistency and reduce configuration drift between environments. 
+This guide provides a high-level overview of the lifecycle phases of an Aspire application, from development through local deployment to production release. By using the same AppHost configuration across all phases, you ensure consistency and reduce configuration drift between environments. 
 The example in this guide demonstrates how Aspire orchestrates containerized applications with persistent storage and CI/CD automation using the [Docker Integration](/integrations/compute/docker/) and GitHub.
 
 ## App lifecycle
@@ -25,6 +25,8 @@ The Aspire application lifecycle consists of three main phases:
 
 ### Example
 
+The following example uses a C# AppHost, but the same lifecycle applies to TypeScript AppHosts.
+
 Consider [this example](https://github.com/BethMassi/VolumeMount/). You have a distributed application that consists of a Blazor web project that relies on a SQL Server database with a persistent data volume as well as a persistent writable file volume to capture user file uploads. 
 You want to distribute your Blazor app as a Docker container image via the GitHub Container Registry. You need the [Aspire.Hosting.Docker](/integrations/compute/docker/) and [Aspire.Hosting.SqlServer](/integrations/databases/sql-server/sql-server-get-started/) integrations. 
 
@@ -104,7 +106,7 @@ When you run `aspire run`:
 <Steps>
 
 1. **Aspire dashboard launches** - A web-based dashboard starts, and its URL (often an HTTPS login URL like `https://localhost:<port>/login?...`) is printed to the console.
-2. **Resources start** - All resources defined in your `AppHost.cs` are orchestrated. 
+2. **Resources start** - All resources defined in your AppHost are orchestrated. 
 3. **Live debugging** - You can attach debuggers, set breakpoints, and modify code with hot reload.
 4. **Telemetry & logs** - Dashboard provides real-time logs, metrics, and distributed traces.
 
@@ -132,7 +134,7 @@ Dashboard:  https://localhost:17244/login?t=9db79f2885dae24ee06c6ef10290b8b2
 
 In the example above, when resources start with the run command:
 - SQL Server container starts in Docker with persistent volume
-- Blazor Web project runs as a .NET process (**not containerized**)
+- Web project runs as a local process (**not containerized**)
 - Database is automatically created and migrated (containerized)
 
 ## Phase 2: Local Deployment
@@ -193,7 +195,7 @@ In [this example](https://github.com/BethMassi/VolumeMount/blob/main/.github/wor
 
 <Steps>
 
-1. **Setup Environment** - Install .NET
+1. **Setup Environment** - Install required SDKs
 2. **Install Aspire CLI** - Install the Aspire CLI
 3. **Build and Push Container Images** - Build app and push image to GitHub Container Registry with `aspire do push`
 4. **Publish Docker Compose Artifacts** - Generate deployment files with `aspire publish`
@@ -204,6 +206,7 @@ In [this example](https://github.com/BethMassi/VolumeMount/blob/main/.github/wor
 #### Step 1: Setup Environment
 
 ```yaml
+# Required for C# AppHost projects
 - name: Setup .NET
   uses: actions/setup-dotnet@v4
   with:
@@ -241,7 +244,7 @@ Replace `your-org/your-repo` with your actual GitHub organization and repository
 </Aside>
 
 The `aspire do push` command does the following:
-- Analyzes your `AppHost.cs` configuration
+- Analyzes your AppHost configuration
 - Restores dependencies and builds the project
 - Builds Docker container images for project resources
 - Tags images with configured registry endpoint and repository
@@ -264,8 +267,12 @@ The `aspire do push` command does the following:
       --output-path ./aspire-output
 ```
 
+<Aside type="note">
+The `--project` flag is needed when your AppHost isn't in the current directory.
+</Aside>
+
 The `aspire publish` command does the following:
-- Analyzes your `AppHost.cs` configuration
+- Analyzes your AppHost configuration
 - Generates `docker-compose.yaml` file with all service definitions
 - Creates `.env` template file for environment variables
 - Packages configuration needed for deployment
@@ -329,11 +336,15 @@ After the workflow completes, you have everything needed for production deployme
 
 | Phase | Command | Purpose | Environment | App | Database |
 |-------|---------|---------|-------------|------------|------------|
-| **Development** | `aspire run` | Inner-loop coding & debugging | Local machine | App process (i.e. .NET) | Container |
+| **Development** | `aspire run` | Inner-loop coding & debugging | Local machine | Local process | Container |
 | **Local Deploy** | `aspire deploy` | Test containerized app locally | Registered compute environment (i.e. Docker Desktop) | Container | Container |
 | **Release** | CI/CD workflow (i.e. GitHub Actions) | Publish to staging/ production | Cloud/Server | Container | Container |
 
-The `AppHost.cs` file is the **single source of truth** for your application architecture. Each phase above uses the exact same `AppHost` configuration. This eliminates configuration drift between development and deployment. It defines things your distributed application needs like:
+<Aside type="tip">
+This example uses a C# AppHost, but the same lifecycle workflow applies to TypeScript AppHosts. Replace `.csproj` references with your `apphost.ts` path as needed.
+</Aside>
+
+The AppHost is the **single source of truth** for your application architecture. Each phase above uses the exact same AppHost configuration. This eliminates configuration drift between development and deployment. It defines things your distributed application needs like:
 - **Services & Dependencies** - Projects, containers, and their relationships
 - **Configuration** - Connection strings, secrets, and parameters
 - **Volumes** - Persistent storage for databases and files