Template Updates for vNext

[FriedrichWeinmann]

Will work on adding new features to templates, for some revamp / upgrade.
And since my memory is as horrible as it is, I write down my ideas somewhere I'll find them again.
Feel free to add your own proposals as response, happy to include ideas from the hivemind :)

MiniModule

• Add build script to generate / update help markdown using Microsoft.PowerShell.PlatyPS
• Add build script to code-sign artifact
• Add comment to make sure that changes to one build script are also applied to the other
• Add comment in psm1 to remind people not to put code there and to also update the build scripts
• Fully document all build scripts
• The Release step should include the latest changelog entries in the release notes
• Reorder release pipeline: Github release should be before PSGallery release, as it is easier to repeat
• Github release should grab repo name from environment variables, in case repo has different name than module

PSFProject

• Add psf-requirements.ps1 build script and use it as default for faster dependencies installation
• Add vsts-release.ps1 build script to publish a github releases
• Update *.yml files to use new build logic
• Add initialize.ps1 & variables.ps1 to the default files included
• Add build logic to generate about_ concept help from markdown, including readme.md
• Add build logic to generate documentation on commands, including migration to maml / external help
• Update readme.md to include better content (e.g. Install info)
• Dynamically inject Export-ModuleMember to the psm1 during the build process
• Include option to automatically update the FunctionsToExport during the build process
• Refactor help tests. Deal with type evaluation. Manage Mandatory parameters in Parametersets. Consider parametersets.
• Add build script to generate / update help markdown using Microsoft.PowerShell.PlatyPS
• Add build script to code-sign artifact
• Add comment to make sure that changes to one build script are also applied to the other
• Add comment in psm1 to remind people not to put code there and to also update the build scripts
• Fully document all build scripts
• The Release step should include the latest changelog entries in the release notes