Better story for different versions/flavors of a module

[vors]

Problem

Currently, platyPS doesn't have a way to re-use content between different version or flaivors of the module. I.e. https://github.com/PowerShell/PowerShell-Docs/tree/staging/reference has different top-level folders with a bunch of duplicated content.

The same thing is applicable for different flavors of the same module, i.e. Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, and Skype for Business Online.

There is a significant overlap, so it's desirable to re-use the documentation.

Proposal

The schema would need to accommodate new meta information to support this.

• Command level tag to indicate applicable module names and versions per cmdlet.
• Parameter level tag for the same.

API to create and consume this functionality

• New parameter for New-ExternalHelp that allows generating particular version out of tagged md
• New capabilities for Update-MarkdownHelp that allows to update multi-version
• * Maybe new cmdlet or param set for onboarding experience: easily combine existing md files for different versions into one.

[vors]

To make it generic and simple to use, tags don't need to correspond to the module name or the version.
For both the parameter level and command level tags, they can be chosen as appropriate

For example

applicable: 3.0.0, 4.0.0, 4.1.0

Or

applicable: Lync for Bussiness 2016, Lync 2013

Then it can be scoped with a parameter New-ExternalHelp -ApplicableTag "Lync 2013"
Note that omitting applicable would mean "applicable to all version that can be generated out of it".
Which makes this schema changes incremental and doesn't require a schema number bump.

[vors]

First part of this work is merged into master, quick demo that explains the workflow https://gist.github.com/vors/d71009486ca95142653c7c29b8396123

[vors]

Merged to master

[kenwith]

@vors - never mind.. I deleted question about -ApplicableTag for the New-ExternalHelpCab after I re-read how it works. Ignore this. :)