diff --git a/.gitattributes b/.gitattributes index 307cd13c4..2ef6ae16c 100644 --- a/.gitattributes +++ b/.gitattributes @@ -6,3 +6,9 @@ # images are binary *.png binary + +# MS Office documents are binary +*.pptx binary +*.potx binary +*.docx binary +*.dotx binary diff --git a/.github/config/en-custom.txt b/.github/config/en-custom.txt index ec27507ed..a1cd53821 100644 --- a/.github/config/en-custom.txt +++ b/.github/config/en-custom.txt @@ -1224,3 +1224,5 @@ natively NuGet KubeVela GigaOm +potx +href diff --git a/.github/workflows/website.yaml b/.github/workflows/website.yaml index 3080fa00b..498e49e6c 100644 --- a/.github/workflows/website.yaml +++ b/.github/workflows/website.yaml @@ -58,6 +58,11 @@ jobs: run : | mkdir -p ./docs/static/swagger cp -r ./radius/swagger ./docs/static/ + - name: Override git_branch for PR + if: github.event_name == 'pull_request' + run: | + # Within docs/config.toml, replace the line that starts with "github_branch" with "github_branch: $GITHUB_HEAD_REF" + sed -i "s|github_branch = .*|github_branch = \"$GITHUB_HEAD_REF\"|" docs/config.toml - name: Build Hugo Site run: | cd docs diff --git a/docs/content/community/contributing/overview/index.md b/docs/content/community/contributing/overview/index.md index f4fcc0d05..eceae304a 100644 --- a/docs/content/community/contributing/overview/index.md +++ b/docs/content/community/contributing/overview/index.md @@ -11,8 +11,9 @@ We welcome contributions to the Radius! Check out the following table to learn | Component | Description | Contribution guides | |-----------|-------------|---------------------| | **`rad` CLI** | Deploys and manages Radius resources | [radius-project/radius](https://github.com/radius-project/radius/blob/main/docs/contributing/contributing-code/contributing-code-cli/running-rad-cli.md) | -| **Bicep** | Language and tools which includes the application model as a set of types. Will eventually be merged with https://github.com/azure/bicep | [radius-project/bicep](https://github.com/radius-project/bicep/blob/radius-compiler/CONTRIBUTING.md) | -| **ARM Deployment Engine** | Processes the output of the Bicep compiler and deploys resources. | [radius-project/deployment-engine](https://github.com/radius-project/deployment-engine/blob/main/CONTRIBUTING.md) | +| **Bicep** | Language and tools which includes the application model as a set of types which will eventually be merged with https://github.com/azure/bicep | [radius-project/bicep](https://github.com/radius-project/bicep/blob/radius-compiler/CONTRIBUTING.md) | +| **ARM Deployment Engine** | Processes the output of the Bicep compiler and deploys resources | [radius-project/deployment-engine](https://github.com/radius-project/deployment-engine/blob/main/CONTRIBUTING.md) | | **Radius Control Plane** | Implements operations on the application model as a sequence of resource management operations | [radius-project/radius](https://github.com/radius-project/radius/tree/main/docs/contributing/contributing-code) | -| **Templates** | Deployable starter templates for getting up and running with Radius | [radius-project/templates](https://github.com/radius-project/templates) | +| **Dashboard** | The frontend experience for Radius | [radius-project/dashboard](https://github.com/radius-project/dashboard/blob/main/CONTRIBUTING.md) | +| **Recipes** | Commonly used [Recipe](https://docs.radapp.dev/recipes) templates for Radius Environments | [radius-project/recipes](https://github.com/radius-project/recipes/blob/main/CONTRIBUTING.md) | | **Docs** | Documentation for Radius | [Contributing to docs]({{< ref contributing-docs >}}) | diff --git a/docs/content/community/media-coverage.md b/docs/content/community/media-coverage.md index a9f7f2f83..5e2b3fab8 100644 --- a/docs/content/community/media-coverage.md +++ b/docs/content/community/media-coverage.md @@ -3,7 +3,7 @@ type: docs title: "Radius press coverage and media links" linkTitle: "Press/media coverage" description: "Learn about Radius through press articles, blog posts, presentation and other coverage of Radius" -weight: 400 +weight: 500 --- ## Blog posts @@ -13,9 +13,9 @@ weight: 400 | [The Microsoft Azure Incubations Team launches Radius, a new open application platform for the cloud](https://azure.microsoft.com/en-us/blog/the-microsoft-azure-incubations-team-launches-radius-a-new-open-application-platform-for-the-cloud/) | Microsoft Azure Blog | Oct 18, 2023 | | [Enabling developer collaboration with Radius](https://cloudblogs.microsoft.com/opensource/2023/10/18/enabling-developer-collaboration-with-radius/) | Microsoft Open Source Blog | Oct 18, 2023 | -Ongoing blog posts can be found at [Radius Blog](https://blog.radapp.io) +Ongoing blog posts can be found at [Radius Blog](https://blog.radapp.io). -## Videos +## Presentations | Video | Event | Date | |-------|-------|------| @@ -23,6 +23,8 @@ Ongoing blog posts can be found at [Radius Blog](https://blog.radapp.io) | [Introducing Radius - Open at Microsoft ](https://www.youtube.com/watch?v=mT_NWFnYn0A)| Open at Microsoft | Nov 7, 2023 | | [Mark Russinovich at the Linux Foundation Member Summit](https://aka.ms/radius-lfms)|Linux Foundation Member Summit | Oct 24, 2023 | +Want to give you own presentation? Check out the [Give a Radius Presentation]({{< ref presentations >}}) page. + ## Press articles | Article Title | Media Source | Date | diff --git a/docs/content/community/presentations/index.md b/docs/content/community/presentations/index.md new file mode 100644 index 000000000..03a2d3a1e --- /dev/null +++ b/docs/content/community/presentations/index.md @@ -0,0 +1,26 @@ +--- +type: docs +title: "Give a Radius presentation" +linkTitle: "Presentations" +description: "Learn how to give a Radius presentation, with downloadable slides and assets" +weight: 400 +--- + +We welcome community members giving presentations on Radius and spreading the word about all the awesome Radius features! + +## Slides + +We offer a template PowerPoint file to get started: + +Download the Radius PowerPoint template + +## Giving a Radius presentation + +1. Begin by downloading the [Radius Presentation Deck](https://github.com/radius-project/docs/raw/{{< param github_branch >}}/presentation-pack/Radius.potx). This contains slides needed to give a Radius presentation. +1. Refer to the Radius [presentation pack directory](https://github.com/radius-project/docs/tree/{{< param github_branch >}}/presentation-pack) for any diagrams or images you need to create. +1. Next, review the docs to make sure you understand the [concepts]({{< ref concepts >}}). +1. Use the Radius [getting started guide]({{< ref getting-started >}}) and [samples repo](https://github.com/radius-project/samples) to show demos of how to use Radius. + +## Previous presentations + +Refer to the [Radius press coverage and media links]({{< ref media-coverage >}}) page for a list of previous presentations. diff --git a/docs/content/concepts/faq/index.md b/docs/content/concepts/faq/index.md index 2c892ae8d..31e064f32 100644 --- a/docs/content/concepts/faq/index.md +++ b/docs/content/concepts/faq/index.md @@ -188,8 +188,8 @@ 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-concept" >}}) 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]({{< 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. ### How does Radius compare to KubeVela? -[KubeVela](https://kubevela.io/) is an open-source platform that provides a higher level of abstraction for application deployments. Similar to Radius, it allows developers to define applications and their components, deployment across cloud providers or on-prem, and automated infrastructure provisioning with pre-defined templates. However, unlike Radius, KubeVela does not allow for modeling of connections between resources to set environment variables, configure access credentials, and more that make it simpler for developers to deploy and access resources. \ No newline at end of file +[KubeVela](https://kubevela.io/) is an open-source platform that provides a higher level of abstraction for application deployments. Similar to Radius, it allows developers to define applications and their components, deployment across cloud providers or on-prem, and automated infrastructure provisioning with pre-defined templates. However, unlike Radius, KubeVela does not allow for modeling of connections between resources to set environment variables, configure access credentials, and more that make it simpler for developers to deploy and access resources. diff --git a/docs/content/concepts/overview/cloud-apps-radius.png b/docs/content/concepts/overview/cloud-apps-radius.png deleted file mode 100644 index 3cda511d3..000000000 Binary files a/docs/content/concepts/overview/cloud-apps-radius.png and /dev/null differ diff --git a/docs/content/concepts/overview/cloud-apps-today.png b/docs/content/concepts/overview/cloud-apps-today.png deleted file mode 100644 index 8ec707b95..000000000 Binary files a/docs/content/concepts/overview/cloud-apps-today.png and /dev/null differ diff --git a/docs/content/concepts/overview/environments.png b/docs/content/concepts/overview/environments.png deleted file mode 100644 index 75aae0411..000000000 Binary files a/docs/content/concepts/overview/environments.png and /dev/null differ diff --git a/docs/content/concepts/overview/index.md b/docs/content/concepts/overview/index.md deleted file mode 100644 index 50d5a1d9f..000000000 --- a/docs/content/concepts/overview/index.md +++ /dev/null @@ -1,91 +0,0 @@ ---- -type: docs -title: Overview for Radius -linkTitle: Overview -description: Learn how Radius fits into the app development landscape and it's long-term vision -weight: 100 -toc_hide: true ---- - -## Building cloud-native apps is too difficult today - -App teams today struggle to model and deploy their applications. Complex architectures, cross-platform portability requirements, and org-level best-practices all make it difficult to not only model and deploy, but also maintain and troubleshoot large applications. - -Apps today are modeled and deployed with Dockerfiles, Kubernetes custom resources (CRDs), Helm charts, and infrastructure-as-code templates, with scripts to glue it all together. Plus, the range of infrastructure types (cloud, on-premises, serverless) can double or triple the work as teams figure out how to move apps between platforms. - -{{< image alt="Diagram showing all of the technologies needed to model an application today" src="cloud-apps-today.png" width="600px" >}} - -Once deployed, teams don't have a way to view and manage apps holistically. Instead, they're drowning in lists of disjointed resources. - -What's missing is a way to collapse the entire concept of an application into a single entity so it can be deployed, managed, and scaled easily. - -## Radius empowers teams to focus on their apps - -### Build a unified concept of your application - -At the heart of Radius is a new **application resource**, with an accompanying set of resources and abstractions to describe your app's requirements and capabilities. - -{{< image alt="Diagram showing modeling an app with Radius" src="cloud-apps-radius.png" width="600px" >}} - -These new resources form the [**Radius app model**]({{< ref application-graph>}}), which allow you to: - -- Visualize the entire application, including its dependencies and relationships -- Investigate cross-app health and diagnostics, including dependencies and connections -- Identify ownership and locate artifacts -- Support handoff between teams as the app matures - -The result is no longer just a flat list of resources - it's a fully codified abstraction of how the services and infrastructure relate to each other: - -{{< image alt="Diagram showing Radius Application in the Azure portal" src="ui-mockup-basic.png" width="700px" >}}
- -### Drastically reduce infra ops time - -[App environments]({{< ref collaboration-concept >}}) are landing zones for applications. They are the place where you can deploy, manage, and scale your apps. - -{{< image alt="Diagram showing Radius Environments" src="environments.png" width="600px" >}} - -Environments allow you to: - -- Iterate quickly in an environment running locally, then scale that same app up in a production environment -- Stamp out versions of the app to the edge, to multiple geos, or even to multiple clouds -- Follow best practices to be naturally secure by default, even with many teams working together -- Easily layer IT policies across an app (access, backup, ...) - -### Model applications as code - -With the Radius app model, teams can easily codify and share pieces of an application. For example, a database owned by one team can seamlessly connect to a container with app code owned by a second team. - -{{< tabs Bicep >}} - -{{< codetab >}} -{{< rad file="snippets/appmodel-concept.bicep" embed=true marker="//SNIPPET" replace-key-container="//CONTAINER" replace-value-container="container: {...}" replace-key-properties="//PROPERTIES" replace-value-properties="properties: {...}" >}} -{{< /codetab >}} - -{{< /tabs >}} - -Radius uses the [Bicep language]({{< ref bicep >}}) as its file-format and structure. It offers: - -- A high quality authoring experience with modules, loops, parametrization, and templating -- ARM Deployment Stacks as the declarative deployment/rollback mechanism -- Ability to punch through abstractions to platform when necessary -- Extensions to work with other providers (e.g. Kubernetes, Azure Active Directory, etc.) - -## Platform strategy - -Radius aims to support all hosting platform types - from hyperscale cloud, to self-hosted Kubernetes on the edge, to IoT and edge devices. - -{{< image alt="Diagram showing Radius platforms" src="platforms.png" width="800px" >}} - -### Application portability - -The Radius app model is designed to be portable across all Radius-supported platforms. Combined with portable resources and other frameworks such as [Dapr](https://dapr.io/), teams can write their apps once and deploy to any Radius-enabled platform in minutes. - -### Consistent tooling - -As teams onboard to Radius and begin deploying across platforms, the tooling and experiences are consistent everywhere. The [rad CLI]({{< ref cli >}}) works across every platform and environment. This allows teams to easily scale across platforms and be productive everywhere. - -## Next step - -Now that you have an overview of Radius, learn more about the Radius app model: - -{{< button text="Learn about the Radius Application model" page="application-graph" size="btn-lg" color="success" >}} \ No newline at end of file diff --git a/docs/content/concepts/overview/platforms.png b/docs/content/concepts/overview/platforms.png deleted file mode 100644 index c09a31623..000000000 Binary files a/docs/content/concepts/overview/platforms.png and /dev/null differ diff --git a/docs/content/concepts/overview/snippets/appmodel-concept.bicep b/docs/content/concepts/overview/snippets/appmodel-concept.bicep deleted file mode 100644 index 3d8af9cc8..000000000 --- a/docs/content/concepts/overview/snippets/appmodel-concept.bicep +++ /dev/null @@ -1,42 +0,0 @@ -import radius as radius - -param environment string - -//SNIPPET -// Infrastructure operators provide database to the application team -param databaseId string - -// Define application -resource app 'Applications.Core/applications@2023-10-01-preview' = { - name: 'myapp' - //PROPERTIES - properties: { - environment: environment - } - //PROPERTIES -} - -// Define container resource to run app code -resource frontend 'Applications.Core/containers@2023-10-01-preview' = { - name: 'frontend' - properties: { - application: app.id - //CONTAINER - container: { - image: 'myregistry/frontend:latest' - ports: { - web: { - containerPort: 3000 - } - } - } - //CONTAINER - // Connect container to database - connections: { - itemstore: { - source: databaseId - } - } - } -} -//SNIPPET diff --git a/docs/content/concepts/overview/ui-mockup-basic.png b/docs/content/concepts/overview/ui-mockup-basic.png deleted file mode 100644 index 0408261ba..000000000 Binary files a/docs/content/concepts/overview/ui-mockup-basic.png and /dev/null differ diff --git a/docs/content/concepts/overview/ui-mockup-list.png b/docs/content/concepts/overview/ui-mockup-list.png deleted file mode 100644 index f6be23987..000000000 Binary files a/docs/content/concepts/overview/ui-mockup-list.png and /dev/null differ diff --git a/docs/content/concepts/technical/_index.md b/docs/content/concepts/technical/_index.md new file mode 100644 index 000000000..82ff2f824 --- /dev/null +++ b/docs/content/concepts/technical/_index.md @@ -0,0 +1,7 @@ +--- +type: docs +title: "Technical concepts in Radius" +linkTitle: "Technical concepts" +description: "Learn about the architecture, API design, and other technical concepts of Radius" +weight: 300 +--- \ No newline at end of file diff --git a/docs/content/concepts/api-concept/index.md b/docs/content/concepts/technical/api/index.md similarity index 99% rename from docs/content/concepts/api-concept/index.md rename to docs/content/concepts/technical/api/index.md index 62a34e1d0..432bc4630 100644 --- a/docs/content/concepts/api-concept/index.md +++ b/docs/content/concepts/technical/api/index.md @@ -1,10 +1,12 @@ --- type: docs title: Radius API -linkTitle: API +linkTitle: Radius API description: Learn about the Radius API -weight: 500 +weight: 200 categories: "Concept" +aliases: + - /concepts/api-concept/ --- ## Overview diff --git a/docs/content/concepts/architecture-concept/controlplane-services-generic.png b/docs/content/concepts/technical/architecture/controlplane-services-generic.png similarity index 100% rename from docs/content/concepts/architecture-concept/controlplane-services-generic.png rename to docs/content/concepts/technical/architecture/controlplane-services-generic.png diff --git a/docs/content/concepts/architecture-concept/flow-deploy.png b/docs/content/concepts/technical/architecture/flow-deploy.png similarity index 100% rename from docs/content/concepts/architecture-concept/flow-deploy.png rename to docs/content/concepts/technical/architecture/flow-deploy.png diff --git a/docs/content/concepts/architecture-concept/flow-list-apps.png b/docs/content/concepts/technical/architecture/flow-list-apps.png similarity index 100% rename from docs/content/concepts/architecture-concept/flow-list-apps.png rename to docs/content/concepts/technical/architecture/flow-list-apps.png diff --git a/docs/content/concepts/architecture-concept/flow-terraform.png b/docs/content/concepts/technical/architecture/flow-terraform.png similarity index 100% rename from docs/content/concepts/architecture-concept/flow-terraform.png rename to docs/content/concepts/technical/architecture/flow-terraform.png diff --git a/docs/content/concepts/architecture-concept/index.md b/docs/content/concepts/technical/architecture/index.md similarity index 98% rename from docs/content/concepts/architecture-concept/index.md rename to docs/content/concepts/technical/architecture/index.md index f5f51e1ad..a1bbd41ee 100644 --- a/docs/content/concepts/architecture-concept/index.md +++ b/docs/content/concepts/technical/architecture/index.md @@ -3,10 +3,12 @@ type: docs title: Radius architecture linkTitle: Architecture description: Learn about the architecture of the Radius API and services -weight: 600 +weight: 100 categories: "Concept" tags: ["control plane"] slug: 'architecture' +aliases: + - /concepts/architecture-concept/ --- ## Overview @@ -15,7 +17,7 @@ Radius provides an HTTP-based API and supporting tools that can deploy and manag This page serves as documentation about the overall architecture of Radius to help educate contributors to the project or any user who wants a deeper understanding of the system and its capabilities. -**Prerequisite:** Read the [API docs]({{< ref api-concept >}}) to understand the terminology and structure of the Radius API. +**Prerequisite:** Read the [API docs]({{< ref "/concepts/technical/api" >}}) to understand the terminology and structure of the Radius API. ## Design motivations for Radius diff --git a/docs/content/concepts/architecture-concept/ucp-selfhosted-imperative.png b/docs/content/concepts/technical/architecture/ucp-selfhosted-imperative.png similarity index 100% rename from docs/content/concepts/architecture-concept/ucp-selfhosted-imperative.png rename to docs/content/concepts/technical/architecture/ucp-selfhosted-imperative.png diff --git a/docs/content/concepts/architecture-concept/ucp-selfhosted.png b/docs/content/concepts/technical/architecture/ucp-selfhosted.png similarity index 100% rename from docs/content/concepts/architecture-concept/ucp-selfhosted.png rename to docs/content/concepts/technical/architecture/ucp-selfhosted.png diff --git a/docs/content/concepts/why-radius/_index.md b/docs/content/concepts/why-radius/_index.md new file mode 100644 index 000000000..f41d1e4f4 --- /dev/null +++ b/docs/content/concepts/why-radius/_index.md @@ -0,0 +1,7 @@ +--- +type: docs +title: "Why Radius?" +linkTitle: "Why Radius?" +description: "Learn about why we created Radius and how it can help you" +weight: 100 +--- \ No newline at end of file diff --git a/docs/content/concepts/application-graph/application.png b/docs/content/concepts/why-radius/application-graph/application.png similarity index 100% rename from docs/content/concepts/application-graph/application.png rename to docs/content/concepts/why-radius/application-graph/application.png diff --git a/docs/content/concepts/application-graph/dashboard.png b/docs/content/concepts/why-radius/application-graph/dashboard.png similarity index 100% rename from docs/content/concepts/application-graph/dashboard.png rename to docs/content/concepts/why-radius/application-graph/dashboard.png diff --git a/docs/content/concepts/application-graph/index.md b/docs/content/concepts/why-radius/application-graph/index.md similarity index 91% rename from docs/content/concepts/application-graph/index.md rename to docs/content/concepts/why-radius/application-graph/index.md index 7ceb8bd08..a64a0ce23 100644 --- a/docs/content/concepts/application-graph/index.md +++ b/docs/content/concepts/why-radius/application-graph/index.md @@ -7,6 +7,8 @@ weight: 200 toc_hide: true --- + + ## 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. @@ -25,11 +27,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 api-concept >}}) 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]({{< ref "/concepts/technical/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 api-concept >}}). +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" >}}). For example, I can get the status of my `frontend` container, and get its definition and its connections to other resources: @@ -72,4 +74,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="collaboration-concept" color="success" >}} +{{< button text="Radius Environments" page="/concepts/why-radius/collaboration" color="success" >}} diff --git a/docs/content/concepts/application-graph/list-to-graph.png b/docs/content/concepts/why-radius/application-graph/list-to-graph.png similarity index 100% rename from docs/content/concepts/application-graph/list-to-graph.png rename to docs/content/concepts/why-radius/application-graph/list-to-graph.png diff --git a/docs/content/concepts/collaboration-concept/index.md b/docs/content/concepts/why-radius/collaboration/index.md similarity index 99% rename from docs/content/concepts/collaboration-concept/index.md rename to docs/content/concepts/why-radius/collaboration/index.md index 862b94aa7..2cfac0105 100644 --- a/docs/content/concepts/collaboration-concept/index.md +++ b/docs/content/concepts/why-radius/collaboration/index.md @@ -1,10 +1,11 @@ --- type: docs title: "Concept: Collaboration in Radius" -linkTitle: "Collaboration" +linkTitle: "Dev + ops collaboration" description: "Learn how Radius Environments and Recipes support collaboration between platform engineers, application developers, and IT operators." weight: 300 -slug: collaboration +aliases: + - /concepts/collaboration-concept/ --- ## What we heard diff --git a/docs/content/concepts/why-radius-concept/index.md b/docs/content/concepts/why-radius/introduction/index.md similarity index 97% rename from docs/content/concepts/why-radius-concept/index.md rename to docs/content/concepts/why-radius/introduction/index.md index b02491ea9..61892c0bf 100644 --- a/docs/content/concepts/why-radius-concept/index.md +++ b/docs/content/concepts/why-radius/introduction/index.md @@ -1,10 +1,12 @@ --- type: docs -title: "Concept: Why Radius?" -linkTitle: "Why Radius?" -description: "Describes the motivations for creating Radius." +title: "Introduction: Why did we create Radius?" +linkTitle: "Introduction" +description: "Learn about why we created Radius and how it can help you" weight: 100 categories: "Concept" +aliases: + - /concepts/why-radius-concept/ --- ## Our starting point diff --git a/docs/content/concepts/multi-cloud-concept/index.md b/docs/content/concepts/why-radius/multi-cloud/index.md similarity index 98% rename from docs/content/concepts/multi-cloud-concept/index.md rename to docs/content/concepts/why-radius/multi-cloud/index.md index 1cffcd45a..b589be7eb 100644 --- a/docs/content/concepts/multi-cloud-concept/index.md +++ b/docs/content/concepts/why-radius/multi-cloud/index.md @@ -1,10 +1,12 @@ --- type: docs title: "Concept: Open-source and multi-cloud" -linkTitle: Open-source and multi-cloud +linkTitle: Open-source & multi-cloud description: For many enterprises, their cloud native computing strategy involves using multiple cloud providers. Open-source projects, like Kubernetes, help ensure these enterprises achieve their strategy. As a result, Radius was designed to be open-source and multi-cloud from the start. -weight: 100 +weight: 200 categories: "Concept" +aliases: + - /concepts/multi-cloud-concept/ --- ## Organizations are increasingly multi-cloud diff --git a/docs/content/getting-started/index.md b/docs/content/getting-started/index.md index c9b17ed5e..8551692ea 100644 --- a/docs/content/getting-started/index.md +++ b/docs/content/getting-started/index.md @@ -173,11 +173,19 @@ Resources: redis-r5tcrra3d7uh6 (kubernetes: core/Service) ``` -## Recap and next steps +## 8. Cleanup -It's easy to build on the default app and add more resources to the app. +To delete your app, run the [rad app delete]({{< ref rad_application_delete >}}) command to cleanup the app and its resources, including the Recipe resources: -To delete your app, see [rad app delete]({{< ref rad_application_delete >}}). +```bash +rad app delete demo -y +``` + +## Next steps + +Now that you've run your first Radius app, you can learn more about Radius by reading the following guides: + +- [Tutorials]({{< ref tutorials >}}) - Learn how to build and deploy a variety of applications with Radius
{{< button text="Next step: Radius Tutorials" page="tutorials" >}} diff --git a/docs/content/guides/author-apps/application/overview/index.md b/docs/content/guides/author-apps/application/overview/index.md index 339d9d0c7..964985fe0 100644 --- a/docs/content/guides/author-apps/application/overview/index.md +++ b/docs/content/guides/author-apps/application/overview/index.md @@ -34,7 +34,7 @@ The [Kubernetes Metadata extension]({{< ref "guides/operations/kubernetes/kubern ## 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. +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 "/concepts/technical/api" >}}) and [Postman How-To guide]({{< ref "guides/operations/control-plane/howto-postman" >}}) for more information on how to query the application graph. {{< image src="app-graph.png" alt="Diagram of the application graph" width=500px >}} diff --git a/docs/content/guides/author-apps/aws/howto-aws-resources/index.md b/docs/content/guides/author-apps/aws/howto-aws-resources/index.md index d002241dc..95483fa77 100644 --- a/docs/content/guides/author-apps/aws/howto-aws-resources/index.md +++ b/docs/content/guides/author-apps/aws/howto-aws-resources/index.md @@ -44,7 +44,7 @@ Run [`rad init --full`]({{< ref rad_init >}}) to initialize a new environment in rad init --full ``` -Follow the prompts to install the [control plane services]({{< ref architecture-concept >}}), create an [environment resource]({{< ref "/guides/deploy-apps/environments" >}}), and create a [local workspace]({{< ref workspaces >}}). You will be asked for: +Follow the prompts to install the [control plane services]({{< ref "/concepts/technical/architecture" >}}), create an [environment resource]({{< ref "/guides/deploy-apps/environments" >}}), and create a [local workspace]({{< ref workspaces >}}). You will be asked for: - **Namespace** - When an application is deployed, this is the namespace where your containers and other Kubernetes resources will be run. By default, this will be in the `default` namespace. {{% alert title="💡 About namespaces" color="success" %}} When you initialize a Radius Kubernetes environment, Radius installs the control plane resources within the `radius-system` namespace in your cluster, separate from your applications. The namespace specified in this step will be used for your application deployments. diff --git a/docs/content/guides/author-apps/portable-resources/overview/index.md b/docs/content/guides/author-apps/portable-resources/overview/index.md index c1deb6413..5070a072f 100644 --- a/docs/content/guides/author-apps/portable-resources/overview/index.md +++ b/docs/content/guides/author-apps/portable-resources/overview/index.md @@ -29,4 +29,4 @@ The following portable resources are available to use within your application: ## Reference -Refer to the [API reference docs]({{< ref api >}}) to learn more about the Radius API and the available portable resources plus their schema \ No newline at end of file +Refer to the [API reference docs]({{< ref "/concepts/technical/api" >}}) to learn more about the Radius API and the available portable resources plus their schema \ No newline at end of file diff --git a/docs/content/guides/deploy-apps/environments/overview/environments.png b/docs/content/guides/deploy-apps/environments/overview/environments.png deleted file mode 100644 index 9f0034e11..000000000 Binary files a/docs/content/guides/deploy-apps/environments/overview/environments.png and /dev/null differ diff --git a/docs/content/guides/deploy-apps/environments/overview/index.md b/docs/content/guides/deploy-apps/environments/overview/index.md index 23baf7fc5..d3f5a9ecc 100644 --- a/docs/content/guides/deploy-apps/environments/overview/index.md +++ b/docs/content/guides/deploy-apps/environments/overview/index.md @@ -8,7 +8,11 @@ categories: "Overview" tags: ["environments"] --- -Radius Environments are prepared "landing zones" for Radius Applications. Applications deployed to an environment will inherit the container runtime, configuration, and other settings from the environment. Stay tuned for additional environment capabilities coming soon. +## What is an environment? + +Radius Environments are prepared "landing zones" for Radius Applications. Applications deployed to an environment will inherit the container runtime, configuration, Recipes, and other settings from the environment. + +Environments are server-side resources that exist within the Radius control-plane. You can use the Radius API and [rad CLI](#cli-commands) to interact with your installation's environments. ## Configuration @@ -16,22 +20,18 @@ The following configuration options are available for environments: ### Container runtime -Radius Environments can be configured with a container runtime, where Radius [containers]({{< ref "guides/author-apps/containers" >}}) will be run, along with [gateways and routes]({{< ref networking >}}). - -A Kubernetes namespace is specified on the environment to tell Radius where to render application resources at deploy time. +Radius Environments can be configured with a container runtime, where Radius [containers]({{< ref "guides/author-apps/containers" >}}) will be deployed. Currently, only Kubernetes clusters are supported for container runtimes. -{{< image src=environments.png alt="Diagram showing a Radius Environment mapping to a Kubernetes cluster and namespace" width=800px >}} +A Kubernetes namespace is specified on the environment to tell Radius where to render environment-scoped resources. For example, a shared database deployed to an environment will be deployed to the namespace specified on the environment. Application-scoped resources will be deployed into a new namespace for each application, in the format `-`. For example, if an application named `myapp` is deployed to an environment with the namespace `default`, the application-scoped resources will be deployed to the namespace `default-myapp`. -### Cloud Provider +### Cloud provider You can optionally configure cloud providers allow you to deploy and connect to cloud resources across various cloud platforms. For example, you can use the Radius Azure provider to run your application's services in your Kubernetes cluster, while deploying Azure resources to a specified Azure subscription and resource group. More information on setting up a cloud provider can be found in the [providers]({{< ref providers >}}) section. #### Supported cloud providers -| Provider | Description | -|----------|-------------| -| Microsoft Azure | Deploy and connect to Azure resources | -| Amazon Web Services | Deploy and connect to AWS resources | +- Microsoft Azure +- Amazon Web Services ### External identity provider @@ -99,8 +99,8 @@ Visit the [environment schema page]({{< ref environment-schema >}}) to learn mor {{< button page="environment-schema" text="Schema" >}} -## Example +## Managing multiple environments -The following example shows an environment configured with Kubernetes as the target runtime. The `default` namespace designates where to render application resources. +If you are working with multiple environments, you can use [workspaces]({{< ref "/guides/operations/workspaces/overview" >}}) to manage them. Workspaces allow you to switch between different sets of environments, and can be used to manage different environments for different projects. -{{< rad file="snippets/environment.bicep" embed=true marker="//ENV" >}} +{{< button page="/guides/operations/workspaces/overview" text="Workspaces" >}} diff --git a/docs/content/guides/operations/control-plane/howto-postman/index.md b/docs/content/guides/operations/control-plane/howto-postman/index.md index 6533ff1ff..e59ae9eb9 100644 --- a/docs/content/guides/operations/control-plane/howto-postman/index.md +++ b/docs/content/guides/operations/control-plane/howto-postman/index.md @@ -158,4 +158,4 @@ Next, you'll need to get the control plane API endpoint and use Postman to inter ## Next step: Explore the Radius API -Now that you have successfully authenticated to the Radius API and interacted with resources, you can explore the API using the [Radius API reference]({{< ref api >}}). +Now that you have successfully authenticated to the Radius API and interacted with resources, you can explore the API using the [Radius API reference]({{< ref "/concepts/technical/api" >}}). diff --git a/docs/content/guides/operations/control-plane/traces/zipkin/index.md b/docs/content/guides/operations/control-plane/traces/zipkin/index.md index a422eda1e..9abe6e155 100644 --- a/docs/content/guides/operations/control-plane/traces/zipkin/index.md +++ b/docs/content/guides/operations/control-plane/traces/zipkin/index.md @@ -10,7 +10,7 @@ tags: ["tracing", "observability"] [Zipkin](https://zipkin.io/) is an open-source distributed tracing system. It helps gather timing data needed to troubleshoot latency problems in microservice architectures. It manages both the collection and lookup of this data. -The following steps show you how to configure the [Radius control plane]({{< ref architecture-concept >}}) components to send distributed tracing data to Zipkin running as a container in your Kubernetes cluster and how to view the data. +The following steps show you how to configure the [Radius control plane]({{< ref "/concepts/technical/architecture" >}}) components to send distributed tracing data to Zipkin running as a container in your Kubernetes cluster and how to view the data. ## Pre-requisites diff --git a/docs/content/guides/operations/groups/overview/index.md b/docs/content/guides/operations/groups/overview/index.md index 65735be2f..5a5bbafa8 100644 --- a/docs/content/guides/operations/groups/overview/index.md +++ b/docs/content/guides/operations/groups/overview/index.md @@ -68,6 +68,6 @@ rad group switch mygroup ## Additional information -- [Radius API]({{< ref api-concept >}}) -- [Radius architecture]({{< ref architecture-concept >}}) +- [Radius API]({{< ref "/concepts/technical/api" >}}) +- [Radius architecture]({{< ref "/concepts/technical/architecture" >}}) - [rad CLI reference]({{< ref rad_group >}}) \ No newline at end of file diff --git a/docs/content/guides/operations/kubernetes/kubernetes-install/index.md b/docs/content/guides/operations/kubernetes/kubernetes-install/index.md index 21136dc34..289f0e3de 100644 --- a/docs/content/guides/operations/kubernetes/kubernetes-install/index.md +++ b/docs/content/guides/operations/kubernetes/kubernetes-install/index.md @@ -11,6 +11,12 @@ slug: 'install' Radius handles the deployment and management of environments, applications, and other resources with components that are installed into the Kubernetes cluster. +## Prerequisites + +- [Kubernetes cluster]({{< ref "guides/operations/kubernetes/overview#supported-kubernetes-clusters" >}}) +- [kubectl](https://kubernetes.io/docs/tasks/tools/install-kubectl/) +- [rad CLI]({{< ref howto-rad-cli >}}) + ## Install with the rad CLI Use the [`rad install kubernetes` command]({{< ref rad_install_kubernetes >}}) to install Radius into the `radius-system` namespace on your Kubernetes cluster. You can optionally use the `--set` flag to customize the installation with [Helm configuration options](#helm-configuration-options): diff --git a/docs/content/guides/operations/kubernetes/kubernetes-metadata/index.md b/docs/content/guides/operations/kubernetes/kubernetes-metadata/index.md index e2c4d7755..226939407 100644 --- a/docs/content/guides/operations/kubernetes/kubernetes-metadata/index.md +++ b/docs/content/guides/operations/kubernetes/kubernetes-metadata/index.md @@ -3,7 +3,7 @@ type: docs title: "How-To: Set Kubernetes metadata" linkTitle: "Kubernetes metadata" description: "Learn how to configure Kubernetes labels and annotations for generated objects" -weight: 400 +weight: 500 categories: "How-To" tags: ["containers","Kubernetes","applications","environments"] --- diff --git a/docs/content/guides/operations/kubernetes/kubernetes-uninstall/index.md b/docs/content/guides/operations/kubernetes/kubernetes-uninstall/index.md new file mode 100644 index 000000000..de50faeb6 --- /dev/null +++ b/docs/content/guides/operations/kubernetes/kubernetes-uninstall/index.md @@ -0,0 +1,37 @@ +--- +type: docs +title: "How-To: Uninstall Radius from Kubernetes" +linkTitle: "Uninstall Radius" +description: "Learn how to uninstall Radius control plane from your Kubernetes cluster" +weight: 400 +categories: "How-To" +tags: ["Kubernetes"] +--- + +## Prerequisites + +- [Radius installed on Kubernetes cluster]({{< ref "guides/operations/kubernetes/kubernetes-install" >}}) + +## Step 1: Uninstall the Radius control-plane from your kubernetes cluster + +To uninstall the existing Radius control-plane, run the following command: + +```bash +rad uninstall kubernetes +``` + +All the Radius services running in the `radius-system` namespace will be removed. Note that Radius configuration and data will still be persisted in the cluster until the namespace is also deleted. + +## Step 2: Delete the `radius-system` namespace + +To delete the `radius-system` namespace, run the following command: + +```bash +kubectl delete namespace radius-system +``` + +All Radius configuration and data will be removed as part of the namespace. This completely removes from your cluster. + +## Step 3: Remove the rad CLI + +You can remove the rad CLI by deleting the [ binary ]({{< ref "/guides/tooling/rad-cli/overview#binary-location" >}}) and ~/.rad folder from your machine. \ No newline at end of file diff --git a/docs/content/guides/operations/workspaces/overview/index.md b/docs/content/guides/operations/workspaces/overview/index.md index ed2eb8f01..6b1ed217b 100644 --- a/docs/content/guides/operations/workspaces/overview/index.md +++ b/docs/content/guides/operations/workspaces/overview/index.md @@ -7,10 +7,14 @@ weight: 200 categories: "Overview" --- -Workspaces allow you to manage multiple Radius platforms and environments using a local configuration file. You can easily define and switch between workspaces to deploy and manage applications across separate environments. +## What are workspaces? + +Workspaces allow you to manage multiple Radius [environments]({{< ref "/guides/deploy-apps/environments/Overview" >}}) using a local, client-side, configuration file. You can easily define and switch between workspaces to deploy and manage applications across separate environments. {{< image src=workspaces.png alt="Diagram showing a Radius configuration file mapping workspaces to Kubernetes clusters" width=800px >}} +The [`config.yaml`]({{< ref "/reference/config" >}}) file in your local Radius directory contains workspace entries that point to a Radius platform and environment. + ## CLI commands The following commands let you interact with Radius Environments: diff --git a/docs/content/guides/recipes/howto-author-recipes/index.md b/docs/content/guides/recipes/howto-author-recipes/index.md index 228b58799..06bffb77d 100644 --- a/docs/content/guides/recipes/howto-author-recipes/index.md +++ b/docs/content/guides/recipes/howto-author-recipes/index.md @@ -78,7 +78,7 @@ Once you have defined your IaC template you will need to output a `result` objec The `result` object must include: - **`values`**: The fields that the target resource requires. (_username, host, port, etc._) - **`secrets`**: The fields that the target resource requires, but should be treated as secrets. (_password, connectionString, etc._) -- **`resources`**: The [UCP ID(s)]({{< ref "api-concept#resource-ids" >}}) of the resources providing the backing service. Used by UCP to track dependencies and manage deletion. +- **`resources`**: The [UCP ID(s)]({{< ref "/concepts/technical/api#resource-ids" >}}) of the resources providing the backing service. Used by UCP to track dependencies and manage deletion. {{< tabs "Bicep" "Terraform" >}} diff --git a/docs/content/guides/recipes/overview/index.md b/docs/content/guides/recipes/overview/index.md index 222288c4e..c0fc9259f 100644 --- a/docs/content/guides/recipes/overview/index.md +++ b/docs/content/guides/recipes/overview/index.md @@ -19,7 +19,7 @@ Recipes enable a **separation of concerns** between IT operators and developers | Language | Supported sources | Notes | |----------|-------------------|-------| | [Bicep](https://learn.microsoft.com/azure/azure-resource-manager/bicep/) | [OCI registries](https://opencontainers.org/) | Supports Azure, AWS, and Kubernetes -| [Terraform](https://developer.hashicorp.com/terraform/docs) | [Public Terraform registries](https://registry.terraform.io/) | Supports Azure, AWS, and Kubernetes providers
Other providers not yet configurable +| [Terraform](https://developer.hashicorp.com/terraform/docs) | [Public module sources](https://developer.hashicorp.com/terraform/language/modules/sources)
Private modules not yet configurable | Supports Azure, AWS, and Kubernetes providers
Other providers not yet configurable ### Select the Recipe that meets your needs diff --git a/docs/content/guides/tooling/rad-cli/overview/index.md b/docs/content/guides/tooling/rad-cli/overview/index.md index 1dfbb1e50..e3b52efab 100644 --- a/docs/content/guides/tooling/rad-cli/overview/index.md +++ b/docs/content/guides/tooling/rad-cli/overview/index.md @@ -43,7 +43,7 @@ The rad CLI is distributed as a single binary that can be installed on Linux, ma {{< button text="Install rad CLI" page="howto-rad-cli" >}} -### Binary location +## Binary location {{< tabs "macOS/Linux/WSL" "Windows" >}} @@ -66,9 +66,9 @@ By default, the rad CLI installation script installs the rad CLI to `%LOCALAPPDA {{< /tabs >}} -### Configuration location +## Configuration -The rad CLI stores workspaces, the rad-Bicep compiler, and other configuration under the `rad` directory. +The rad CLI stores its configuration, the rad-Bicep compiler, and other configuration under the `rad` directory. {{< tabs "macOS/Linux/WSL" "Windows" >}} @@ -77,11 +77,23 @@ The rad CLI stores configuration under `~/.rad` {{% /codetab %}} {{% codetab %}} -The rad CLI stores configuration under `%USERPROFILE%\rad` +The rad CLI stores configuration under `%USERPROFILE%\.rad` {{% /codetab %}} {{< /tabs >}} +### `config.yaml` file + +The rad CLI stores its configuration in a YAML file named `config.yaml` under the `rad` directory. This file contains [workspaces]({{< ref "/guides/operations/workspaces/overview" >}}), which point to your cluster, your default [resource group]({{< ref "/guides/operations/groups/overview" >}}), and your default [environment]({{< ref "/guides/deploy-apps/environments/overview" >}}). + +When the rad CLI runs commands, it will use the configuration in the `config.yaml` file to determine which cluster, resource group, and environment to target and use. + +For more information, refer to the [`config.yaml` reference documentation]({{< ref "/reference/config" >}}). + +### `rad-bicep` compiler + +The rad CLI uses the rad-bicep compiler to compile Bicep files to JSON templates. The rad-bicep compiler is stored as `/bin/rad-bicep` within your configuration directory. + ## Reference documentation Visit the [reference documentation]({{< ref "/reference/cli" >}}) to learn more about the rad CLI and its commands. diff --git a/docs/content/reference/api/resource-policies/index.md b/docs/content/reference/api/resource-policies/index.md index bab2d90da..56f796948 100644 --- a/docs/content/reference/api/resource-policies/index.md +++ b/docs/content/reference/api/resource-policies/index.md @@ -9,15 +9,15 @@ description: "Learn the timeout/retry policies of the Radius API" There are two main Radius services that will provide the resources described below: -- [Deployment Engine]({{< ref "architecture-concept#bicep-deployments-resource-provider" >}}) -- [Resource Provider]({{< ref "architecture-concept#applications-resource-provider" >}}) +- [Deployment Engine]({{< ref "/concepts/technical/architecture#bicep-deployments-resource-provider" >}}) +- [Resource Provider]({{< ref "/concepts/technical/architecture#applications-resource-provider" >}}) ## Deployment engine behavior | Operation | Resource Name | Server Timeout (Seconds) | Async Operation retry condition| |------|:--------:|-------------|---------|------------| | Default retry timeout for resource deployment | The name of your resource. | 12.5 minutes per resource | Retries on 5xx errors, 50 retry requests -| Default request timeout | | Dependent on [UCP]({{< ref "architecture-concept#ucp-a-general-resource-management-api" >}}) | +| Default request timeout | | Dependent on [UCP]({{< ref "/concepts/technical/architecture#ucp-a-general-resource-management-api" >}}) | ### Resource provider behavior diff --git a/docs/content/reference/config.md b/docs/content/reference/config.md index fd8faea45..c14ea4677 100644 --- a/docs/content/reference/config.md +++ b/docs/content/reference/config.md @@ -18,26 +18,18 @@ workspaces: kind: kubernetes environment: /planes/radius/local/resourcegroups/dev/providers/applications.core/environments/dev scope: /planes/radius/local/resourceGroups/dev - providerConfig: - azure: - subscriptionid: DEV-SUBID - resourcegroup: Dev prod: connection: context: ProdCluster kind: kubernetes environment: /planes/radius/local/resourcegroups/prod/providers/applications.core/environments/prod scope: /planes/radius/local/resourceGroups/prod - providerConfig: - azure: - subscriptionid: PROD-SUBID - resourcegroup: Prod ``` ## Default location - **macOS/Linux:** `~/.rad/config.yaml` -- **Windows:** `%USERPROFILE%.rad\config.yaml` +- **Windows:** `%USERPROFILE%\.rad\config.yaml` ## Schema @@ -56,7 +48,6 @@ workspaces: | [**connection**](#connection) | The connection details for the target Radius platform | | | **environment** | The default environment UCP ID to use for the workspace. Can be empty if no environment exists or if no default set | `/planes/radius/local/resourcegroups/dev/providers/applications.core/environments/dev` | | **scope** | The default scope UCP ID to use for the workspace | `/planes/radius/local/resourcegroups/dev` | -| [**providerConfig**](#providerconfig) | The provider configuration for the workspace | | #### connection @@ -65,10 +56,3 @@ workspaces: | **context** | The name of the Kubernetes context to use | `DevCluster` | | **namespace** | The name of the Kubernetes namespace to use when deploying Radius Applications | `default` | -#### providerConfig - -| Key | Description | Example | -|-----|-------------|---------| -| **azure** | The kind of [cloud provider](#cloud-providers) to configure. Currently only 'azure' is supported | `azure` | -| **subscriptionid** | The Azure subscriptionID to deploy resources into -| **resourcegroup** | The name of the Azure resource group to deploy Azure resources into | `Dev` | diff --git a/presentation-pack/Logos/PDF/Radius-Logo-Reverse.pdf b/presentation-pack/Logos/PDF/Radius-Logo-Reverse.pdf new file mode 100644 index 000000000..a2fe77966 Binary files /dev/null and b/presentation-pack/Logos/PDF/Radius-Logo-Reverse.pdf differ diff --git a/presentation-pack/Logos/PDF/Radius-Logo.pdf b/presentation-pack/Logos/PDF/Radius-Logo.pdf new file mode 100644 index 000000000..d660f3f09 Binary files /dev/null and b/presentation-pack/Logos/PDF/Radius-Logo.pdf differ diff --git a/presentation-pack/Logos/PDF/Radius-Logomark-Reverse.pdf b/presentation-pack/Logos/PDF/Radius-Logomark-Reverse.pdf new file mode 100644 index 000000000..dbc61b1cd Binary files /dev/null and b/presentation-pack/Logos/PDF/Radius-Logomark-Reverse.pdf differ diff --git a/presentation-pack/Logos/PDF/Radius-Logomark.pdf b/presentation-pack/Logos/PDF/Radius-Logomark.pdf new file mode 100644 index 000000000..e288e96a5 Binary files /dev/null and b/presentation-pack/Logos/PDF/Radius-Logomark.pdf differ diff --git a/presentation-pack/Logos/PDF/Radius-Logotype-Reverse.pdf b/presentation-pack/Logos/PDF/Radius-Logotype-Reverse.pdf new file mode 100644 index 000000000..2d83951ea Binary files /dev/null and b/presentation-pack/Logos/PDF/Radius-Logotype-Reverse.pdf differ diff --git a/presentation-pack/Logos/PDF/Radius-Logotype.pdf b/presentation-pack/Logos/PDF/Radius-Logotype.pdf new file mode 100644 index 000000000..08ab5a7ea Binary files /dev/null and b/presentation-pack/Logos/PDF/Radius-Logotype.pdf differ diff --git a/presentation-pack/Logos/PNG/0.5x/Radius-Logo-Reverse@0.5x.png b/presentation-pack/Logos/PNG/0.5x/Radius-Logo-Reverse@0.5x.png new file mode 100644 index 000000000..524f43da6 Binary files /dev/null and b/presentation-pack/Logos/PNG/0.5x/Radius-Logo-Reverse@0.5x.png differ diff --git a/presentation-pack/Logos/PNG/0.5x/Radius-Logo@0.5x.png b/presentation-pack/Logos/PNG/0.5x/Radius-Logo@0.5x.png new file mode 100644 index 000000000..e44b0e173 Binary files /dev/null and b/presentation-pack/Logos/PNG/0.5x/Radius-Logo@0.5x.png differ diff --git a/presentation-pack/Logos/PNG/0.5x/Radius-Logomark-Reverse@0.5x.png b/presentation-pack/Logos/PNG/0.5x/Radius-Logomark-Reverse@0.5x.png new file mode 100644 index 000000000..f64420485 Binary files /dev/null and b/presentation-pack/Logos/PNG/0.5x/Radius-Logomark-Reverse@0.5x.png differ diff --git a/presentation-pack/Logos/PNG/0.5x/Radius-Logomark@0.5x.png b/presentation-pack/Logos/PNG/0.5x/Radius-Logomark@0.5x.png new file mode 100644 index 000000000..f1b9760d2 Binary files /dev/null and b/presentation-pack/Logos/PNG/0.5x/Radius-Logomark@0.5x.png differ diff --git a/presentation-pack/Logos/PNG/0.5x/Radius-Logotype-Reverse@0.5x.png b/presentation-pack/Logos/PNG/0.5x/Radius-Logotype-Reverse@0.5x.png new file mode 100644 index 000000000..4d6905450 Binary files /dev/null and b/presentation-pack/Logos/PNG/0.5x/Radius-Logotype-Reverse@0.5x.png differ diff --git a/presentation-pack/Logos/PNG/0.5x/Radius-Logotype@0.5x.png b/presentation-pack/Logos/PNG/0.5x/Radius-Logotype@0.5x.png new file mode 100644 index 000000000..33026f267 Binary files /dev/null and b/presentation-pack/Logos/PNG/0.5x/Radius-Logotype@0.5x.png differ diff --git a/presentation-pack/Logos/PNG/0.75x/Radius-Logo-Reverse@0.75x.png b/presentation-pack/Logos/PNG/0.75x/Radius-Logo-Reverse@0.75x.png new file mode 100644 index 000000000..3039e6dba Binary files /dev/null and b/presentation-pack/Logos/PNG/0.75x/Radius-Logo-Reverse@0.75x.png differ diff --git a/presentation-pack/Logos/PNG/0.75x/Radius-Logo@0.75x.png b/presentation-pack/Logos/PNG/0.75x/Radius-Logo@0.75x.png new file mode 100644 index 000000000..e7ff77905 Binary files /dev/null and b/presentation-pack/Logos/PNG/0.75x/Radius-Logo@0.75x.png differ diff --git a/presentation-pack/Logos/PNG/0.75x/Radius-Logomark-Reverse@0.75x.png b/presentation-pack/Logos/PNG/0.75x/Radius-Logomark-Reverse@0.75x.png new file mode 100644 index 000000000..db00c97a7 Binary files /dev/null and b/presentation-pack/Logos/PNG/0.75x/Radius-Logomark-Reverse@0.75x.png differ diff --git a/presentation-pack/Logos/PNG/0.75x/Radius-Logomark@0.75x.png b/presentation-pack/Logos/PNG/0.75x/Radius-Logomark@0.75x.png new file mode 100644 index 000000000..ef4749c55 Binary files /dev/null and b/presentation-pack/Logos/PNG/0.75x/Radius-Logomark@0.75x.png differ diff --git a/presentation-pack/Logos/PNG/0.75x/Radius-Logotype-Reverse@0.75x.png b/presentation-pack/Logos/PNG/0.75x/Radius-Logotype-Reverse@0.75x.png new file mode 100644 index 000000000..fbb7d4037 Binary files /dev/null and b/presentation-pack/Logos/PNG/0.75x/Radius-Logotype-Reverse@0.75x.png differ diff --git a/presentation-pack/Logos/PNG/0.75x/Radius-Logotype@0.75x.png b/presentation-pack/Logos/PNG/0.75x/Radius-Logotype@0.75x.png new file mode 100644 index 000000000..842806019 Binary files /dev/null and b/presentation-pack/Logos/PNG/0.75x/Radius-Logotype@0.75x.png differ diff --git a/presentation-pack/Logos/PNG/1x/Radius-Logo-Reverse.png b/presentation-pack/Logos/PNG/1x/Radius-Logo-Reverse.png new file mode 100644 index 000000000..692de10ca Binary files /dev/null and b/presentation-pack/Logos/PNG/1x/Radius-Logo-Reverse.png differ diff --git a/presentation-pack/Logos/PNG/1x/Radius-Logo.png b/presentation-pack/Logos/PNG/1x/Radius-Logo.png new file mode 100644 index 000000000..1242d4e99 Binary files /dev/null and b/presentation-pack/Logos/PNG/1x/Radius-Logo.png differ diff --git a/presentation-pack/Logos/PNG/1x/Radius-Logomark-Reverse.png b/presentation-pack/Logos/PNG/1x/Radius-Logomark-Reverse.png new file mode 100644 index 000000000..12a24b981 Binary files /dev/null and b/presentation-pack/Logos/PNG/1x/Radius-Logomark-Reverse.png differ diff --git a/presentation-pack/Logos/PNG/1x/Radius-Logomark.png b/presentation-pack/Logos/PNG/1x/Radius-Logomark.png new file mode 100644 index 000000000..c78b5b6b4 Binary files /dev/null and b/presentation-pack/Logos/PNG/1x/Radius-Logomark.png differ diff --git a/presentation-pack/Logos/PNG/1x/Radius-Logotype-Reverse.png b/presentation-pack/Logos/PNG/1x/Radius-Logotype-Reverse.png new file mode 100644 index 000000000..b64cc10b7 Binary files /dev/null and b/presentation-pack/Logos/PNG/1x/Radius-Logotype-Reverse.png differ diff --git a/presentation-pack/Logos/PNG/1x/Radius-Logotype.png b/presentation-pack/Logos/PNG/1x/Radius-Logotype.png new file mode 100644 index 000000000..0b8cb6477 Binary files /dev/null and b/presentation-pack/Logos/PNG/1x/Radius-Logotype.png differ diff --git a/presentation-pack/Logos/SVG/Radius-Logo-Reverse.svg b/presentation-pack/Logos/SVG/Radius-Logo-Reverse.svg new file mode 100644 index 000000000..6e7f4c4a5 --- /dev/null +++ b/presentation-pack/Logos/SVG/Radius-Logo-Reverse.svg @@ -0,0 +1,27 @@ + + + + + + + + + + + + + + + + + + + \ No newline at end of file diff --git a/presentation-pack/Logos/SVG/Radius-Logo.svg b/presentation-pack/Logos/SVG/Radius-Logo.svg new file mode 100644 index 000000000..f1995cd4a --- /dev/null +++ b/presentation-pack/Logos/SVG/Radius-Logo.svg @@ -0,0 +1,52 @@ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + \ No newline at end of file diff --git a/presentation-pack/Logos/SVG/Radius-Logomark-Reverse.svg b/presentation-pack/Logos/SVG/Radius-Logomark-Reverse.svg new file mode 100644 index 000000000..5aff4d22b --- /dev/null +++ b/presentation-pack/Logos/SVG/Radius-Logomark-Reverse.svg @@ -0,0 +1,16 @@ + + + + + + + + \ No newline at end of file diff --git a/presentation-pack/Logos/SVG/Radius-Logomark.svg b/presentation-pack/Logos/SVG/Radius-Logomark.svg new file mode 100644 index 000000000..7e2e94365 --- /dev/null +++ b/presentation-pack/Logos/SVG/Radius-Logomark.svg @@ -0,0 +1,41 @@ + + + + + + + + + + + + + + + + + + + + + + + + + \ No newline at end of file diff --git a/presentation-pack/Logos/SVG/Radius-Logotype-Reverse.svg b/presentation-pack/Logos/SVG/Radius-Logotype-Reverse.svg new file mode 100644 index 000000000..c63b2b2f2 --- /dev/null +++ b/presentation-pack/Logos/SVG/Radius-Logotype-Reverse.svg @@ -0,0 +1,24 @@ + + + + + + + + + + + + + + + + \ No newline at end of file diff --git a/presentation-pack/Logos/SVG/Radius-Logotype.svg b/presentation-pack/Logos/SVG/Radius-Logotype.svg new file mode 100644 index 000000000..6d0d43d1d --- /dev/null +++ b/presentation-pack/Logos/SVG/Radius-Logotype.svg @@ -0,0 +1,24 @@ + + + + + + + + + + + + + + + + \ No newline at end of file diff --git a/presentation-pack/README.md b/presentation-pack/README.md new file mode 100644 index 000000000..c561bbcba --- /dev/null +++ b/presentation-pack/README.md @@ -0,0 +1,9 @@ +# Radius Presentation Pack + +This directory contains assets you can leverage when giving a Radius presentation, including: + +- [Radius PowerPoint template](Radius.potx) +- [Radius logos](Logos/) +- [Radius resource icons](Resources/) + +For more information, refer to [Giving a Radius presentation](https://docs.radapp.io/community/presentations/). diff --git a/presentation-pack/Radius.potx b/presentation-pack/Radius.potx new file mode 100644 index 000000000..52dce275e Binary files /dev/null and b/presentation-pack/Radius.potx differ diff --git a/presentation-pack/Resources/SVG/Application.svg b/presentation-pack/Resources/SVG/Application.svg new file mode 100644 index 000000000..0fbd7384b --- /dev/null +++ b/presentation-pack/Resources/SVG/Application.svg @@ -0,0 +1,26 @@ + + + + + + + + + + + + + + \ No newline at end of file diff --git a/presentation-pack/Resources/SVG/Container.svg b/presentation-pack/Resources/SVG/Container.svg new file mode 100644 index 000000000..925041cbb --- /dev/null +++ b/presentation-pack/Resources/SVG/Container.svg @@ -0,0 +1,19 @@ + + + + + + + + + + + \ No newline at end of file diff --git a/presentation-pack/Resources/SVG/Environment.svg b/presentation-pack/Resources/SVG/Environment.svg new file mode 100644 index 000000000..83705065d --- /dev/null +++ b/presentation-pack/Resources/SVG/Environment.svg @@ -0,0 +1,16 @@ + + + + + + + + \ No newline at end of file diff --git a/presentation-pack/Resources/SVG/Gateway.svg b/presentation-pack/Resources/SVG/Gateway.svg new file mode 100644 index 000000000..85873028b --- /dev/null +++ b/presentation-pack/Resources/SVG/Gateway.svg @@ -0,0 +1,17 @@ + + + + + + + + + \ No newline at end of file diff --git a/presentation-pack/Resources/SVG/Hexagon.svg b/presentation-pack/Resources/SVG/Hexagon.svg new file mode 100644 index 000000000..7833828e3 --- /dev/null +++ b/presentation-pack/Resources/SVG/Hexagon.svg @@ -0,0 +1,11 @@ + + + + + + + \ No newline at end of file diff --git a/presentation-pack/Resources/SVG/Portable Resources.svg b/presentation-pack/Resources/SVG/Portable Resources.svg new file mode 100644 index 000000000..6a4d9f98a --- /dev/null +++ b/presentation-pack/Resources/SVG/Portable Resources.svg @@ -0,0 +1,25 @@ + + + + + + + + + + + + + \ No newline at end of file diff --git a/presentation-pack/Resources/SVG/Recipe.svg b/presentation-pack/Resources/SVG/Recipe.svg new file mode 100644 index 000000000..71a8bb949 --- /dev/null +++ b/presentation-pack/Resources/SVG/Recipe.svg @@ -0,0 +1,37 @@ + + + + + + + + + + + + + + + + + + + + + + + + + \ No newline at end of file diff --git a/presentation-pack/Resources/SVG/Secret Stores.svg b/presentation-pack/Resources/SVG/Secret Stores.svg new file mode 100644 index 000000000..24a81f6d7 --- /dev/null +++ b/presentation-pack/Resources/SVG/Secret Stores.svg @@ -0,0 +1,31 @@ + + + + + + + + + + + + + + + + + + + \ No newline at end of file