[META] 7.14 Solution Nav implementation

[cchaos]

This is a Kibana platform wide (all solutions) meta ticket for tasks needed to be done for the implementation of the proposed solution navigation for the 7.14 release.

Coordinator: @cchaos

For 7.14, the main path for each solution team is to convert their current page layout construction to utilize the KibanaPageTemplate component with a nested EuiSideNav component for their navigation items. The Kibana Core team will be working simultaneously to update the Kibana specific component.

Be sure to reference these Page Layout Guidelines as you move through conversions. They will get continually updated as more common patterns emerge.

KibanaPageTemplate

• [@cchaos @myasonik] Provide a general service/component for applying specific page layouts (POC: [WIP] Page layouts cchaos/kibana#24)
  • Unifying converting listing pages to new layout  #98651 Introduction of the KibanaPageTemplate component with basic empty page configuration
  • [KibanaPageLayout] Solution Nav specific styles & props #100089 Adds quick render of EuiSideNav and title embellishments by pass solutionNav to KibanaPageTemplate
  • [ ] Add emptyPrompt and loadingPrompt props to KibanaPageTemplate Follow up in 7.15
  • [KibanaPageTemplate] Adds collapsibility to solutionNav #103192

Kibana Core/Platform

• [@TinaHeiligers] Add data pages Home page add sample data UI contains a lot of blank space #102260

Analytics solution

This is the only solution group that will not have an implementation of solution navigation. Though their pages will still need to be converted to use the KibanaPageTemplate. Most likely they'll be the first group of applications to use the provided platform service.

• [@cchaos @myasonik] Convert an initial set of applications to the new KibanaPageLayout
• [@ryankeairns] Fix all layout related fixes listed in [META] Analytics Solution fixes needed for page layouts #98827

Machine Learning

• [@peteharverson @cchaos] Discuss possibility of ML converting to side nav
  • Discussed this and ML's navigation is too small.
• [@cchaos] Tidy up of the existing tabs structure/style [Page layouts] Some light fixes #103197

Observability solution

• [@katefarrar] Finalize navigation items ([Observability] Implement Solution Navigation #98212)
• [@weltenwort] Add shared observability page template and navigation [Logs UI] Add shared observability page template and navigation #99380
• [APM] Convert to the new Observability page template and remove tab navigation from the global views [APM] Convert to the new Observability page template and remove tab navigation from the global views #99883
• [Uptime] Remove tabs navigation in place of the new solution navigation [Uptime] Remove tabs navigation in place of the new solution navigation #99901
• [Logs] Remove tab navigation in place of the new solution navigation [Logs] Remove tab navigation in place of the new solution navigation #99966
• [Metrics] Remove tab navigation in place of the new solution navigation [Metrics] Remove tab navigation in place of the new solution navigation #99970
• [Fleet] Adjust Fleet layout to match the new page pattern @kpollich [Fleet + Integrations UI] Migrate Fleet UI to new tabbed layout #101828

Security solution

• [@bfishel] [UX] Proposed side nav for Security (https://github.com/elastic/security-team/issues/1070)
• [@michaelolo24 @semd] Security Solution Navigation (https://github.com/elastic/security-team/issues/1101)

Enterprise search

This solution is already using a custom version of the side navigation implementation. The main goal will be to align with the other solutions by moving the stock EUI components.

• App Search: [@constancecchen] Convert SideNav to EUI's Solution Nav (https://github.com/elastic/app-search-team/issues/1715)
• Workplace Search: [@scottybollinger] Convert all pages to use KibanaPageTemplate and EuiSideNav (https://github.com/elastic/workplace-search-team/issues/1712)

Management

This section/app is a mix of many solutions. The Core team will work on an initial conversion (work already started here cchaos#24 (comment)) then create a meta ticket for assigning further teams to the individual pages.

• [@cchaos @myasonik @mattkime] Initial conversion of management app to KibanaPageTemplate [Stack Management] Converted to use KibanaPageTemplate (sort of) #101335
• [Meta] Stack Management page conversions for new layout [Meta] Stack Management page conversions for new layout #101336

[elasticmachine]

Pinging @elastic/kibana-design (Team:Kibana-Design)