Generalize Wiki #37
Description
Describe the issue
We should centralize the wiki to be something that we can clone to each sub-repo within the organization. This would mean we can have clear and uniform guidance on how developers can engage with us, file feedback, follow best-practices for .NET development, and submit PRs.
There are a lot of mostly blank pages we can consolidate about the WCT. We should make the home page general to the organization, but then have a top-level page for each Toolkit within the org.
The getting started section should be a resource for developers in choosing a technology and point to each toolkit which can help them with that. We can point to each sample repo/app as well as the NuGet packages and docs for each project collectively.
Preview Packages should be centralized on the DevOps feed, so that guidance should be already fairly neutral (outside the WinUI 3 section I think we can remove now).
The rest of the sections about contributing we should review and clean-up together. FYI @brminnick.
We may want to move the Org-specific info pages about the Toolkit org up (the last section currently).
Then we can have more general-development stuff last but order by common things like the build infrastructures to more specific things (like UI testing on Windows). Maybe we break those out into project specific groups.
Thoughts? FYI @Sergio0694 as well.