Popover component: Thoughts and advice #815
-
Hi all — we're exploring using the popover component to provide more information about Conversations for users who aren't familiar with the product. In this use case a user is within a Programmable Messaging service and will be exploring what they want their service to do with incoming messages. They may not have an understanding on what Conversations is so instead of forcing the user away to Conversations straight away, we are thinking of providing them a brief explanation on what the API offers with an explicit link to find out more. This link will take them to Conversations on Console. Would love any thoughts or insight on using the popover component in this context. |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments 4 replies
-
Hey @kevhealy-git - I think this looks great! This is a good use case for a popover. I like that the user doesn't get navigated to a new page right away, but instead gets a glimpse of the info in the popover first. |
Beta Was this translation helpful? Give feedback.
-
Hi @kevhealy-git, quick clarifying question for this one; Is the intention that "Conversations" is also still a link? The reason I ask is that for a number of limitations and accessibility reasons, an element can't be two things at the same. An element on the whole can only perform a single distinct action; "I am a link to a new page", "I launch a modal", "I launch a popover". If you are still intending to have the word conversations be a link to a new page, then you would need another mechanism to launch the popover. If the word conversations only launches the popover on click, then that's fine, the only difference being you'd be using a link style button, which is not underlined. |
Beta Was this translation helpful? Give feedback.
Hey @kevhealy-git - I think this looks great! This is a good use case for a popover. I like that the user doesn't get navigated to a new page right away, but instead gets a glimpse of the info in the popover first.