Sub-navigation items for the In Page Navigation Component? #4194
-
|
Hi there, I'm looking for a way to include sub-navigation items for the Is there a way to do this currently within the component that I'm missing? If not, I think this could be a great addition! I'm also running into an issue where the 7 navigation items provided aren't always enough for what I'm building. It would be helpful to have more nav items hidden within the component that can be unhidden as needed. See this docs page as an example for when more than 7 navigation items and sub-items are used. Thanks! 
|
Beta Was this translation helpful? Give feedback.
Replies: 2 comments 2 replies
-
|
Disclaimer: This is a very experimental bot using OpenAI's GPT-4. The answers may not be correct, a human will review the answer and update it if necessary. Sorry, I don't know how to help with that. I did do a search though, and I managed to find these other Discussions that might be similar or related to your question. Give them a read to see if they answer your question. If they do, head back here and update this discussion and mark it as answered, pointing others to the related discussion:
|
Beta Was this translation helpful? Give feedback.
-
|
Hey @ericanafziger ! Can you share a Figma file or more about your use case? In Page Navigation is meant to show a set of links/pages with different content. We haven't run into a case yet where a product team has needed to show hierarchy across different pages within the component, so we'd love to learn more about your scenario. On Twilio and Paste docs, those are custom "Table of Contents" components (that isn't actually available as a Paste component yet, but it's in our backlog) and link to headings within a page to show the document structure. Similar but just slightly different use case! |
Beta Was this translation helpful? Give feedback.
-
|
@serifluous thanks for your quick response! In this scenario, I'm using the component to mock up the Twilio Docs site with the addition of a new section/navigation item to support the product initiative. The user would be redirected from an email link (or a link within console) to the Twilio Docs site. If the Table of Contents component is coming, I can just recreate this as a local component for now that matches what we already have live. The In Page Navigation component just matched so closely, I assumed the Twilio Docs were using that component with an additional variant for the sub-items. Thank you! |
Beta Was this translation helpful? Give feedback.
-
|
Ok, nice! If you don't want to start from scratch, here's an example you can pull from our own doc site's Figma files: https://www.figma.com/design/hxQ1dFELwDsryKXeXQ6jMh/Website---default?node-id=403-7345&p=f&t=9j59YO0PVE4Uayqj-0 Let me know if you aren't able to copy out the frames. |
Beta Was this translation helpful? Give feedback.
@serifluous thanks for your quick response! In this scenario, I'm using the component to mock up the Twilio Docs site with the addition of a new section/navigation item to support the product initiative. The user would be redirected from an email link (or a link within console) to the Twilio Docs site.
If the Table of Contents component is coming, I can just recreate this as a local component for now that matches what we already have live. The In Page Navigation component just matched so closely, I assumed the Twilio Docs were using that component with an additional variant for the sub-items.
Thank you!