Customer Problem: 

Currently Quay.io’s UI/UX is dated (early 2010’s) and inconsistent with and decouple from the current cloud.redhat.com overall user experience. As a result customers and partners are unaware with how Quay ties into Red Hat’s offerings, creating a disjointed experience that doesn’t yet clearly demonstrate the true value of Quay.io in conjunction with the Red hat’s product suite. 

Goal: 

Quay.io's overall UX is going to move into console.redhat.com. As a result visual appearance and user experience needs to align with the rest of the portal. In the process, Red Hat Quay and Quay.io will provide a UI experience that is cohesive, easy and effective for both our on-premise and hosted customers that will seamlessly expose users to the full value of RH Quay & Quay.io and the RH product line as a whole. We also plan to capture user’s feedback and integrate it in future iterations.

Why is this important: 

Based on the UX Research, customers have also stated that users “are not so satisfied with the intuitiveness of the UI” therefore there is room for Red Hat Quay and Quay.io to serve their users better with an upgraded user experience.

Dynamic plugin will be implemented  on the hybrid console. Quay.io will keep up with Red hat wide product initiatives to better serve our customer and partners, while raising awareness to current Quay.io users of the other tools available within the RH product suite.

Prioritized deliverables:

• Integrate enhanced user experience integrated into HAC using Patternfly
• User login - authentication is dedicated to Red Hat SSO/login
• Quay UI - embedded into chrome framework
• Top navigation item just for Quay.io

We will accomplish this by: 

• Working with engineering to redirect users from Quay.io to console.redhat.com
• Working with UI/UX team to map out a new UI consistent with RH products yet specific to Quay user’s needs

Attached

• Quay list of priorities to help guide Quay design and engineering teams efforts