Peter M Taylor

I would be very interested Kevin to “extend” auto generated documentation adapting the C4 notation suggested for some Github source code with another Powershell Github API that converts downloaded raw...

This is a good idea. I guess for a use case example would be that all incoming work and their definitions for discussion for the next period/cycle of time would...

any progress regarding Porting to VSCode?

@Antaris that example is great I find that much easier to shift my focus/interest on namespace I need with the plus minus on the side to expand and collapse things...

need to refine @tigerfansga idea alongside with your own CI. Travis could be substituted for Appveyor and "extend" your process towards auto-documentation.

Could I ask for some use case examples when you mentioned " comment based help to generate the markdown"

Suggesting two ways. 1. Use multiple environments in the same .yml file https://www.appveyor.com/docs/build-environment/#using-multiple-images-for-the-same-build With these build options. https://www.appveyor.com/docs/linux-images-software/ 2. One continuous build using several tag systems to focus one platform...

Good idea! If the recursive option was used that is reading a directory of scripts, be better to display one image per file script otherwise gets clustered and too hard...

Ah reflecting this further I think y thoughts would be a simple named switch like -OutputType All for allowing any file even recursively or -OutputType Single to easier to read...

Sounds good. Go for it! Merry Xmas too!