Docs: Allow the built documents from CI to be accessible in some way

[Gnbrkm41]

It seems that I cannot build the docs/dotnet-api-docs repo locally because of internal repos that the build process depend on. This is annoying because I cannot verify the changes I've made before the PR is merged; it would be great if the document pages built from the CI can be made visible to us, so that we can make additional change for completeness before the PR is merged.

From what I can see, post-CI build reports (Example) seem to have links to the built pages, but they redirect to MS Login page and logging in results in 403 unauthorised error.

Docs authoring package for VS Code could be an option; but I've been having problems using the plugin and given that it's a plugin that merely imitates the behaviour I wouldn't fully trust the plugin to do the same thing as the ones built from here.

[svick]

This is a duplicate of https://github.com/MicrosoftDocs/feedback/issues/533, where the resolution was:

we do have a future roadmap item to figure out a way to review a PR from a non-Microsoft user that doesn’t require an @microsoft.com address.

Though it's not clear to me when can we expect anything to happen in this area.

[Thraka]

Closing as duplicate.

[Thraka]

Duplicate of MicrosoftDocs/feedback#533

[Thraka]

@Gnbrkm41 The docs authoring pack doesn't really do anything for the API docs 😦 We really appreciate any help you do in the API space. Thank you for your help.