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
  • Content types
  • Managing your site structure
  • Linking a space to your docs site
  • Changing sections or variants
  • Reordering sections or variants
  • Setting default content
  • Remove content from a site

Was this helpful?

Edit on GitHub
  1. Publishing Documentation

Site structure

Add structure to your published documentation using site sections and variants

Last updated 3 months ago

Was this helpful?

The content on your site comes from in your organization. You can link one or multiple spaces. GitBook will publish each one and handle the navigation between spaces.

Content types

Linked spaces can serve as one of two different content types, which determine how GitBook treats them in relation to each other and shows them to visitors.

Managing your site structure

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, divided into sections and variants.

Your site starts out with a single section with your site's name and a single variant with the space you linked during your site's set-up.

Linking a space to your docs site

When you add a space — as a variant or a section — a name and slug will be generated based on the space’s title.

Changing sections or variants

Reordering sections or variants

You can also use the keyboard to select and move content. Select a section or variant 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 default content

If you have multiple sections in your site, one section will be marked as 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.

If you have multiple variants within a section, one variant will be marked as the default. Like sections, the default variant is shown when visitors arrive on your site, or when they visit a section. Other variants each have a slug that’s appended to the section’s URL.

Setting a space as default removes its slug field, as it will be served from the section root instead. GitBooks redirects the space’s slug to the appropriate path, to ensure visitors keep seeing your content.

Remove content from a site

To remove the content of a space 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 space from your site will remove it from the published site, but will not delete the space or the content within it.

To add a , click the Add 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.

To add a , click the Add variant button in the section you’d like to add to, then choose a space to link. The new variant is then added to the list of variants within the chosen section and will be available to visitors in the variant dropdown on your site.

You can change the name and slug of each of sections and variants by clicking the Edit button in the table row of the item you’d like to edit. This will open a modal. Edit the field(s) you’d like to change, then click the Save button to save.

Changing a linked space's slug will change the space's canonical URL. GitBook will create an automatic redirect from the old URL to the new one. You can also .

To replace a section or variant, first delete it by clicking its Edit button, then click the Delete button in the lower left of the modal. Once the item is deleted, click the Add section or Add variant button to add it again.

Your site displays sections and variants in the order that they appear in your Site structure table. They can be reordered by grabbing the Drag handle and moving it up or down. The changed order will be reflected on your site immediately.

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

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

site section
variant
manually create redirects
spaces
Cover

Content variants

Publish multiple versions of the same content — ideal for localization, versioning, and more.

Cover

Site sections

Split your site into distinct parts — ideal for multiple products or parts of your organization.

The structure of a published docs site.
Update a site section or variant.