> 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/motors-theme-documentation/content/setting-up-content-pages-and-posts.md).

# Setting up Content Pages and Posts

All pages can be created as simple content pages or built by means of Visual Composer page builder. You will need to first set up the page and then add and set up content blocks. Just add a row and add the modules to row from the Visual Composer dashboard.

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

Now you can choose how to compose your template. Add Content modules, Testimonials, etc. You have everything to realize your imagination.

We have also included extension packages for Visual Composer. You can use them free.

Just pick the module you like and add it to the row. Then you can edit it.

You can also edit the row background, add video or parallax images to the background. Just click on Row edit icon and you will see the options & features, which are available for this row.

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

Custom added shortcodes in our theme are on a separate tab:

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

Besides this, each page contains these options which include header color or background image, title fonts and colors, breadcrumbs and button settings:

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


---

# 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/motors-theme-documentation/content/setting-up-content-pages-and-posts.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.