che-19271 Adding a note about support of both product & project devfi…

…les on Eclipse Che hosted by Red Hat (#1986)

Signed-off-by: Ilya Buziuk <ibuziuk@redhat.com>

modules/hosted-che/partials/ref_about-hosted-che.adoc

@@ -11,7 +11,11 @@ The new service is part of the link:https://developers.redhat.com/developer-sand
 
 == Differences between Eclipse Che and CodeReady Workspaces
 
-Red Hat CodeReady Workspaces is the product that is built from the Eclipse Che project. The product is normally two versions behind the project. Red Hat also provides licensing, packaging, and support, so CodeReady Workspaces is considered a more stable product than the upstream Eclipse Che project. More details about the difference between Eclipse Che and Red Hat CodeReady Workspaces can be found on the official link:https://access.redhat.com/documentation/en-us/red_hat_codeready_workspaces/2.6/html/release_notes_and_known_issues/installing_and_deploying_codeready_workspaces#difference-between-che-and-codready-workspaces[documentation].
+Red Hat CodeReady Workspaces is the product that is built from the Eclipse Che project. The product is normally two versions behind the project. Red Hat also provides licensing, packaging, and support, so CodeReady Workspaces is considered a more stable product than the upstream Eclipse Che project. More details about the difference between Eclipse Che and Red Hat CodeReady Workspaces can be found on the official link:https://access.redhat.com/documentation/en-us/red_hat_codeready_workspaces/2.8/html/release_notes_and_known_issues/installing_and_deploying_codeready_workspaces#difference-between-che-and-codready-workspaces[documentation].
+
+NOTE: link:https://workspaces.openshift.com/[Eclipse Che hosted by Red Hat] provides both CodeReady Workspaces product-specific, as well as, Eclipse Che community devfiles on the "Get Started" tab of the User Dashboard.
+
+image::hosted-che/get-started-product-and-community-devfiles.png[]
 
 IMPORTANT: Eclipse Che and Red Hat CodeReady Workspaces share all of the features - all the product's functionality is available in the project and vice versa. However, not all the upstream plugins are available in the CodeReady Workspaces. To use an unsupported plugin inside the CodeReady Workspaces, one needs to explicitly point to the raw `meta.yaml` of the plugin from the devfile. The procedure is described in the xref:end-user-guide:adding-a-vs-code-extension-to-a-workspace.adoc#adding-the-vs-code-extension-using-the-workspace-configuration_che[Adding a VS Code extension using the workspace configuration] section.