I've been answering questions in the PowerShell tag recently, and I began to notice that specific cmdlets have been tagged over time. At first I thought this was oddly specific, but after some thought I think PowerShell cmdlets would make good candidates for tags, if the context of a particular question calls for it.
- It is very unambiguous. A question asking about some specific behavior of select-string would be well served by the "select-string" tag, grouping it with similar questions and allowing for easy navigation by future users.
- It would unnecessarily broaden the focus of some questions if they did not have cmdlet tags. Take this question for example, wherein the user experiences some difficulty with the output of Select-String when it returns a collection instead of a single object. The other two tags "PowerShell" and "Regex" begin to describe the problem, but the real issue is with the output returned from the cmdlet.
- It says a lot with a little. "This question specifically concerns this powershell cmdlet." When coupled with even a stub of a tag wiki, new users could learn about this particular cmdlet. Seasoned PowerShell users may recognize the cmdlet immediately, or even subscribe to it if they feel particularly comfortable with the topic.
With this in mind I've selected several existing cmdlet tags and have edited them to include a very basic description and link to Microsoft documentation:
If the community feels that these tags are worthwhile to pursue, I would like to continue fleshing out these existing cmdlet tag wikis by including suggestions on what sort of questions to tag these with, links to useful documentation, and links to related cmdlets. I would also like to create new cmdlet tags for either
- existing questions that are strong candidates to include a specific cmdlet tag, or
- new questions that would demonstrate some problem where this tag is appropriate.
This is my first time really undergoing any sort of tag review, and I would like some feedback as to if I'm going about this the right way. When justifiable, should these specific cmdlets have their own tags? Is there some sort of general procedure that I can follow to perform these edits without spamming up the powershell active listings?