> For the complete documentation index, see [llms.txt](https://gitbook.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://gitbook.com/docs/manage-your-site/site-structure.md). # Site structure The content on your site lives in its [sections](/docs/create-content/content-structure/space.md). You can add one or multiple sections. GitBook will publish each one and handle the navigation between them. ## Content types Content in your site can serve as one of two different content types, which determine how GitBook treats it and shows it to visitors.

		Cover image (dark)	Cover image			Cover image (dark)
Sections	Split your site into distinct parts — ideal for multiple products or parts of your organization.	/files/jCp95LXOba5SJ05eragF	/files/R89ivAvJAE76NMEwpYNr	/pages/BhYaMwXvRKZYVdHgZM5T		/files/84E3evM3hCGW0RAWhn3C
Content variants	Publish multiple versions of the same content — ideal for localization, versioning, and more.	/files/S17Cf7AIte2wqtwrQJ2f	/files/ztYwJupTRWGUjAvs9Kxs	/pages/VYD1uYVNjSTqX4nw00s3		/files/rhJWb29YSNvxnb5BrpMf

## Managing your site structure By managing the structure of your site, you can also manage your site’s top navigation bar. This navigation bar allows users to jump to different sections and groups. Open the structure editor from **Site structure**, under **General** in the site sidebar. 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 content you created during your site's set-up.

A GitBook screenshot showing a docs site's structure — The structure of a published docs site.

### Adding a section to your docs site To add a [section](/docs/manage-your-site/site-structure/site-sections.md), click the **Add section** button underneath the table and choose the content to add. 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 [variant](/docs/manage-your-site/site-structure/variants.md), click the **Add variant** button in the section you’d like to add to, then choose the content to add. 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. When you add content — as a variant or a section — a name and slug will be generated based on its title. ### Changing sections or variants

A GitBook screenshot showing how to edit a variant — Update a site section or variant.

You can change the name and slug of each of your 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. {% hint style="info" %} 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 [manually create redirects](/docs/publish/site-redirects.md). {% endhint %} {% hint style="info" %} Slugs are unique across your entire organization — each path can only be used on one site, even across different sites. If you see a "path is already taken" error, another site is already using that slug. Choose a slightly varied slug that's still meaningful for your content. {% endhint %} 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. ### Reordering sections or variants 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. 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. To set a section or variant as default, click on the **Actions menu**

in its table row and then click **Set as default**. {% hint style="info" %} Setting content as default removes its slug field, as it will be served from the section root instead. GitBook redirects the old slug to the appropriate path, to ensure visitors keep seeing your content. {% endhint %} ### Remove content from a site To remove a section or variant from a site, open the structure editor from **Site structure**, under **General** in the site sidebar, and find the content you want to remove. Open the **Actions menu**

for the content you want to remove and choose **Remove**. {% hint style="success" %} Removing content from your site will remove it from the published site, but **will not delete the content itself** — you can still find it in [All content](/docs/create-content/content-structure/all-content.md). {% endhint %} If you delete a section's content entirely, the site — along with its settings and customizations — remains available. Deleted content stays in the **Trash** for seven days before it's permanently removed. If the deleted section was your site's default, check that the default is still set correctly. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://gitbook.com/docs/manage-your-site/site-structure.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.