> For the complete documentation index, see [llms.txt](https://docs.stylemixthemes.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.stylemixthemes.com/splash-theme-documentation/theme-features/how-to-set-up-the-sidebar.md).

# How to set up the sidebar

In this theme we paid special attention to Sidebars for your biggest convenience and on multiple previous requests.

We have two types of sidebar: right sidebar and left sidebar, which can be selected for both of archive and single posts/pages.

In addition to that, you can add/create a new sidebar with VC Widgets/Elements, in this case you will need to go here:

![](https://support.stylemixthemes.com/storage/stm-manuals/April2020/sidebars-1.jpeg)

Edit or create a new sidebar, and add any sections you need by means of Visual Composer

![](https://support.stylemixthemes.com/storage/stm-manuals/April2020/sidebars-2.jpeg)

For archive pages you can set sidebar options up via **Appearance -> Customize -> Layout**.

For single pages/posts you can add sidebar via **Widgetised Sidebar** or **STM Sidebar** VC element

![](https://support.stylemixthemes.com/storage/stm-manuals/April2020/sidebars-3.jpg)


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.stylemixthemes.com/splash-theme-documentation/theme-features/how-to-set-up-the-sidebar.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.