Incomplete documentation

[JimHume]

Information is incomplete or missing from a large percentage of the articles in the repository.

"As an administrator, it is hard to rely on the documentation when it is incomplete, and very difficult to use any of the functionality in its entirety without sufficient documentation."

[rodmhgl]

That's the purpose of this repository / project. Can you please be more specific with the cmdlets / areas you're seeing incomplete documentation in so we can target them?

[JimHume]

There are 48 instances of "{{Fill in the description}}". The pattern of text is easy enough to find if searching for "{{Fill":
https://github.com/MicrosoftDocs/windows-powershell-docs/search?utf8=%E2%9C%93&q=%7B%7BFill&type=

Update: the search pattern can be simplified to "Fill". The parentheses aren't required as it turns out.

The reason this issue is concerning: The "{{Fill *}}" pattern is leaking to the live site. One such example of an above offender:
https://docs.microsoft.com/en-us/powershell/module/provisioning/install-provisioningpackage?view=win10-ps

I initially found this when trying to look for details from the "Creators Update" or "Fall Creators Update".

Second update: I went back to try to figure out whether or not the Install-ProvisioningPackage would allow for packages via UNC path and realized there's another search term that yields ~11 files in its results: https://github.com/MicrosoftDocs/windows-powershell-docs/search?utf8=%E2%9C%93&q=%7B%7B+Add+example+code+here+%7D%7D&type=

"{{ Add example code here}}" has a few results and it also displays the results for "{{ Add description here }}"

[brianlic-msft]

@JimHume Thanks for reporting this! We're working on getting some of these corrected. For now, you can use PowerShell cmdlets for provisioning Windows 10 (reference) for the provisioning module.

If you see descriptions that are missing and would like to contribute, please submit a pull request and I can working on getting it merged. Thanks!