(setting component to quay.io as this work should be done alongside our hosted service work)

Need a design that shows how the new UI work being done to integrate quay.io into the Hybrid Application Console can be re-used by Red Hat Quay for on-premise customers.

How does the UI code need to be structured or written to be reusable across quay.io the service and Red Hat Quay the product?

What dependencies does the use of Dynamic Plugins mandate for no-premise Quay?

What impact might the use of dynamic plugins for on-premise Quay have on our overall HAC integration architecture?