Skip to content
Closed
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion docs/content/_index.md
Original file line number Diff line number Diff line change
Expand Up @@ -16,7 +16,7 @@ Radius is a cloud native application platform. It enables developers and IT ope
[**Learn more**](https://radapp.io/)
{{% /alert %}}

{{< button text="Get started with Radius 🚀" page="getting-started" color="success" size="btn-lg" >}}
{{< button text="Radius Quick Start 🚀" page="quick-start" color="success" size="btn-lg" >}}

{{< cardpane >}}
{{< card header="**🎓 Tutorials**" footer="[**View available tutorials →**]({{< ref tutorials >}})" >}}
Expand Down
2 changes: 1 addition & 1 deletion docs/content/concepts/_index.md
Original file line number Diff line number Diff line change
Expand Up @@ -3,5 +3,5 @@ type: docs
title: "Radius concepts"
linkTitle: "Concepts"
description: "Learn about Radius background, core concepts, and architecture"
weight: 80
weight: 25
---
Original file line number Diff line number Diff line change
@@ -1,15 +1,11 @@
---
type: docs
title: Radius Application Graph
linkTitle: Application graph
description: Learn how the Radius application graph allows you to model your entire application
weight: 200
toc_hide: true
hide_summary: true
title: "Application and Resources"
linkTitle: "Application and Resources"
description: "Learn about Radius Application"
weight: 400
---

<!-- DISABLE_ALGOLIA -->

## Radius Applications

Radius offers an [application resource]({{< ref "guides/author-apps/application" >}}) which teams can use to define and deploy their entire application, including all of the compute, relationships, and infrastructure that make up the application. Since the graph of relationships between deployed resources is much more descriptive than a basic list of resources, the Radius Application graph can automate complex deployment tasks and enable rich visualization experiences.
Expand All @@ -28,11 +24,11 @@ The Radius Application graph also allows your application to be self-documenting

{{< image src="dashboard.png" alt="A mockup of a dashboard UI showing an application, its resources, and its connections" width=700px >}}

> **Note:** A Radius dashboard is still on the roadmap, but in the meantime you can use the [Radius API]({{< ref "/concepts/technical/api" >}}) to build your own visual experiences today.
> **Note:** A Radius dashboard is still on the roadmap, but in the meantime you can use the Radius API to build your own visual experiences today.

## Mine the app graph API

The Radius Application graph is also exposed as an API, allowing you to build your own visualizations, workflows, and more on top of Radius. Learn more in the [API docs]({{< ref "/concepts/technical/api" >}}).
The Radius Application graph is also exposed as an API, allowing you to build your own visualizations, workflows, and more on top of Radius. Learn more in the API docs.

For example, I can get the status of my `frontend` container, and get its definition and its connections to other resources:

Expand Down Expand Up @@ -75,4 +71,4 @@ GET /planes/radius/local/resourceGroups/default/providers/Applications.Core/cont

Now that you have an understanding of the Radius app graph, learn how you can deploy Radius applications to prepared landing zones with Radius Environments:

{{< button text="Radius Environments" page="/concepts/why-radius/collaboration" color="success" >}}

4 changes: 2 additions & 2 deletions docs/content/concepts/faq/index.md
Original file line number Diff line number Diff line change
Expand Up @@ -14,7 +14,7 @@ Currently yes. Although Radius is architected to run on any platform, today Kube

### Can I incrementally adopt, or "try out" Radius?

Yes. The easiest way to add Radius to an existing application is through [Radius annotations]({{< ref "/tutorials/tutorial-add-radius#step-3-add-radius-to-the-guestbook-application" >}}). Simply add the annotations to your existing Helm chart or Kubernetes YAML and you can use the Radius app graph, connections, and Recipes. [Try the tutorial]({{< ref "/tutorials/tutorial-add-radius" >}}) to learn more.
Yes. The easiest way to add Radius to an existing application is through [Radius annotations]({{< ref "/reference/samples/tutorial-add-radius#step-3-add-radius-to-the-guestbook-application" >}}). Simply add the annotations to your existing Helm chart or Kubernetes YAML and you can use the Radius app graph, connections, and Recipes. [Try the tutorial]({{< ref "/reference/samples/tutorial-add-radius" >}}) to learn more.

### Do I have to self-host Radius? Is there a managed service for Radius?

Expand Down Expand Up @@ -188,7 +188,7 @@ Where .NET Aspire is focused on the .NET experience from moving from local devel

### How does Radius compare to Azure Developer CLI (azd)?

The [Azure Developer CLI](https://learn.microsoft.com/en-us/azure/developer/azure-developer-cli/) is an open-source tool that provides developer-friendly commands to simplify the process of building, deploying, and managing Azure resources. While both azd and Radius are geared towards the development and deployment workflows, the most apparent difference is that azd can be only be used to manage Azure resources, whereas Radius supports multiple cloud providers. Radius also introduces a way to model (and not just deploy) entire applications and automate these through [Recipes]({{< ref "guides/recipes/overview">}}), which allows for complete [separation of concerns]({{< ref "collaboration" >}}) between operators and developers. With azd, even though developers may leverage CLI templates to deploy infrastructure, they still need to understand the underlying infrastructure and how to connect to it.
The [Azure Developer CLI](https://learn.microsoft.com/en-us/azure/developer/azure-developer-cli/) is an open-source tool that provides developer-friendly commands to simplify the process of building, deploying, and managing Azure resources. While both azd and Radius are geared towards the development and deployment workflows, the most apparent difference is that azd can be only be used to manage Azure resources, whereas Radius supports multiple cloud providers. Radius also introduces a way to model (and not just deploy) entire applications and automate these through [Recipes]({{< ref "guides/recipes/overview">}}), which allows for complete separation of concerns between operators and developers. With azd, even though developers may leverage CLI templates to deploy infrastructure, they still need to understand the underlying infrastructure and how to connect to it.

### How does Radius compare to KubeVela?

Expand Down
Original file line number Diff line number Diff line change
@@ -1,7 +1,7 @@
---
type: docs
title: "Introduction: Why did we create Radius?"
linkTitle: "Introduction"
title: "Radius Overview"
linkTitle: "Radius Overview"
description: "Learn about why we created Radius and how it can help you"
weight: 100
categories: "Concept"
Expand Down
Original file line number Diff line number Diff line change
@@ -1,9 +1,9 @@
---
type: docs
title: "Concept: Collaboration in Radius"
linkTitle: "Dev + ops collaboration"
description: "Learn how Radius Environments and Recipes support collaboration between platform engineers, application developers, and IT operators."
weight: 300
title: "Resource Types"
linkTitle: "Resource Types"
description: "Learn how Radius Resource Types support collaboration between platform engineers, application developers, and IT operators."
weight: 200
aliases:
- /concepts/collaboration-concept/
---
Expand Down
7 changes: 0 additions & 7 deletions docs/content/concepts/technical/_index.md

This file was deleted.

Loading
Loading