Wiki restructuring - Solution creation

[eriqua]

Description

• [Wiki] Find a better title for the 'Solution Creation' section #1519
• [Feature Request] Add a step by step "how to create a solution" #1518
• [Feature Request] Create Azure DevOps example for pipeline-orchestration #1514
• Add links to solutions using CARML #1563
• Add a reference to the samples folder on root #1520

[AlexanderSehr]

Regarding the ADO universal packages I guess it will be a pipeline orchestration example. We actually have a PR open for the general multi-repo approach (pipeline orchestration) and can then I guess add to it :)

[MariusStorhaug]

Would it also make sense to add a chapter on "layering" with the diagrams showing the different layers and how that fits together?

Similar to this:

[rahalan]

@eriqua , can you and @MariusStorhaug please elaborate more on the description

[eriqua]

This comes out of the workshop feedback. The solution creation wiki page currently includes samples of how to leverage published modules (from template specs or the private bicep registry) and combine them to create a simple solution.

The risk is for the code provided in that page to get stale. For this reason, the page should instead be linked to the samples folder containing code which should be continuously tested and thus known working (ref #1184).

In addition, the solution creation page should contain:

• guidance on how to create a solution (e.g. identify required modules, identify deployment order, choose between pipeline vs template orchestration, go to module readme and check required param, etc)
• be linked to external repos using CARML (e.g. AKS)

@MariusStorhaug I agree with the layering page. Probably something for the context section. I'd suggest a different issue for that though.

cc @MrMCake @rahalan @MariusStorhaug please advise if still unclear

[AlexanderSehr]

Linked to #1375 . Added a first couple tips + references to other workloads

[rahalan]

@rahalan split into more issues (one per task)

[MariusStorhaug]

Closed as this will be covered by other issues.