Docs issues
There's quite a few minor issues with the docs, probably caused by the migration to the Devolutions side.
https://docs.devolutions.net/powershell-universal/powershell-commands/new-udtable#example-7
Has markdown accidentally included at the end of the code block (I've seen a few of these but this one I remember).
A lot of links are dead, for example all of https://docs.devolutions.net/powershell-universal#security and https://docs.devolutions.net/powershell-universal#development
There's a difference in the list of variables described in the docs and the showcase https://docs.devolutions.net/powershell-universal/platform/variables#built-in-variables
https://showcase-psu.devolutions.net/Variables
I'd suggest that the parameter info shown in the showcase, vs docs - is reviewed. There is a lot of info on the parameters in the showcase, including what types they accept, which isn't even in the docs. Just the first page for example https://showcase-psu.devolutions.net/Autocomplete vs https://docs.devolutions.net/powershell-universal/powershell-commands/new-udautocomplete
Additionally, there's no documentation which describes what a 'site' license is.
https://store.devolutions.net/package#psu
Is this the same as the 'Enterprise' license before? https://web.archive.org/web/20240910103959/https://ironmansoftware.com/pricing/powershell-universal, which was 'One License for your Entire Organization'. Further described on https://support.ironmansoftware.com/portal/en/kb/articles/kb0014-enterprise-versus-per-server-licensing-faq. I say this because site is a bad name for a license like this IMO, especially if in the Docs the only mention of the word site is in the context of licensing is for IIS Sites https://docs.devolutions.net/powershell-universal/licensing#what-if-i-have-multiple-sites-on-a-single-iis-server
All Comments (3)
Hello @ajh
Thank you for taking the time to report these documentation issues and for providing specific examples.
We have been adapting the PowerShell Universal documentation following the migration to the Devolutions platform, and some pages, links, and references did not carry over as cleanly as intended. We have been correcting these issues as they are identified.
I will also report the items you listed to our internal team so they can be reviewed and corrected accordingly, including the broken links, documentation and Showcase differences, command parameter details, and the Site license clarification.
We appreciate you bringing these to our attention.
Best regards,
Ruben Tapia
@ajh Thank you for pointing this out. We agree that “Site License” can be confusing, particularly because “site” is also used in the documentation to refer to IIS websites.
This license allows an unlimited number of PowerShell Universal instances within the licensed site or business unit. It is not necessarily equivalent to the former Enterprise license, which covers an entire organization.
We are reviewing the terminology and will also update the licensing documentation to define the scope more clearly.
I have also updated some of the other issues you have mentioned. We are continuing to refine the documentation so I appreciate the feedback.
Adam Driscoll
PowerShell Expert and Software Architect at Devolutions
No problem, thanks