-
Notifications
You must be signed in to change notification settings - Fork 8.3k
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
Create button in empty state for dashboard #62070
Comments
Pinging @elastic/kibana-app (Team:KibanaApp) |
Pinging @elastic/kibana-design (Team:Design) |
While I agree this screenshot looks odd, and the buttons could be more consistent (e.g. use the same icon and icon placement), there are a few things to keep in mind as this project is still mid flight:
I share all that for context, but it doesn't mean there isn't room for improvement. Looking at this again with a fresh set of eyes, I would propose unifying the button designs in the menu and flyout and use a non-filled button in the empty panel. |
Quick question about the "Create new" button in the top menu. Is that to create a new object for a panel or a whole new dashboard? Looking at the rest of the menu I see "Add" but I no longer see the old "New" menu item that originally created the new dashboard. |
Create a new object/panel (opens the Visualize type picker). Objects created from Dashboard would live with the dashboard, as opposed to being added to the Visualize 'library'. That part is not quite complete but there is/will be an emphasis on the 'Create new' route vs 'Add' (which is being intentionally downplayed). |
This screenshots shows three buttons with the wording "Create new". The EUI button guidelines say to avoid the wording "Create new" and instead follow "Create" with a noun, such as "Create visualization" or "Create dashboard".
The text was updated successfully, but these errors were encountered: