Create more task/recipe based documentation

[markwilkie]

This issue might turn into an epic itself. But the basic idea is to better use the frame of a developer, and present documentation for how a dev would think.

For example, what are the most important MSBuild properties/items/targets in the standard arcade build lifecycle?

Devs have to deal with figuring out what to find and replace when porting a large codebase with a complicated build and test setup. Let's create docs to help them do this.

Thanks @rynowak for your insight here.

[rynowak]

I also want to say that I'm pleased with the overall level of quality of the in-code documentation for the various MSBuild targets and tasks. This is some of the most readable MSBuild code I've ever seen. Keep it up!

Unfortunately in-code documentation only helps if you know where to look.

[markwilkie]

We've worked to go farther down this road by a) creating a principles doc which basically says just this and b) upping the priority such that features provide the right documentation that follow the principles.

Closing, but happy to open specific scenario issues to add to the feature work.