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

Phase 2: MVP - Quay.io UI Launch

XMLWordPrintable

    • UI Quay.io MVP - Part II
    • False
    • None
    • False
    • Not Selected
    • To Do
    • 0% To Do, 0% In Progress, 100% Done

       

      Why is this important?

      At our face-to-face, Engineering determined the "definition of done" for the new Quay MVP UI as the following before deploying the UI publicly on Quay.io.

      Additionally other ** requirements integral to our launch in the UI is API configuration to enable scalability and implementing a UX Analytic tool to track user activity before and after our launch.

      These requirements ensure baseline parity with the current Quay.io UI that will enable user to have the most essential functionality required before demoing the beta version of the product.

      Known Constraints

      The first launch on quay.io will be without sign up page flow and will require users old login information

      UI Requirements for Launch :

      • Settings
        • User
        • Org
        • Repo
        • Authentication
        • Robot tokens
        • OAuth
        • Teams and Membership
        • Default Permissions
      • Routing
      • Footer

       

       

       

            doconnor@redhat.com Dave O'Connor
            qberry@redhat.com Quiana Berry
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: