radius-project / radius-project/docs

Scenario-based tutorials and reference architectures

Open
#1,701 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

triaged
Dominant language
Bicep
Stars
26
Forks
52
Avg merge
3d 2h
Merged PRs (30d)
3

Description

What content needs to be created or modified?

Add scenario-based tutorials and/or reference architectures, ideally tailored to industries or common real-world scenarios, to showcase common architecture patterns using Radius.

Describe the solution you'd like

Create a set of guided tutorials/blueprints that walk users through end-to-end solutions (and the architecture behind them), such as "retail/e-commerce", "SaaS multi-tenant", "data processing pipeline", etc., focusing on commonly used patterns and how to implement them with Radius.

Where should the new material be placed?

Please suggest a location in the docs structure where this content should reside, or a URL path if known.

The associated pull request from the Radius code repo, if applicable

If there is, or will be, a code change in the main Radius repository related to this content, please provide the PR link here.

Additional context

Include any relevant context, links, or screenshots that might help with writing this documentation.

AB#18062

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reviewing the Radius documentation structure and existing tutorials and samples to identify where scenario-based content belongs. Define the scope and architecture patterns for the proposed real-world scenarios, then document end-to-end guided solutions and confirm that the tutorials clearly explain how to implement them with Radius.

Written by the indexing model from the issue text.

Assessment

Domain
documentation
Issue type
Documentation
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.