kibana icon indicating copy to clipboard operation
kibana copied to clipboard
verified publisher icon elastic

[Workspace Chrome] Visual Improvements

Open tsullivan opened this issue 1 month ago • 3 comments

Summary

These visual changes have been pulled out of an exploration POC: https://github.com/elastic/kibana/pull/235808

~~Depends on https://github.com/elastic/eui/pull/9220~~ Depends on https://github.com/elastic/kibana/pull/244866

Changes:

Area Change
Nav bar and secondary nav bar
  • shaded
    		•
    Global header background
  • shaded
    		•
    Application space, App menu bar
  • globally consistent white background
  • drop shadow
    		•
    Left side navigation
  • pushes the global header to the right
    		•
    Between the global header and the nav bar and between the logo and the nav sections
  • New divider style, doesn't touch the boundaries of the container
    		•

    Checklist

    Check the PR satisfies following conditions.

    Reviewers should verify this PR satisfies this list as well.

    • [ ] Audit all Kibana pages for consistency of stylistic changes
    • ~~[ ] Any text added follows EUI's writing guidelines, uses sentence case text and includes i18n support~~
    • ~~[ ] Documentation was added for features that require explanation or tutorials~~
    • ~~[ ] Unit or functional tests were updated or added to match the most common scenarios~~
    • ~~[ ] If a plugin configuration key changed, check if it needs to be allowlisted in the cloud and added to the docker list~~
    • ~~[ ] This was checked for breaking HTTP API changes, and any breaking changes have been approved by the breaking-change committee. The release_note:breaking label should be applied in these situations.~~
    • ~~[ ] Flaky Test Runner was used on any tests changed~~
    • ~~[ ] The PR description includes the appropriate Release Notes section, and the correct release_note:* label is applied per the guidelines~~
    • ~~[ ] Review the backport guidelines and apply applicable backport:* labels.~~

    Identify risks

    ~~Does this PR introduce any risks? For example, consider risks like hard to test bugs, performance regression, potential of data loss.~~

    ~~Describe the risk, its severity, and mitigation for each identified risk. Invite stakeholders and evaluate how to proceed before merging.~~

    tsullivan avatar Nov 17 '25 21:11 tsullivan

    :robot: Jobs for this PR can be triggered through checkboxes. :construction:

    :information_source: To trigger the CI, please tick the checkbox below :point_down:

    • [ ] Click to trigger kibana-pull-request for this PR!
    • [ ] Click to trigger kibana-deploy-project-from-pr for this PR!
    • [ ] Click to trigger kibana-deploy-cloud-from-pr for this PR!

    elasticmachine avatar Nov 17 '25 21:11 elasticmachine

    Cloud deployments require a Github label, please add ci:cloud-deploy or ci:cloud-redeploy and trigger the job through the checkbox again.

    kibanamachine avatar Nov 18 '25 00:11 kibanamachine

    :broken_heart: Build Failed

    Failed CI Steps

    History

    • :broken_heart: Build #364643 failed 2c21bd57097dcba0e90f0cb8d6907ef746d737d9
    • :broken_heart: Build #362133 failed 87a5eb55a488a6e8606fb3a65309fb59b2772104
    • :broken_heart: Build #362129 failed e97d4e1051259f71d03700416090779af18a8a9f

    elasticmachine avatar Dec 01 '25 19:12 elasticmachine

    Replace with https://github.com/elastic/kibana/pull/245898

    tsullivan avatar Dec 10 '25 17:12 tsullivan