Quick links
Standards FAQ
🔑 Sign in
🆕 Create account
💬 Chat on Slack
📩 [email protected]
🖥 Website standards.site
🐦 Twitter @standards_site
📷 Instagram @standards.site
Design & Editing
Editor overview
Preparing logo assets
Click & Hover Behaviors
Text
Media
Accessibility
Button
Dropdown
Sequence
Navigation Menu
Links
Color
Components
Automations
Tooltips
Files & Downloads
Collaborative editing
Project backups
Workspace & Project Management
Publish & share
Dashboard overview
Workspaces
Workspace members
Viewers
Project access page
Project folders
Project settings
Agency client workflow
Project transfers
Connect a custom domain
SAML SSO integration
Analytics & view history
Your account
Sign in
Plan & Billing
Updating account
Approvals
For multi-page projects, it is especially common to create a table of contents intended to be used across different pages for easy navigation. It could be a primary navigation, a section index, or a footer, but a table of contents is unique in that they’re often present on multiple pages, and their content should stay identical throughout.
Table of contents can be one of the more complex Components since it often requires additional nested Components. Due to the potentially large number of list items, it’s often wise to first save a link item Component when creating a table of contents to ensure consistent height, spacing, text styles, and hover states across all links. This way, you can easily change the style of all the links in your index by simply updating one component.
Once all the items have been added and all the links activated, the entire link index can be saved as a Component.
<aside>
💡 Tip: Setting a Lock content ensures that link text or URLs are accidentally overwritten.
</aside>
Back
Return to Standards Help Center