Merge branch 'edge' into reshma/upgradek8s

docs/content/guides/author-apps/application/overview/index.md

@@ -2,38 +2,44 @@
 type: docs
 title: "Overview: Radius applications"
 linkTitle: "Overview"
-description: "Learn about Radius applications"
+description: "Learn about Radius applications and how they bring all of your services, dependencies, and relationships together."
 weight: 100
 categories: "Overview"
 tags: ["applications"]
 ---
 
-## Overview
+<img src="application.png" alt="Diagram of an application" width=350px >
 
-An [application]({{< ref application-graph>}}) is the primary resource that contains all of your services and relationships.
+A Radius application is the primary resource that brings all your "stuff" together. This can include services, dependencies, and relationships. Radius apps give you a single description and view into your entire application, and allow you to deploy and manage it easily.
 
-Because Radius has all the relationships and requirements of an application, deployments and configurations are simplified. Developers no longer need to specify all the identity, networking, or other configuration that is normally required, and operators don't need to write custom deployment scripts.
+## Add portability to your application
 
-For example, if you want a container to read from an Azure Storage Account without using Radius, this normally requires creating managed identities, RBAC roles, identity federation, Kubernetes service accounts, and more. With Radius, developers can define a single [connection]({{< ref "guides/author-apps/containers/overview#connections" >}}) from their container to a Storage Account, and Radius sets up all the required configuration automatically.
+Radius applications are designed to be cloud and platform agnostic. This means that you can define your application once, and deploy it to any cloud or platform that Radius supports. This allows you to easily move your application between clouds, or even between cloud and on-premises environments. Developers can define their requirements and dependencies (_Redis, SQL, Dapr, etc._) and operators can define the [environments]({{< ref "guides/deploy-apps/environments/overview" >}}) and [Recipes]({{< ref "guides/recipes/overview" >}}) that bind those requirements to the appropriate cloud resources.
 
-<img src="graph-automation.png" alt="A diagram showing a connection from a Radius container to an Azure storage account resulting in managed identities, role-based access control, and CSI drivers." width=600px >
+<img src="portable-resources.png" alt="Diagram of portable resources binding to different clouds" width=600px >
 
-## Extensions
+Learn more about portable resources in the [portable resources docs]({{< ref "guides/author-apps/portable-resources/overview" >}}) and [Dapr docs]({{< ref "guides/author-apps/dapr/overview" >}})
+
+## Customize your application with extensions
 
 Extensions allow you to customize how resources are generated or customized as part of deployment.
 
 ### Kubernetes Namespace extension
 
-The Kubernetes namespace extension allows you to customize how all of the resources within your application generate Kubernetes resources. See the [Kubernetes mapping guide]({{< ref kubernetes-mapping >}}) for more information on namespace mapping behavior
+The Kubernetes namespace extension allows you to customize how all of the resources within your application generate Kubernetes resources. See the [Kubernetes mapping guide]({{< ref kubernetes-mapping >}}) for more information on namespace mapping behavior.
 
 ### Kubernetes Metadata extension
 
-The [Kubernetes Metadata extension]({{< ref "guides/operations/kubernetes/kubernetes-metadata">}}) enables you set and cascade Kubernetes metadata such as labels and Annotations on all the Kubernetes resources defined with in your Radius application 
+The [Kubernetes Metadata extension]({{< ref "guides/operations/kubernetes/kubernetes-metadata">}}) enables you set and cascade Kubernetes metadata such as labels and Annotations on all the Kubernetes resources defined with in your Radius application.
 
-## Resource schema 
+## Query and understand your application with the Radius Application Graph
+
+Radius applications are more than just client-side configuration and automation, they also provide a server-side graph of your application. This graph can be queried and used to understand your application, and can be used to power other Radius features and custom tooling. Refer to the [API concept docs]({{< ref "api-concept" >}}) and [Postman How-To guide]({{< ref "guides/operations/control-plane/howto-postman" >}}) for more information on how to query the application graph.
 
-- [Application schema]({{< ref application-schema >}})
+<img src="app-graph.png" alt="Diagram of the application graph" width=500px >
+
+## Resource schema 
 
-## Further reading
+Refer to the [application schema docs]({{< ref application-schema >}}) for more information on how to define an application.
 
-Refer to the [applications]({{< ref "/tags/applications" >}}) tag for more guides on the application resource.
+{{< button text="📄 Application schema" page="application-schema" >}}

docs/content/guides/author-apps/dapr/_index.md

@@ -0,0 +1,7 @@
+---
+type: docs
+title: "Dapr building blocks"
+linkTitle: "Dapr"
+description: "Easily leverage Dapr building blocks in your application for code and infrastructure portability"
+weight: 500
+---

docs/content/guides/author-apps/dapr/index.md → docs/content/guides/author-apps/dapr/overview/index.md

@@ -1,11 +1,10 @@
 ---
 type: docs
-title: "Dapr building blocks"
-linkTitle: "Dapr"
+title: "Overview: Dapr building blocks"
+linkTitle: "Overview"
 description: "Easily leverage Dapr building blocks in your application for code and infrastructure portability"
-weight: 500
-slug: "dapr"
-categories: "Concept"
+weight: 100
+categories: "Overview"
 tags: ["Dapr"]
 ---