Fix misc issues (#6)

* fix: standardize section headings to lowercase across documentation

* fix: update links in documentation for consistency

* fix: update search term for Go icon in IntegrationGrid and set fetchpriority for images in Hero component

* fix: add canonical URL for SEO and reorder favicon links for better prioritization

* fix: restore robots.txt file with user-agent and sitemap directives (corrected location)

* Update src/frontend/astro.config.mjs

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

---------

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

Author: IEvangelist

src/frontend/astro.config.mjs

@@ -97,9 +97,9 @@ export default defineConfig({
 				{ tag: 'meta', attrs: { name: 'twitter:description', content: 'Aspire (formerly .NET Aspire) streamlines your development workflow with code-first control, modularity, and observability.' } },
 				{ tag: 'meta', attrs: { name: 'twitter:image', content: 'https://aspire.dev/og-image.png' } },
 
-				// Favicons and icons
-				{ tag: 'link', attrs: { rel: 'icon', type: 'image/png', href: '/favicon-96x96.png', sizes: '96x96' } },
+				// Favicons and icons (ordered: SVG → PNG → ICO → Apple Touch Icon)
 				{ tag: 'link', attrs: { rel: 'icon', type: 'image/svg+xml', href: '/favicon.svg' } },
+				{ tag: 'link', attrs: { rel: 'icon', type: 'image/png', href: '/favicon-96x96.png', sizes: '96x96' } },
 				{ tag: 'link', attrs: { rel: 'shortcut icon', href: '/favicon.ico' } },
 				{ tag: 'link', attrs: { rel: 'apple-touch-icon', sizes: '180x180', href: '/apple-touch-icon.png' } },
 				{ tag: 'meta', attrs: { name: 'apple-mobile-web-app-title', content: 'Aspire' } },

src/frontend/src/assets/robots.txt src/frontend/public/robots.txtsrc/frontend/src/assets/robots.txt renamed to src/frontend/public/robots.txt

@@ -163,7 +163,7 @@ const icons = [
   { meta: elasticIcon, alt: "Elasticsearch", search: "elasticsearch" },
   { meta: eventStoreIcon, alt: "EventStore", search: "eventstore" },
   { meta: garnetIcon, alt: "Garnet", search: "garnet" },
-  { meta: goIcon, alt: "Go", search: "go", light: goLightIcon },
+  { meta: goIcon, alt: "Go", search: "golang gofeature", light: goLightIcon },
   { meta: gitHubIcon, alt: "GitHub", search: "github", light: gitHubLightIcon },
   { meta: javaIcon, alt: "Java", search: "java" },
   { meta: k6Icon, alt: "k6", search: "k6" },

src/frontend/src/components/IntegrationGrid.astro

@@ -12,6 +12,7 @@ const imageAttrs = {
   decoding: "async" as const,
   width: 1000,
   height: 1000,
+  fetchpriority: "high" as const,
   alt: image?.alt || "",
 };
 

src/frontend/src/components/starlight/Hero.astro

@@ -72,7 +72,7 @@ import PublishAppTopologyLight from "@assets/architecture/overview/publish-app-t
 
 ## Dev-time orchestration
 
-In run mode, [the AppHost orchestrates](/getting-started/app-host/) all resources defined in your app model. But how does it achieve this?
+In run mode, [the AppHost orchestrates](/get-started/app-host/) all resources defined in your app model. But how does it achieve this?
 
 > [!IMPORTANT]
 > The AppHost isn't a production runtime. It's a development-time orchestration tool that simplifies the process of running and debugging your application locally.
@@ -109,7 +109,7 @@ In this section, several key questions are answered to help you understand how t
 
 The orchestration process follows a layered architecture. At its core, the AppHost represents the developer's desired view of the distributed application's resources. DCP ensures that this desired state is realized by orchestrating the resources and maintaining consistency.
 
-The [app model](/getting-started/app-host/) serves as a blueprint for DCP to orchestrate your application. Under the hood, the AppHost is a .NET console application powered by the [`📦 Aspire.Hosting.AppHost`](https://www.nuget.org/packages/Aspire.Hosting.AppHost) NuGet package. This package includes build targets that register orchestration dependencies, enabling seamless dev-time orchestration.
+The [app model](/get-started/app-host/) serves as a blueprint for DCP to orchestrate your application. Under the hood, the AppHost is a .NET console application powered by the [`📦 Aspire.Hosting.AppHost`](https://www.nuget.org/packages/Aspire.Hosting.AppHost) NuGet package. This package includes build targets that register orchestration dependencies, enabling seamless dev-time orchestration.
 
 DCP is a Kubernetes-compatible API server, meaning it uses the same network protocols and conventions as Kubernetes. This compatibility allows the Aspire AppHost to leverage existing Kubernetes libraries for communication. Specifically, the AppHost contains an implementation of the `k8s.KubernetesClient` (from the [📦 KubernetesClient](https://www.nuget.org/packages/KubernetesClient) NuGet package), which is a .NET client for Kubernetes. This client is used to communicate with the DCP API server, enabling the AppHost to delegate orchestration tasks to DCP.
 
@@ -122,7 +122,7 @@ import AppHostDcpFlowLight from "@assets/architecture/overview/app-host-dcp-flow
             alt="Flow diagram showing AppHost delegating to DCP"
             label={"AppHost flow diagram"} />
 
-### Developer Control Plane
+### Developer control plane
 
 DCP is at the core of the Aspire AppHost orchestration functionality. It's responsible for orchestrating all resources defined in your app model, starting the developer dashboard, ensuring that everything is set up correctly for local development and testing. DCP manages the lifecycle of resources, applies network configurations, and resolves dependencies.
 

src/frontend/src/content/docs/architecture/overview.mdx

@@ -7,15 +7,15 @@ import { Aside, Steps } from '@astrojs/starlight/components';
 
 Aspire's resource model allows you to define and configure resources in a structured way, enabling seamless integration and management of your application's components. This guide provides details the common patterns for adding and configuring resources in Aspire.
 
-## API Patterns
+## API patterns
 
 Aspire separates **resource data models** from **behavior** using **fluent extension methods**.  
 - **Resource classes** define only constructors and properties.  
 - **Extension methods** implement resource creation, configuration, and runtime wiring.  
 
 This guide describes each pattern and shows a **verbatim Redis example** at the end. It also covers how to publish manifests via custom resources.
 
-## Adding Resources with `AddX(...)`
+## Adding resources with `AddX(...)`
 
 An `AddX(...)` method executes:
 
@@ -26,7 +26,7 @@ An `AddX(...)` method executes:
 1. **Optional wiring** of endpoints, health checks, container settings, environment variables, command-line arguments, and event subscriptions.
 </Steps>
 
-### Signature Pattern
+### Signature pattern
 
 ```csharp
 public static IResourceBuilder<TResource> AddX(
@@ -47,7 +47,7 @@ public static IResourceBuilder<TResource> AddX(
 }
 ```
 
-### Optional Wiring Examples
+### Optional wiring examples
 
 **Endpoints**:
 
@@ -87,7 +87,7 @@ public static IResourceBuilder<TResource> AddX(
 builder.Eventing.Subscribe<EventType>(resource, handler);
 ```
 
-### Summary Table
+### Summary table
 
 | Step | Call/Method | Purpose |
 |--|--|--|
@@ -96,11 +96,11 @@ builder.Eventing.Subscribe<EventType>(resource, handler);
 | Register | `builder.AddResource(resource)` | Add resource to the application model |
 | Optional wiring | `.WithEndpoint(…)`, `.WithHealthCheck(…)`, `.WithImage(…)`, `.WithEnvironment(…)`, `.WithArgs(…)`, `Eventing.Subscribe(…)` | Configure container details, wiring, and runtime hooks |
 
-## Configuring Resources with `WithX(...)`
+## Configuring resources with `WithX(...)`
 
 `WithX(...)` methods **attach annotations** to resource builders.
 
-### Signature Pattern
+### Signature pattern
 
 ```csharp
 public static IResourceBuilder<TResource> WithX(
@@ -113,7 +113,7 @@ public static IResourceBuilder<TResource> WithX(
 - **Action**: `WithAnnotation(...)`.
 - **Returns**: `IResourceBuilder<TResource>`.
 
-### Summary Table
+### Summary table
 
 | Method | Target | Action |
 |--|--|--|
@@ -124,7 +124,7 @@ public static IResourceBuilder<TResource> WithX(
 
 Annotations are **public** metadata types implementing `IResourceAnnotation`. They can be added or removed dynamically at runtime via hooks or events. Consumers can query annotations using `TryGetLastAnnotation<T>()` when necessary.
 
-### Definition and Attachment
+### Definition and attachment
 
 ```csharp
 public sealed record PersistenceAnnotation(
@@ -136,19 +136,19 @@ builder.WithAnnotation(new PersistenceAnnotation(
     100));
 ```
 
-### Summary Table
+### Summary table
 
 | Concept | Pattern | Notes |
 |--|--|--|
 | Annotation Type | `public record XAnnotation(...) : IResourceAnnotation` | Public to support dynamic runtime use. |
 | Attach | `builder.WithAnnotation(new XAnnotation(...))` | Adds metadata to resource builder. |
 | Query | `resource.TryGetLastAnnotation<XAnnotation>(out var a)` | Consumers inspect annotations as needed. |
 
-## Custom Value Objects
+## Custom value objects
 
 Custom value objects defer evaluation and allow the framework to discover dependencies between resources.
 
-### Core Interfaces
+### Core interfaces
 
 | Interface | Member | Mode | Purpose |
 |--|--|--|--|
@@ -159,7 +159,7 @@ Custom value objects defer evaluation and allow the framework to discover depend
 - **Implement** `IValueProvider` and `IManifestExpressionProvider` on all structured value types.  
 - **Implement** `IValueWithReferences` only when your type holds resource references.
 
-### Attaching to Resources
+### Attaching to resources
 
 ```csharp
 builder.WithEnvironment(context =>
@@ -190,7 +190,7 @@ public static IResourceBuilder<T> WithEnvironment<T>(
 }
 ```
 
-### Summary Table
+### Summary table
 
 | Concept | Pattern | Purpose |
 |--|--|--|

src/frontend/src/content/docs/architecture/resource-api-patterns.mdx

@@ -12,7 +12,7 @@ Parent-child relationships serve two purposes:
 - **Lifecycle Containment**: The child's execution is tied to the parent's — starting, stopping, and failures cascade from parent to child automatically.
 - **Dashboard Visualization**: The child appears **nested beneath** the parent in dashboards and visualizations, improving readability.
 
-### Lifecycle Containment
+### Lifecycle containment
 
 When a resource implements the `IResourceWithParent` interface, it declares **true containment** — meaning its lifecycle is controlled by its parent:
 
@@ -24,7 +24,7 @@ When a resource implements the `IResourceWithParent` interface, it declares **tr
 A logging sidecar container is tied to the lifecycle of a main application container — if the main app stops, the logging sidecar is also terminated.
 </Aside>
 
-### Visual Grouping (Without Lifecycle Impact)
+### Visual grouping (without lifecycle impact)
 
 Aspire also supports **visual-only parent-child relationships** using the `WithParentRelationship()` method during resource construction.
 
@@ -49,7 +49,7 @@ You must **explicitly declare** relationships by either:
 
 This explicitness ensures developers have full control over resource containment and presentation.
 
-### Real-World Scenarios
+### Real-world scenarios
 
 The following scenarios illustrate how Aspire models parent-child relationships:
 
@@ -59,7 +59,7 @@ The following scenarios illustrate how Aspire models parent-child relationships:
 | Database with admin dashboard | Database container | Admin UI container |
 | Microservice with associated health monitor | API container | Health probe container |
 
-## Values and References
+## Values and references
 
 In Aspire, configuration, connectivity details, and dependencies between distributed resources are modeled using **structured values**. These values capture relationships explicitly—not just as simple strings—making the application graph **portable, inspectable, and evolvable**.
 
@@ -90,7 +90,7 @@ architecture-beta
   epr:L <-- R:frontend
 ```
 
-### Special Case: Endpoints
+### Special case: Endpoints
 
 Normally, resource references form an acyclic graph — **no cycles allowed**. However, **endpoint references are treated specially** and **may form cycles** intentionally.
 
@@ -105,7 +105,7 @@ Endpoints are modeled as **external entities**:
   Endpoints are managed separately from strict dependency edges to allow flexible, real-world service wiring.
 </Aside>
 
-### How the DAG Forms
+### How the DAG forms
 
 Resources connect to each other through:
 
@@ -123,7 +123,7 @@ Each reference **adds an edge** to the graph, allowing Aspire to:
   Aspire **never infers references automatically** — all value flows must be explicitly authored by developers.
 </Aside>
 
-### Structured vs Literal Values
+### Structured vs literal values
 
 Aspire distinguishes between **structured values** and **literal values**.
 
@@ -139,7 +139,7 @@ At publish time and run time:
   **Flattening values too early destroys portability, environment substitution, and cross-platform compatibility.** Aspire delays flattening as long as possible to maintain graph fidelity.
 </Aside>
 
-### Value Providers and Deferred Evaluation
+### Value providers and deferred evaluation
 
 Every structured value type in Aspire implements two fundamental interfaces:
 
@@ -159,7 +159,7 @@ Internally, value providers are attached to environment variables, CLI arguments
   Deferred evaluation guarantees that Aspire applications can be **published safely**, **deployed flexibly**, and **run consistently** across environments.
 </Aside>
 
-### Core Value Types (Expanded)
+### Core value types (expanded)
 
 | Type | Represents | Run Mode | Publish Mode |
 |------|------------|----------|--------------|
@@ -253,7 +253,7 @@ The following patterns are common mistakes when using `ReferenceExpression`:
 | Access `Endpoint.Url` during publish.  | Use `Endpoint.Property(...)` in the expression.         |
 | Mix resolved strings and placeholders. | Keep the entire value inside one `ReferenceExpression`. |
 
-## Endpoint Primitives
+## Endpoint primitives
 
 The `EndpointReference` is the fundamental type used to interact with another resource's endpoint. It provides properties such as:
 
@@ -279,7 +279,7 @@ var endpoint = redis.GetEndpoint("tcp");
 builder.Build().Run();
 ```
 
-### What Does "Allocated" Mean?
+### What does "allocated" mean?
 
 An endpoint is **allocated** when Aspire resolves its runtime values (e.g., `Host`, `Port`, `Url`) during **run mode**. Allocation happens as part of the **startup sequence**, ensuring endpoints are ready for use in local development.
 
@@ -452,7 +452,7 @@ Key members:
 
 `EndpointReferenceExpression` implements the same `IManifestExpressionProvider` / `IValueProvider` pair, so it can be embedded in a `ReferenceExpression` or resolved directly with `GetValueAsync()`.
 
-## Context-Based Endpoint Resolution
+## Context-based endpoint resolution
 
 Aspire resolves endpoints differently based on the relationship between the source and target resources. This ensures proper communication across all environments.