FYI - I created a related thread here to discuss the technical design questions around aspects of this: O3 side navigation technical design
The fact that most (if not all) of the header and the side navigation is extension-based would seem to give us a lot of flexibility here, and I don’t really see any reason why implementations that are comfortable with and/or expecting the header and navigation to remain as they are should necessarily have to change.
@mksrom , presumably if the same extensions slots and extensions exist and are able to be wired into as they are today to offer the same experience, that would be something we’d want to continue to support, and this alternative design is just a different set of extensions added to various slots in the header and left navigation menus?
The tech design post I link to above is basically trying to figure this out:
- What are done as changes to existing components (eg. the home app or style guide components)?
- What are done as new components and/or new frontend modules that can be used as alternatives?
- What should be the out-of-the-box refapp and module configuration (eg. extension/slot defaults) - if any?
Thoughts?