馃帹 Design: Moving from Admin Area to Organization for self-managed users
Problem
Currently all Organization-related functionality is feature flagged so that we can roll it out on GitLab.com specifically to start with. However, in the mid term we also want to enable Organizations for self-managed customers. As a lot of the existing Admin Area functionality is going to move to Organizations, we need to decide what we want the User Experience to be during this transition. See also: 馃帹 Design: Transition to Organization for self-m... (#383267). Could we define what an iterative transition for self-managed customers would look like? How could Admin Area and Organization co-exist while functionality is moved from one to the other?
Note: The Admin Area will probably never cease to exist and remain a place a to host hardware settings and an Organization overview.
Proposal
Phase1 - Organization MVC
Organization | Admin | Navigation |
---|---|---|
|
|
|
Phase2 - Transition phase
Organization | Admin | Navigation |
---|---|---|
|
|
|
Phase3 - Transition phase complete
Organization | Admin | Navigation |
---|---|---|
|
|
|