> For the complete documentation index, see [llms.txt](https://docs.pixiebrix.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.pixiebrix.com/developing-mods/developer-concepts/building-interfaces/styling-elements.md).

# Styling Elements

### Styling Options

Here are just a few things you can do to style elements in your Sidebar:

* Adjust alignment
* Bold or emphasize text
* Change the color or background of text
* Apply a border
* Add margin or padding to adjust space between other elements

![](https://files.cdn.thinkific.com/file_uploads/720267/images/45a/d98/5b4/1691095239223.jpg)

🎯 You can do even more to customize the elements with Bootstrap utility classes. [Bootstrap](https://getbootstrap.com/) is a popular CSS Framework for styling websites. For example, applying certain classes like `d-none` to an element will hide it. If you want something custom with an element, search online (or ask the [PixieBrix community](https://slack.pixiebrix.com/) for help) to find classes you can type in the open text box below the margin and padding sections.

### **Hiding elements**

In some situations, you may also want to hide an element under certain conditions. For instance, you may not want to show a text box if you don't get a useful response from ChatGPT. You can use template language to pass conditional logic in the *Hidden* field to determine whether an element should be shown.

Next, we'll discuss some [advanced elements](/developing-mods/developer-concepts/building-interfaces/adding-advanced-elements.md) you might want to add to your Sidebar besides texts, images, and headers.


---

# 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.pixiebrix.com/developing-mods/developer-concepts/building-interfaces/styling-elements.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.