Note: This is not intended to be a definitive or exhaustive list. If there are additional templates that you feel may add value they should be added to the scope on consultation with PM.

• Plugin Development Templates:
  • Load the "Frontend dynamic plugin template" (via type: url, target: https://github.com/redhat-developer/red-hat-developer-hub-software-templates/blob/main/templates/create-frontend-plugin/template.yaml).
  • Load the "Backend dynamic plugin template" (via type: url, target: https://github.com/redhat-developer/red-hat-developer-hub-software-templates/blob/main/templates/create-backend-plugin/template.yaml).
  • Justification: Crucial for showcasing RHDH's extensibility and enabling users to immediately start developing their own plugins. But, requires clear messaging for the user about the template's GitHub integration dependency. In essence these may be for information only, but they are still valuable to surface to the platform engineer as an available additional tool.
• Content Management Templates:
  • Load the "Create a TechDoc" template (used to add TechDocs to existing projects).
  • Load the "Create a Catalog Entity" template (used to add a new catalog-info.yaml to an existing repo).
  • Justification: Provides immediate utility for users to add their own documentation and software components into the RHDH catalog.