Quick Start Guide

[ianphil]

Description

As a technical editor, I'd like to use existing docs to create a quick start guide, in order to allow any user to get started with cobalt.

Acceptance Criteria

Reference: [Done-Done Checklist] (https://github.com/Microsoft/code-with-engineering-playbook/blob/master/Engineering/BestPractices/DoneDone.md)

• [x] Should use content from the Adpat Document
• [x] Should use content from the Single Region Readme
• [x] Should "feel" like a lab not documentation.

Also, here are a few points that need to be addressed:

1. No persona / or the persona is Everyone.
2. See stub file for this story: docs/2_QUICK_START_GUIDE.md

Resources

Epic #347

Tasks

Stories are intended to be completed in a single sprint; if task breakdown creates addition work then team should discuss promoting the Story to an Epic. Reference: [Minimal Valuable Slices] (https://github.com/Microsoft/code-with-engineering-playbook/blob/master/Engineering/BestPractices/MinimalSlices.md)

Reference: [How to Write Better Tasks] (http://agilebutpragmatic.blogspot.com/2012/04/splitting-story-into-tasks-how-to-write.html)

Assignee should break down work into tasks here

[TechnicallyWilliams]

Quick start guide passively links to the az-hello-word CIT: #227 [Doc] az-hello-world template needs documentation (prev. azure-simple-hw)