Uploaded image for project: 'Red Hat Internal Developer Platform'
  1. Red Hat Internal Developer Platform
  2. RHIDP-7008

Assess Adopting New Frontend System for different plugins

    • L
    • False
    • Hide

      None

      Show
      None
    • False

      Feature Overview (aka. Goal Summary)

      We should understand the New Frontend System as a complete team. For this we should adopt it as a "learning exercise" to some of our plugins.

      Goals (aka. expected user outcomes)

      Add New Frontend System support to some plugins. Goal is that anyone from the UI team has done it for one plugin.

      Requirements (aka. Acceptance Criteria):

      1. Adopt the new frontend system for ~ 5 plugins (each team member should pick up at least one)?
        1. Our UI plugins from rhdh-plugins
          1. Bulk import
          2. Extensions/Marketplace
          3. Homepage
        2. Plugins from BCP like
          1. JFrog
          2. Nexus
          3. OpenShift Image Registry
          4. Theme
      2. Spike to understand our issues to convert these plugins (are there more bridges needed for additional mountpoints)
        1. Global Floating Action Button
        2. Global Header

      Out of Scope (Optional)

      Customer Considerations (Optional)

      This just prepare plugins to support the NFS. No change for customers expected.

      Documentation Considerations

      This just prepare plugins to support the NFS. No change in our off. doc expected. Some READMEs might be updated.

              rorai Rohit Rai
              cjerolim Christoph Jerolimov
              RHIDP - Frontend Plugins & UI
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated: