Description of problem:

From Ben:

1. Some extensions have missing "Highlights"
2. Some plugins in the extensions marketplace have missing "Highlights" in their expanded view (e.g. LDAP Catalog Integration has the highlight "Add some highlights of the plugins features")
   • Actual: The phrase "Add some highlights of the plugins features" is shown as a Highlight in the plugins expanded view
   • Expected: The plugin should have some genuine highlights that are unique to each plugin
   • Reproduce: Visit various plugins (there are a few). Search GitHib for "Add some highlights of the plugins features" to find them in the /plugins folder.
3. Extensions marketplace doesn't gracefully handle a situation where the marketplace listing has no `icon: ` field in the metadata. In these situations, it should show a default. https://www.figma.com/design/E6C9X3OSVzlWkW7ZsbxN7s/Administration?node-id=8216-14576&t=lyc74PNFpkmVcalR-4
   • Actual: No square is shown by default unless something has been encoded into the metadata. This is inefficient. The grey square must be present in the metadata. Without it no default is shown.
   • Expected: When a plugin does not have a graphical icon encoded in it's metadata a default "plug" icon should be shown. https://www.figma.com/design/E6C9X3OSVzlWkW7ZsbxN7s/Administration?node-id=8216-14576&t=lyc74PNFpkmVcalR-4
   • Reproduce: Remove the `icon: ` stanza encoded in a yaml for a marletplace listing. Once reloaded, the marketplace listing will no longer show a placeholder icon.

From Matt:

1. Missing icons on several Red Hat plugins
2. Some plugins don't capitalize Red Hat developer Hub properly in their details links
   • Azure DevOps and ArgoCD Software Template Actions as two examples have links to "Documentation for Red Hat developer Hub" in them. Lowercase D. Capitalize RHDH properly
3. Consider consistently capitalizing on the plugin details panel
   • If I search for a plugin, it takes me to the software catalog page for it, instead of the catalog entry, and there isn't a linkage between the two that I see. The techdocs and source link are displayed, but not active, however there is a source link above that section which works.
   • Is there value in offering a link from a plugin's software catalog entry to go view it in the plugin catalog? the information is a bit different between them.
4. Extensions Marketplace doesn't list the TechDocs addons plugin
5. Dynatrace (certified) plugin showing up in plugins filtered by "custom"
6. Customizing plugins
   • Plugin details have a customization section, but it's generic and doesn't offer any helpful content on how or where you can modify a plugin. It contains a generic link to go look at the RHDH docs, which takes the user to the root directory, and makes them figure out where they can get more info on modifying plugins. We should be able to do better and be more helpful than that.
   • Either include some basic info on where/how to configure a plugin on its details page, or at least directly take the user to a plugins doc page that describes that in more depth to help users succeed in making changes.

From Christoph:

1. Highlights: Add some highlights of the plugins features
2. Description: Provides the set of Software Template Actions => Provides a set of Software Template Actions
3. Merge Signals Frontend and Backend plugin?
4. Merge Kubernetes and Kubernetes Backend?
5. Dynatrace Certified is also displayed as custom plugin!!!
6. Merge Roadie and Rodie.io
7. Check Orchestrator For Red Hat Developer Hub / "Plugin Title"
8. Should we remove Software Catalog integrations or Software Template Actions?
9. Extensions plugin should now use Category Marketplace
10. Backstage Core Catgory for Notifications and Signals as well??
11. Azure DevOps has images in the about page
12. Missing icons:
    1. Catalog Backend Module for Microsoft Graph => Add icon?
    2. Container Image Registry for Quay => Quay icon?
    3. LDAP Catalog integration => LDAP Icon?
    4. Notifications => RHDH or Backstage icon?
    5. OpenShift Cluster Manager => OpenShift icon?
    6. Orchestrator For Red Hat => RHDH icon?
    7. Ping Identity => Icon
    8. Segment
13. Signals => Backstage or RHDH icon?
14. Missing packages:
    1. Ansible Plugins
    2. Argo CD Software Template Actions
    3. Azure Repository Software Template Actions
    4. Bulk import misses backend
    5. Catalog Backend Module for Microsoft Graph
    6. Container Image Registry for Quay
    7. Dynatrace For Managed Backend?
    8. Jira Backend?
    9. LDAP Catalog Integration
    10. Tekton => Kubernetes Backend
    11. Topology => Kubernetes Backend
15. Author correct???
    1. Really from Red Hat??? Catalog Backend Module for Microsoft Graph
    2. PingIdentity from Red HAt???
    3. Regex Software Template Action
    4. Signals should be Backstage Community
16. Verified is on some plugins but now all RH developed plugins?
    1. 3scale
    2. Azure Container registry
    3. Bulk import
    4. Extensions (plugin catalog)
    5. Nexus
    6. Orchestrator For Red Hat?
    7. Red Hat Argo CD

Build Details:

1. 1.5 test day issues