No vertical in-page navigation #3307
-
|
Hello team, Per paste guidance we should be using in-page navigation instead of tabs if we are navigating user to a different URL per tab. If that's the case, should we use vertical tabs instead or use 2 horizontal in-page navigation? I personally think two horizontal in-page navigation is bad UX. Thank you so much for your help! 
|
Beta Was this translation helpful? Give feedback.
Replies: 3 comments 5 replies
-
|
Right now, that is correct, yes. We were likely not presented a use case for vertical in page navigation, as folks didn't tend to have that depth of IA. Where folks were using these kinds of components, they were just switching content and didn't have a route attached to the views. If each of those actually have a deep link url, that's actually very cool, in page navigation just doesn't support it right now. I don't think you should double stack horizontal navs, but equally we shouldn't be using Tabs for navigation as it's completely the wrong semantic if each of those items do actually change the url when you action them. We can take a dependency for a new variant, but I would be curious to hear about further use cases outside this section? If it's not super common, it will be difficult to prioritise due to the volume of other requests we have, which have much higher reuse. Do you happen to know how common this is? |
Beta Was this translation helpful? Give feedback.
-
|
Hi @SiTaggart, thanks for your response! This is actually a very common use case across Segment. It appears in basically every Settings page for each of the products. Each of the vertical tabs currently in Segment has it's own URL. I can provide some screenshots if needed. |
Beta Was this translation helpful? Give feedback.
-
|
Besides in Unify settings, it also appears in every instances of a source settings page and destinations settings page, and privacy settings page. |
Beta Was this translation helpful? Give feedback.
-
|
Another thing that's related to in-page navigation is that Segment uses a lot of tertiary tabs with tables, and each of them have a different URL. (see screenshots) If we did the migration we will end up with stacking two horizontal in-page navigation again... |
Beta Was this translation helpful? Give feedback.
-
|
I suspect visually, when comparing components by components, everything is covered in isolation. For example, folks might have seen vertical tabs, considered them actual tabs, and called it done. Same with horizontal tabs and in page navigation. On their own, the use cases are covered, but how they are implemented in the product might not have been fully considered by the Segment team at the time. That is understandable, as there were a lot of things discovered once people started getting into the product. Things like undocumented custom components. As these come up, we encourage the app foundations team to reevaluate what they need from Paste and file dependencies as they see fit, or continue creating custom components as has been the case previously, even working with Evergreen. |
Beta Was this translation helpful? Give feedback.
-
|
Hi, we have a ticket to fix this in our backlog. You can follow along here: https://twilio-productivity.atlassian.net/browse/DS-166. |
Beta Was this translation helpful? Give feedback.
-
|
Vertical in page nav is released in Core |
Beta Was this translation helpful? Give feedback.
-
|
great news! I'll let my team know! Thank you so much |
Beta Was this translation helpful? Give feedback.
Hi, we have a ticket to fix this in our backlog. You can follow along here: https://twilio-productivity.atlassian.net/browse/DS-166.