Uploaded image for project: 'Project Quay'
  1. Project Quay
  2. PROJQUAY-943

Quay UI enhancements


    • Icon: Epic Epic
    • Resolution: Unresolved
    • Icon: Major Major
    • None
    • None
    • quay
    • None
    • Quay UI enhancements
    • To Do
    • 58% To Do, 0% In Progress, 42% Done
    • 0

      Goal: Enhance the performance and effectiveness of the Quay UI.

      Why is this important: Repository owners and first-time users of Quay or a particular repository will use the UI to configure and explore contents. Repository owners expects efficiency gains by using the UI as opposed to the APIs, for example for batch / group operators. Users require a responsive interface while not putting the Quay services under massive load.

      Prioritized deliverables

      • responsive frontends that are easy on the API server side
      • batch operations for most common tasks
      • regex patterns in search fields
      • organizations as top level navigational concept

      Optional deliverables

      • less clicks to get a pull command
      • navigation shortcuts to sub menus in list views
      • status icons of repos with build status, notifications, private / public status

            Unassigned Unassigned
            DanielMesser Daniel Messer
            1 Vote for this issue
            8 Start watching this issue