-
Epic
-
Resolution: Unresolved
-
Major
-
None
-
None
-
[PF6] Upgrade
-
False
-
-
False
-
In Progress
-
50% To Do, 14% In Progress, 36% Done
Description
The purpose of this epic is to convert the code base to use PF6. As part of this work, we may need to clean up older components, unneeded custom CSS, and make other UI changes.
Success criteria
- App will have the PF6 look and feel
- (Technical) Code will use PF6 styling and libraries
- (Technical) All components no longer supported by PF6 will be removed or converted
- (Technical) Swap all user facing redhat-cloud-services/frontend-components to use PatternFly components
Out of scope
- Any user-facing functional changes or additions (aka the app will behave as it does before the work)
- Tech clean-up except what is required for a smooth conversion to PF6. For example, conversion from .jsx to .tsx is out of scope.
Docs
Initial Analysis
https://docs.google.com/document/d/1jvmc49el_S-X6JB5RBjrJeTBuJNfUGS2CyFsgIEYSJA/edit#heading=h.qgylwjvi4tjk
Project Kick-off
https://docs.google.com/document/d/1CPUVwhe62t8SfnBhI4gKbdQdZqqjqsTcGjc9dBAHhOc/edit?tab=t.0#heading=h.l2cuovol0fpy
General approach
To avoid one large MR, this approach will be taken:
1. Conver redhat-cloud-services/frontend-components components to use PF components this will ensure consistent styling once PF6 is adopted
2. Do an initial application of PF6 and record any components that do not display correctly.
3. Look at each of the components identified in the previous step to see if they need work to use PF components and if custom CSS can be removed or changed to use standard PF CSS helper classes.
4. Start the process of applying PF6
5. Clean up any items that don't look correct (aka apply custom CSS if needed).