The State of Docs Report 2025 is live! Dive in and see why docs matter more than ever:
Read the report
LogoLogo
ProductPricingLog inSign up
  • Documentation
  • Developers
  • Guides
  • Changelog
  • Help Center
  • Getting Started
    • GitBook Documentation
    • Quickstart
    • Importing content
    • GitHub & GitLab Sync
      • Enabling GitHub Sync
      • Enabling GitLab Sync
      • Content configuration
      • GitHub pull request preview
      • Commit messages & Autolink
      • Monorepos
      • Troubleshooting
  • Creating Content
    • Formatting your content
      • Inline content
      • Markdown
    • Content structure
      • Spaces
      • Pages
      • Collections
    • Blocks
      • Paragraphs
      • Headings
      • Unordered lists
      • Ordered lists
      • Task lists
      • Hints
      • Quotes
      • Code blocks
      • Files
      • Images
      • Embedded URLs
      • Tables
      • Cards
      • Tabs
      • Expandable
      • Stepper
      • Drawings
      • Math & TeX
      • Page links
    • Reusable content
    • Broken links
    • Searching content
      • Search & Quick find
      • GitBook AI
    • Writing with GitBook AI
    • Version control
  • API References
    • OpenAPI
      • Add an OpenAPI specification
      • Insert API reference in your docs
    • Guides
      • Structuring your API reference
      • Adding custom code samples
      • Managing API operations
      • Describing enums
      • Integrating with CI/CD
  • Extensions reference
  • Publishing Documentation
    • Publish a docs site
      • Public publishing
      • Private publishing with share links
    • Site structure
      • Content variants
      • Site sections
    • Site customization
      • Icons, colors, and themes
      • Layout and structure
      • Extra configuration
    • Set a custom domain
    • Setting a custom subdirectory
      • Configuring a subdirectory with Cloudflare
      • Configuring a subdirectory with Vercel
    • Site settings
    • Site insights
    • Site redirects
    • Visitor authentication
      • Enabling visitor authentication
      • Setting up Auth0
      • Setting up Azure AD
      • Setting up AWS Cognito
      • Setting up Okta
      • Setting up OIDC
      • Setting up a custom backend
  • LLM-ready docs
  • Collaboration
    • Live edits
    • Change requests
    • PDF export
    • Inviting your team
    • Comments
    • Notifications
  • Integrations
    • Install and manage integrations
    • GitHub Copilot
  • Account management
    • Plans
      • Legacy pricing
      • Sponsored site plan
      • Non-profit plan
      • Billing policy
    • Subscription cancellations
    • Personal settings
    • Organization settings
    • Member management
      • Invite or remove members
      • Roles
      • Teams
      • Permissions and inheritance
    • SSO & SAML
      • SSO Members vs non-SSO
  • Resources
    • GitBook UI
    • Keyboard shortcuts
    • Glossary
Powered by GitBook
LogoLogo

Resources

  • Showcase
  • Enterprise
  • Status

Company

  • Careers
  • Blog
  • Community

Policies

  • Subprocessors
  • Terms of Service
On this page
  • Adding a section to your docs site
  • Create a site section group
  • Editing a section
  • Reordering sections
  • Setting a default section
  • Remove a section

Was this helpful?

Edit on GitHub
  1. Publishing Documentation
  2. Site structure

Site sections

Add multiple products to your site as site sections and create a content hub with tabs to access all your content

Last updated 1 month ago

Was this helpful?

With site sections, you can centralize all your documentation and create a seamless experience for your users.

Site sections are perfect for organizing your documentation — whether you’re managing separate products, or catering to both end-users and developers with content tailored to each.

Sections or variants?

Each site section is a space in GitBook. You can create site sections from any space you like, but we recommend you use sections as semantically different parts of your docs.

Adding a section to your docs site

From your docs site’s dashboard, open the Settings tab in the site header, then click Structure. Here you can see all the content of your site.

To add a site section, click the New section button underneath the table and choose a space to link as a section. The new section is then added to the table and will be available to visitors as a tab at the top of your site.

Create a site section group

You can group site sections together under a single heading. Site section groups will appear as a drop-down in your site’s nav. Site sections in a group can also include an optional description, which appears below the section title in the drop-down menu.

To create a group, click the arrow next to the New section button and choose New section group. Give your new group a name, then click Add section in the modal to add sections to your group. You can add existing sections of your site to the new group, or select another space you want to add using the menu.

Editing a section

Site sections within a group can also optionally display a description, which will appear in the drop-down menu of your site’s nav bar when the section group is hovered. See the image at the top of this page to see an example of how this can look in your published documentation.

Reordering sections

You can also use the keyboard to select and move content: select a section with the space bar, then use the arrow keys to move it up or down. Hit the space bar again to confirm the new position.

Setting a default section

If you have multiple sections in your site, one section will be marked as the default. This section is shown when visitors arrive on your site, and is served from your site’s root URL. Other sections each have a slug that is appended to the root URL.

Remove a section

To remove a section from a site, open the Settings tab from your docs site dashboard, then click Structure to find the content you want to remove.

Removing a section from your site will remove it — and all variants within it — from the published site, but will not delete any of the spaces or the content within them.

You can also . Doing so will create a drop-down menu in your navigation bar — ideal for adding hierarchy to your site sections.

If you want to add variations of the same content — such as localizations or historical versions of the same product — consider using instead.

You can change the name, icon and slug of each of your sections by tapping the Edit button in the table row of the section you’d like to edit. This will open a modal. Edit the field(s) you’d like to change, then click the Save button. You can also delete the variant by clicking the Delete variant button in the lower left.

Changing a section’s slug will change its canonical URL. GitBook will create an automatic redirect from the old URL to the new one. You can also .

Your site displays sections in the order that they appear in your Site structure table. Sections can be reordered by grabbing the Drag handle and moving it up or down. All the spaces within that section will be moved with it. The changed order will be reflected on your site immediately.

To set a section as default, click on the Actions menu in the section's table row and then click Set as default.

To remove a section from a site, click the Settings button from your docs site dashboard, then click Structure to find the content you want to remove. Click the Edit button next to the section you want to remove, then click the Delete button in the lower left of the modal. This will remove the section, along with all the variants within it, from the published site. It will not delete the spaces itself, or the content within them.

Open the Actions menu for the space you want to remove and choose Remove.

content variants
manually create redirects
group site sections together

This feature is available on the .

Ultimate site plan
Example of a GitBook site with site sections
Add structure to your docs with site sections.