Story

Currently in RHDH, several navigation sidebar items are rendered based on user permissions, support grouping, and provide additional behaviors that are not fully supported by the existing NavItemBlueprint. To address these gaps, we need to introduce a custom NavContent extension that enables RHDH to control how navigation items are rendered and organized as they are today, while remaining fully compliant with the NFS model.

Background

Dependencies and Blockers

QE impacted work

Documentation impacted work

Acceptance Criteria

• The custom NavContent extension supports permission-aware rendering of navigation items, ensuring items are displayed only when the user has the required permissions
• The custom NavContent extension should support configuring and rendering navigation items based on a defined priority value
• The custom NavContent extension should consume and render:
  • All navigation items that are provided via the standard NavItemBlueprint
  • Navigation items provided via the custom RHDH NavItem extension

• The custom NavItem extension should support nested navigation items, enabling parent–child relationships in the navigation structure.
• The title provided for a navigation item via extensions configuration should support a titleKey that can be used for translation.

Refs:

WG notes: https://docs.google.com/document/d/14G569uZZjST3j--cEX3_IZcwe3iRU091ETcwZ773GXE/edit?tab=t.0#heading=h.bvqw57j2nbwz

NFS migration spike : https://docs.google.com/document/d/1Qb0T1Iu3ego50iO4V7NErSD44NdWSvk5n70pZvj-EmU/edit?tab=t.0#heading=h.zc5io9fn4km1

Backstage docs:
https://backstage.io/docs/frontend-system/architecture/extensions#creating-an-extension

https://github.com/backstage/backstage/blob/master/docs/frontend-system/building-apps/03-built-in-extensions.md