Here is the definition for PowerShell - github.com/toptal/gitig...

Yes, I would accept a PR for this. We still maintain the 5.1 docs. We don't need repro steps, just a NOTE added to the parameter similar to what we have for `-Include`.

The sidebar nav was removed from the Learn platform and replaced with the list of suggested articles. I don't like it, but is it a platform design decision that I, as an writer, can't change.

We have a style guide for the docs. There is an unofficial code style guide at: github.com/PoshCode/Pow...

How would you organize the documentation? It is not a simple task. There are lots of different kinds of docs. And docs are written for different purposes and audiences. There is a difference between reference docs and teaching docs.

Specifically, the articles in the learn.microsoft.com/en-us/powers... were written by Bruce Payette. It is legacy content that was originally publish as a Word doc. We don't intend to change. It is provided for historical reference. It is was written for v3 and isn't 100% accurate for v7+.

Yes, there is an official style. We try to make all of the documentation adhere to our style. Caveats:
1. We maintain over 9000 documents for PowerShell and the PowerShell SDK.
2. Much of that content was written by others, long before I joined the team.
3. We fix the style as we go.

learn.microsoft.com/en-us/powers...

This works:

$c.RelatedLinks.Add([Microsoft.PowerShell.PlatyPS.Model.Links]::new('Text','https://url.com/document'))

Check the Diagnostics property of the CommandHelp object.

The answer is to update the object before exporting to markdown.

The help text for the placeholders has to come from somewhere. It is not embedded in compiled commands.

No, the older module has the same placeholders. In either version, if you are documenting script-based modules, PlatyPS will include the comment-based help. But there is embedded documentation like that for C#-compiled cmdlets.