RHIDP-6584 - Document how users can install and configure plugins from Marketplace in RHDH

[Gerry-Forde]

IMPORTANT: Do Not Merge - To be merged by Docs Team Only

Version(s):
1.6

Issue:
RHIDP-6584

Preview:
Installing a plugin by using Extensions

[rhdh-bot]

Updated preview: https://redhat-developer.github.io/red-hat-developers-documentation-rhdh/pr-1084/ @ 05/12/25 13:25:13

[zdrapela]

The docs show the community version, but the RC 1.6-88 shows the productized version

[Gerry-Forde]

Test Day Feedback:

• Docs show the screenshot with Pipelines With Tekton by Backstage Community
• The procedure for installing plugins should say that the user should be in the Extensions page, and use the search there, not RHDH's header search bar (or the bigger search bar on the landing page). Even if they're on the right page, there are two search bars, and only one will give the results expected by the procedure, it should specify which to use.
• The screenshot here https://redhat-developer.github.io/red-hat-developers-documentation-rhdh/pr-1084/plugins-rhdh-install/images/rhdh-plugins-reference/rhdh-extensions-tekton-card.png doesn't include the blue highlight on the Extensions nav item in the sidebar, which makes it harder to understand from the screenshot where they are in the UI, or how they got there, if the procedure doesn't specify a starting point.
• The Tekton displayed is also the Community version, and what we see in test day is the Red Hat provided option, which has a different icon. I don't see the community version listed.
• Adding "catalog" or some other qualifer after Extensions, at least when introducing it, would help clear up potential ambiguity.
• Navigational elements in the UI to be visible in the screenshots and match what users will see, wherever possible.
• Installation instructions should specify dynamic-plugins.yaml as the file to be modified
• There should be a caveat that the RHDH project may need to be rolled out manually if installed via HELM in order for the plugin to become enabled.

[Gerry-Forde]

A few small comments, @Gerry-Forde.

@jmagak Thank you, I've incorporated your suggestions. Could you provide an approval please?

[hmanwani-rh]

/cherry-pick release-1.6

[openshift-cherrypick-robot]

@hmanwani-rh: I cannot cherry-pick the present PR on top of its base branch (release-1.6).

In response to this:

/cherry-pick release-1.6

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

[Gerry-Forde]

/cherry-pick main

[openshift-cherrypick-robot]

@Gerry-Forde: new pull request created: #1161

In response to this:

/cherry-pick main

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.