Migration of integration articles (#49)

* feat: Add service discovery section to documentation and sidebar

* feat: Add service defaults section to sidebar and documentation

* feat: Add launch profiles documentation and related image

* Add health checks documentation for Aspire

- Introduced a comprehensive guide on health checks in Aspire, covering both AppHost resource health checks and application health check endpoints.
- Detailed the usage of `/health` and `/alive` endpoints, including their configurations and best practices for non-development environments.
- Provided code examples for implementing health checks, request timeouts, and output caching.
- Explained integration health checks and custom resource health checks with practical examples.
- Included information on dashboard integration for monitoring health check statuses.

* migrate: Integrations check point

* feat: Update titles to include 'integration' for consistency across documentation

* more: migration and updates

* azure: Migration of azure stubs

* plus: more migrations....

* Refactor NuGet package installation commands in documentation to remove short names for consistency

- Updated multiple documentation files to remove the `shortName` attribute from `<InstallPackage>` commands for various Azure, database, and integration packages.
- Added a new helper function `generateFriendlyName` in `helpers.js` to create a friendly searchable name from Aspire NuGet package IDs, enhancing usability and maintainability.

* fix: Clean up .NET

* chore: Remove unused Placeholder component from SQLite integration documentation

* port: Diagnostics content

* Refactor Azure integration documentation and update image sizes

- Adjusted image dimensions for Azure Functions, Key Vault, OpenAI, PostgreSQL, Service Bus, SignalR, SQL Database, Storage Blobs, Queues, Tables, and Web PubSub to 80x80 pixels for consistency.
- Enhanced Azure overview documentation with new sections on local emulators, existing resources, and Azure Container Apps.
- Added descriptions and navigation properties to various integration documentation files, including Docker, Kubernetes, Elasticsearch, SQLite, Data API Builder, SQL Database Projects, Bun, Rust, Apache Kafka, RabbitMQ, Seq, YARP, and Keycloak.

* Refactor code snippets in documentation to include title annotations for clarity

- Updated various integration documentation files to add title annotations to C# code snippets, improving readability and context for users.
- Ensured consistency across all integration guides by standardizing the format of code examples.

* feat: Enhance Azure integration documentation with structured topics and improved clarity

* feat: Add initial devcontainer configuration for Aspire.Dev

* feat: Update Redis, Azure, and PostgreSQL integration documentation with trademark notices and improved clarity

* Update GitHub stats and integration documentation

- Increased star counts for dotnet/aspire, dotnet/aspire-samples, CommunityToolkit/Aspire, and microsoft/aspire.dev in github-stats.json.
- Added new Azure-related integrations and updated existing ones in integration-docs.json, enhancing the documentation for various Azure services.
- Created aspire-integration-names.json to list all integration names for easier reference and management.

Author: IEvangelist

.devcontainer/devcontainer.json

@@ -0,0 +1,23 @@
+{
+  "name": "Aspire.Dev",
+  "image": "mcr.microsoft.com/devcontainers/javascript-node:1-22-bookworm",
+  "customizations": {
+    "vscode": {
+      "extensions": [
+        "astro-build.astro-vscode"
+      ],
+      "settings": {
+        "terminal.integrated.defaultProfile.linux": "bash"
+      }
+    }
+  },
+  "forwardPorts": [4321],
+  "portsAttributes": {
+    "4321": {
+      "label": "Astro dev server",
+      "onAutoForward": "openBrowser"
+    }
+  },
+  "postCreateCommand": "npm install && echo '\n✨ Ready to go! Run \"npm run dev\" to start the dev server.\n'",
+  "remoteUser": "node"
+}

.github/prompts/migrate-from-learn.prompt.md

@@ -43,6 +43,66 @@ Migrate documentation content from the legacy `E:\GitHub\docs-aspire` repository
 - **Links**: `xref:` links → Regular markdown links or remove if no equivalent exists, and do inline code formatting for API references
 - Custom components available: `Aside`, `CardGrid`, `LinkCard`, `Steps`, `TabItem`, `Icon`, `FileTree`, `Kbd`, `LearnMore`, `PivotSelector`, `Pivot`, `ThemeImage`
 
+Learn's zone pivots:
+
+```md
+---
+title: Zone pivot example on Learn
+zone_pivot_groups: unit-testing-framework
+---
+
+:::pivot="xunit"
+Example xUnit content
+:::
+:::pivot="nunit"
+Example NUnit content
+:::
+```
+
+Then you'd have to look up the `docs/zones/zone-pivot-groups.yml` file to see which pivots belong to the `unit-testing-framework` group. For example:
+
+```yml
+- id: unit-testing-framework
+  title: Unit testing framework
+  prompt: Choose a unit testing framework
+  pivots:
+  - id: xunit
+    title: xUnit
+  - id: mstest
+    title: MSTest
+  - id: nunit
+    title: NUnit
+```
+
+For `aspire.dev` our pivots are based on two custom components:
+
+```mdx
+---
+title: Example pivot example on aspire.dev
+---
+
+import Pivot from '@components/Pivot.astro';
+import PivotSelector from '@components/PivotSelector.astro';
+
+<PivotSelector
+    title="Select your testing framework"
+    key="testing-framework"
+    options={[
+        { id: "xunit", title: "xUnit.net" },
+        { id: "mstest", title: "MSTest" },
+        { id: "nunit", title: "NUnit" },
+    ]}
+/>
+
+
+<Pivot id="xunit">
+Example xUnit content
+</Pivot>
+<Pivot id="nunit">
+Example NUnit content
+</Pivot>
+```
+
 ### Image Handling
 1. **Import statement**: Add `import { Image } from 'astro:assets';` to imports
 2. **Asset import**: `import imageName from '@assets/{section}/{filename}';`
@@ -52,7 +112,7 @@ Migrate documentation content from the legacy `E:\GitHub\docs-aspire` repository
 
 ### Link Transformations
 - **Remove**: "See also" sections entirely
-- **Internal links**: Convert to site-relative with trailing slash (e.g., `/dashboard/overview/`)
+- **Internal links**: Convert to site-relative with trailing slash (e.g., `/dashboard/overview/`), assume absolute links should be used when site relative links don't exist in aspire.dev, and use a base of `https://learn.microsoft.com/`, i.e.; for links that start with `/azure`, `/dotnet`, and `/aspnet`.
 - **Only link if certain**: Only create internal links to content you're 100% sure exists
 - **External links**: Keep as-is, prefer official documentation sources
 

.github/prompts/update-integrations.promt.md

@@ -0,0 +1,58 @@
+# Update Integration Documentation Links
+
+## Task Overview
+
+Update the integration documentation links by synchronizing package names from the NuGet catalog with their corresponding documentation URLs.
+
+## Steps
+
+1. **Run the update script**
+
+    ```bash
+    node src/frontend/scripts/update-integrations.js
+    ```
+
+2. **Read the updated package data**
+    - Load `src/frontend/src/data/aspire-integration-names.json`
+    - Extract all package names from the JSON array
+
+3. **Update integration documentation mappings**
+    - Load `src/frontend/src/data/integration-docs.json`
+    - For each package name in `src/frontend/src/data/aspire-integration-names.json`:
+      - Check if a matching entry exists in `integration-docs.json` (where `match` equals the package name)
+      - If an entry exists, verify the `href` is correct
+      - If no entry exists, determine the appropriate documentation URL based on:
+         - Package name patterns (e.g., `Aspire.Hosting.X` → `/integrations/*/x/`)
+         - Existing similar package mappings
+         - Technology category (databases, messaging, caching, ai, etc.)
+      - Add or update the entry with the package name as `match` and site-relative path as `href`
+
+4. **Ensure consistency**
+    - Remove any entries from `integration-docs.json` that reference packages no longer in `aspire-integrations.json`
+    - Maintain alphabetical or logical ordering
+    - Preserve existing correct mappings
+
+## Output
+
+Save the updated `integration-docs.json` with all current packages properly mapped to their documentation pages.
+
+## Example Entry Format
+
+```json
+{
+  "match": "Aspire.Hosting.Redis",
+  "href": "/integrations/caching/redis/"
+},
+{
+  "match": "Aspire.Hosting.Azure.Storage",
+  "href": "/integrations/cloud/azure/azure-storage-blobs/"
+},
+{
+  "match": "Aspire.Hosting.Testing",
+  "href": "/testing/overview/"
+}
+```
+
+## Verification
+
+Ensure that all site relative links end with a trailing slash and point to valid documentation pages, do not assume a page exists without verification. When there's a package name that has no clear mapping, take note of it and list it for manual review—in these situations, we'll likely need to write a new documentation page.

src/frontend/lunaria.config.json

@@ -3,7 +3,7 @@
   "repository": {
     "name": "microsoft/aspire.dev",
     "branch": "main",
-    "rootDir": "src/frontend",
+    "rootDir": ".",
     "hosting": "github"
   },
   "defaultLocale": {

src/frontend/scripts/update-integrations.js

@@ -17,6 +17,7 @@ const EXCLUDED_PACKAGES = [
   'Aspire.RabbitMQ.Client.v7'
 ];
 const OUTPUT_PATH = './src/data/aspire-integrations.json';
+const OUTPUT_NAME_PATH = './src/data/aspire-integration-names.json';
 
 // According to documentation, nuget.org limits:
 // - 'take' parameter to 1,000
@@ -260,6 +261,7 @@ async function getPreferredNonDeprecatedVersion(regBase, id) {
   const nonDeprecated = await filterOutDeprecatedWithRegistration(unique);
   const output = filterAndTransform(nonDeprecated);
     fs.writeFileSync(OUTPUT_PATH, JSON.stringify(output, null, 2));
+    fs.writeFileSync(OUTPUT_NAME_PATH, JSON.stringify(output.map(p => p.title), null, 2));
     console.log(`✅ Saved ${output.length} packages to ${OUTPUT_PATH}`);
   } catch (err) {
     console.error('❌ Error:', err);