Build should not overwrite existing documentation

[JensGJ]

I'm struggling to find the right way to use the documentation part of the template.

Every time I build the module (based on the template) the documentation files are created from scratch - overwriting any changes I have made to them. I haven't been using platyPS outside of this template, but I hope that the fix might be as simple as calling Update-Markdownhelp instead of New-Markdownhelp.

[ekkohdev]

It's been many years since I've done anything with PowerShell, but...

This template was set up to use platyPS to generate an external help file from Markdown source. The basic idea being that a build would use whatever is in the docs source location and generate the external help at that point in time, as part of the build output. The template/build itself isn't doing anything with creating/generating the Markdown source files, beyond what is included in the repo as part of the example.

What changes are you trying to make?

Looking at https://github.com/PowerShell/platyPS?tab=readme-ov-file#quick-start suggests Update-Markdownhelp might help if what you are trying to do is update the Markdown source file content after changes to the module source code, but I can't comment on how that works specifically so YMMV.