I'm interested in a curated directory focused on PowerShell modules rather than general PowerShell resources. What should it include, and how could it stay useful as projects change?
What would make a PowerShell module directory actually useful?
Answers
Start with a clear inclusion policy. Requiring a PowerShell Gallery release that's at least 30 days old gives people something concrete to check. Then include projects that are actively maintained or genuinely feature complete, rather than assuming every quiet project is abandoned.
Maintenance status needs more than an archived repository check. Read the project notes too. A repository can still be open while its maintainers say the module has been sunset or recommend a replacement.
Reply to this answer
Make the descriptions do some work. A short explanation of what a module actually helps with is more useful than a name and a vague compliment. Grouping by task would make the directory easier to scan too.
For example, Microsoft.WinGet.Client gives people a PowerShell option for working with WinGet instead of parsing command-line output. PSWriteHTML is another candidate for people interested in generating HTML.
Reply to this answer
I'd like a section on module building and automation, not just modules for administering systems. PSake, PSDeploy and BuildHelpers are worth looking at for build and deployment workflows.
Don't assume one set of tools will give everyone a complete pipeline, though. CI systems and build preferences vary, so describe what each module covers and where people may need to assemble the rest themselves.
Reply to this answer
Give the directory a way to audit itself. A script that extracts module names, Gallery links, authors and download counts would make review easier. An author summary could also reveal when the list leans heavily on one maintainer.
Downloads are useful context, not proof that a module is good or still supported. Let people suggest additions and corrections, especially when a project changes direction.
Reply to this answer
There's a tradeoff with a Gallery-only rule. It keeps installation and discovery straightforward, but it can exclude a maintained fork that hasn't been published there. I'd state that limitation plainly rather than treating the directory as a complete map of every available module.
9f!claspfunnel_624:
That makes sense. A focused directory can have firm boundaries without implying that projects outside them are unusable.
Reply to this answer
Add your answer
Answers are reviewed before publication.
6q!brackenpiston_438:
It would also help to record the replacement when a module is deprecated, so someone searching for the old name can find the current option.