-
Notifications
You must be signed in to change notification settings - Fork 8.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[APM] Implement new design for "All services" and "Service groups" toggle #142084
Comments
Pinging @elastic/apm-ui (Team:APM) |
@chrisdistasio / @boriskirov currently we show the |
@cauemarcondes I can move the tour to anchor on the new "All services" half of the button group. |
We had a productive discussion with @ogupte about how we can make an impactful change in the navigation experience:
|
Thank you, i'll make change with these updates, will move this issue back to "In Progress" |
* [APM] Adds button group to navigate to "All services" (#142084) * [CI] Auto-commit changed files from 'node scripts/precommit_hook.js --ref HEAD~1..HEAD --fix' * Adds button group legend, fixes spacing and translation IDs * makes the button group part of the page template * addresses feedback * addressed feedback: - Use 'All services' as the default landing page - swap order of button group -> All services, Service groups - move tour from the create button to service group half of the button group - have service groups always enabled but marked Beta - removed some branching logic in routes / page templates - add 'Send feedback' link - fixed service count in cards * fixes tests and deep links * change button group to single type Co-authored-by: kibanamachine <[email protected]>
After collecting feedback on the service groups feature, we'd like to streamline the UI a little and remove the "All services" service group entry that appears once an initial group has been created and present it as an EuiButtonGroup below the "Services" header instead. Allowing the user to quickly toggle between experiences.
Before
After
Notes
Links
The text was updated successfully, but these errors were encountered: