In section 2.2 Workspaces Requirements of the admin guide, https://access.redhat.com/documentation/en-us/red_hat_codeready_workspaces/2.6/html-single/administration_guide/index#workspaces-requirements_crw there are details about plugins which do not exist in CRW, with links to Che containers.

While this is reasonable for upstream, it's not ideal for downstream as the example plugins presented don't exist in CRW, so can't directly be used as a drop-in sizing example.

Example 2.1. The chePlugin che-incubator/typescript/latest

   - image: docker.io/eclipse/che-remote-plugin-node:next

Couple of problems there...

• https://github.com/redhat-developer/codeready-workspaces/tree/crw-2.7-rhel-8/dependencies/che-plugin-registry/v3/plugins/eclipse has no typescript plugin
• https://github.com/eclipse/che-plugin-registry/blob/master/che-theia-plugins.yaml#L34-L45 shows this is now a theia extension rather than a plugin

Also, since the upstream plugin registry (and soon downstream one too) has been rewritten from 'lots of per-plugin yaml files' to '3 overall yaml files', we'll want to revisit this section and ensure that stuff like this block are updated:

How to find the meta.yaml file of chePlugin

Community plug-ins are available in the che-plugin-registry GitHub repository in folder v3/plugins/${organization}/${name}/${version}/.

But also specifically mentioning "Community plugins" in the product admin guide is ... not ideal. cc: dmharris