-
Epic
-
Resolution: Unresolved
-
Critical
-
None
-
None
-
Migrate custom dynamic plugin features to new frontend system
-
False
-
-
False
-
-
In Progress
-
RHDHPLAN-893 - Migrate RHDH UI features to New Frontend System
-
QE Needed, Docs Needed, TE Needed, Customer Facing, PX Needed
-
50% To Do, 50% In Progress, 0% Done
-
-
EPIC Goal
Migrate all / most of the custom dynamic plugin features RHDH to the New Frontend System.
Background/Feature Origin
As part of dynamic plugins in RHDH we've built a lot of custom mount points and features to support multiple different plugins and use cases. We need to migrate all of them to new frontend system extensions and extension blueprints.
Why is this important?
To keep feature parity between RHDH dynamic plugins and new frontend system.
Dependencies (internal and external)
Probably dynamic plugins team.
Acceptance Criteria
- Homepage should work and should be loaded as a dynamic plugin (loaded by default)
- Analytics Provider should work and should be loaded as a dynamic plugin (loaded by default)
- Theme should work and should be loaded as a dynamic plugin (loaded by default)
- Translation should still work and the plugin should be loaded as a dynamic plugin (loaded by default)
- Global Header should still work (migrated from mount points to Blueprints)
- New Drawer feature should still work (migrated from mount points to Blueprints)
- TBD: Do we need Blueprints for Provider and Listeners? (used by homepage plugin but also FAB)
