Uploaded image for project: 'Red Hat 3scale API Management'
  1. Red Hat 3scale API Management
  2. THREESCALE-1918

Switch to PatternFly 4 Header styling

XMLWordPrintable

    • Icon: Task Task
    • Resolution: Done
    • Icon: Major Major
    • None
    • None
    • System
    • None
    • 20
    • Not Started
    • Not Started
    • Not Started
    • Not Started
    • Not Started
    • Not Started
    • 3scale 2019-03-11

      Middleware products will switch to PatternFly 4 (PF4) in a synchronized way for the in-your-face parts. The first part will be the masthead/header.

      https://pf4.patternfly.org/demos/Page/examples-full/?component=Page%20Component%20Default%20Nav%20Header%20Example

      • Currently, 3scale Header is a Rails view. Considering our goal is to move the most of our Frontend job to Webpack + React, we should use Patternfly-React
      • We shouldn't use the Page component, because this component is supposed to work as a container for a whole Single Page Application, which we don't have.
      • It implies redoing our current header into a new PF4/React component, using the Pageheader component
      • The Context Switcher component (currently a React Component), will be a child of this new component. It will need some refactor
      • We need to use dark theme for the context selector https://github.com/patternfly/patternfly-next/pull/1427
      • We need to create new React components for:
      1. Avatar, using Avatar component
      2. Toolbar, using the Toolbar component. It will include 2 children:
        1. Documentation (Question mark)
        2. Admin account (Engine)
      • We need to write test for all components, except Context Switcher

              Unassigned Unassigned
              tmaas-1 Thomas Maas
              Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

                Created:
                Updated: