Skip to content
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

EUI pattern for in product help #2677

Closed
gchaps opened this issue Dec 17, 2019 · 7 comments
Closed

EUI pattern for in product help #2677

gchaps opened this issue Dec 17, 2019 · 7 comments
Assignees
Labels
design decision documentation Issues or PRs that only affect documentation - will not need changelog entries

Comments

@gchaps
Copy link
Contributor

gchaps commented Dec 17, 2019

Sometimes users need more help than can be provided in the UI copy and tooltips. It would be nice to have a pattern for in product help.

I've seen some apps use the flyout on the right. If this is the pattern we want, can we get some guidelines on how to use it, such as width size?

@chandlerprall chandlerprall added the documentation Issues or PRs that only affect documentation - will not need changelog entries label Dec 19, 2019
@cchaos cchaos added this to Needs triage/design in Documentation Tools, Chores and Guidelines via automation Sep 20, 2020
@cchaos cchaos added this to Needs triage/design in Design via automation Sep 20, 2020
@github-actions
Copy link

👋 Hey there. This issue hasn't had any activity for 180 days. We'll automatically close it if that trend continues for another week. If you feel this issue is still valid and needs attention please let us know with a comment.

@cchaos cchaos moved this from Needs triage/design to Guidelines in Documentation Tools, Chores and Guidelines Mar 19, 2021
@gchaps
Copy link
Contributor Author

gchaps commented Jun 7, 2021

Can we revive this issue? This is a topic I'm hearing a lot about from both devs and PMs. Lens is now using a "How it works" pop-up, and ML is following. If this, or any other way type of in-product help is a recommended way for Kibana, we should have guidelines for how to use it.

@miukimiu
Copy link
Contributor

miukimiu commented Jun 7, 2021

I agree we should have guidelines. I'm going to investigate what is being done in Kibana and see how we can bring some guidelines to EUI.

@miukimiu miukimiu self-assigned this Jun 7, 2021
@cchaos
Copy link
Contributor

cchaos commented Aug 15, 2021

Came across this video today that I thought might be helpful. Specifically this callout:

Screen Shot 2021-08-15 at 11 44 00 AM

@miukimiu
Copy link
Contributor

Today, @cristina-eleonora, @gchaps, @kyrspl and I, had a meeting and we now have a plan to follow up on this issue.

Finish the Figma prototype

Cristina started this Figma project and the idea is to finish the guidelines there. After that and if we all agree on the content we can move them to our EUI Docs.

A new tabbed page under EUI Docs Guidelines

The idea is to create a new tabbed page called "In-product help" under Guidelines. Following the Writing page structure:

  • Guidelines - This page will contain the guidelines
  • Examples - This page will contain some components showing some usage examples

@miukimiu
Copy link
Contributor

@cristina-eleonora, @kyrspl, @cchaos just to give some updates what was agreed with @gchaps is the in-product help will live in tech-writing-guidelines. You can find the work in progress here: https://github.com/elastic/tech-writing-guidelines/blob/main/docs/in-prod-help.mdx.

But we also want to make sure EUI follows those guidelines. So in EUI, the idea is to update all the components to reflect those guidelines:

  • EuiTooltip - Should have guidelines and the examples should be better
  • EuiFlyout - Should also have guidelines (Patterns to trigger a flyout, widths to use)
  • EuiPopover - Should also have guidelines.
  • EuiLink - We should explain when it's ok to use external={true}. Also provide some examples with Learn more links.

@daveyholler
Copy link
Contributor

@miukimiu will create separate issues for the still-relevant work.

Documentation Tools, Chores and Guidelines automation moved this from Guidelines to Closed Nov 28, 2022
Design automation moved this from Needs triage/design to Closed Nov 28, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
design decision documentation Issues or PRs that only affect documentation - will not need changelog entries
Projects
No open projects
Development

No branches or pull requests

5 participants