[9.1] Add resource relationship docs

docs/fundamentals/app-host-overview.md

@@ -488,6 +488,37 @@ This logic can easily be inverted to connect to an existing Redis resource when
 > [!IMPORTANT]
 > .NET Aspire provides common APIs to control the modality of resource builders, allowing resources to behave differently based on the execution mode. The fluent APIs are prefixed with `RunAs*` and `PublishAs*`. The `RunAs*` APIs influence the local development (or run mode) behavior, whereas the `PublishAs*` APIs influence the publishing of the resource.
 
+## Resource relationships  
+
+Resource relationships link resources together. Relationships are informational and don't impact an app's runtime behavior. Instead, they're used when displaying details about resources in the dashboard. For example, relationships are visible in the [dashboard's resource details](./dashboard/explore.md#resource-details), and `Parent` relationships control resource nesting on the resources page.
+
+Relationships are automatically created by some app model APIs. For example:
+
+- <xref:Aspire.Hosting.ResourceBuilderExtensions.WithReference*> adds a relationship to the target resource with the type `Reference`.
+- <xref:Aspire.Hosting.ResourceBuilderExtensions.WaitFor*> adds a relationship to the target resource with the type `WaitFor`.
+- Adding a database to a DB container creates a relationship from the database to the container with the type `Parent`.
+
+Relationships can also be explicitly added to the app model using `WithRelationship` and `WithParentRelationship`.
+
+```csharp
+var builder = DistributedApplication.CreateBuilder(args);
+
+var catalogDb = builder.AddPostgres("postgres")
+                       .WithDataVolume()
+                       .AddDatabase("catalogdb");
+
+builder.AddProject<Projects.AspireApp_CatalogDbMigration>("migration")
+       .WithReference(catalogDb)
+       .WithParentRelationship(catalogDb);
+
+builder.Build().Run();
+```
+
+The preceding example uses `WithParentRelationship` to configure `catalogdb` database as the `migration` project's parent. The `Parent` relationship is special because it controls resource nesting on the resource page. In this example, `migration` is nested under `catalogdb`.
+
+> [!NOTE]
+> There's validation for parent relationships to prevent a resource from having multiple parents or creating a circular reference. These configurations can't be rendered in the UI, and the app model will throw an error.
+
 ## See also
 
 - [.NET Aspire integrations overview](integrations-overview.md)