Move the Harbor integration from `Operate` to `Deploy`
Proposal
In the current navigation, you can find the package registry, container registry, model registry, terraform registry, dependency proxy, and (coming soon) the integration with Google Artifact Registry.
The problem is that the Harbor registry is under Operate
.
This issue proposes moving the Harbor registry under the Deploy
navigation to align all of the similar products.
Other locations that were considered
Checklist
-
Review the handbook page for navigation changes -
Add relevant information to the issue description detailing your proposal, including usage and business drivers. -
List at least two other places you considered to introduce your feature -
Add relevant designs to the Design Management area of the issue -
Ensure your UI suggestion align with the Documentation Style Guide -
Engage Technical Writing. They can help craft a term that best describes the feature(s) you’re proposing. -
Follow the product development workflow validation process to ensure you are solving a well understood problem and that the proposed change is understandable and non-disruptive to users. Navigation-specific research is mandatory for additions or when restructuring. -
Engage the Foundations Product Manager for approval. The Foundations DRI (@jtucker_gl) will work with UX partners in product design, research, and technical writing, as applicable. -
Consider whether you need to communicate the change somehow, or if you will have an interim period in the UI where your item will live in more than one place. -
Ensure engineers are familiar with the implementation steps for navigation.
Edited by Jeff Tucker