> 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.md).
# Building Interfaces
Often you'll want to display content that is produced when your mod runs. There are a handful of ways to do that!
### **Bricks for rendering content**
* Display Temporary Information / Show Sidebar
* Show a modal or sidebar form (Learn more in [User Input](/developing-mods/developer-concepts/user-input.md))
* Window Alert
* Show a notes modal
You also might be interested in these, although they'll typically only be used in one of the bricks above.
* Render Document
* HTML Renderer
* Render Markdown
### Using the Display Temporary Information brick
When building mods, you'll usually find yourself using the **Display Temporary Information** brick. This is the GOAT (Greatest of All Time) rendering brick and is the one most commonly used because it runs an action and opens a Sidebar to display the results of that action (without leaving it permanently in your Sidebar).
You can customize what's displayed in the sidebar content, including setting user input with forms, displaying text, and adding buttons that trigger events.
Something like this!
When configuring the Display Temporary Information brick, you'll choose the title at the top, choose the format to display it in and determine when it refreshes. For instance, you might choose the `statechange` refreshTrigger if you want to update the content whenever a form is filled out or if something else changes on the page, updating the state. To learn more about working with state changes, read the [Page State docs](/developing-mods/developer-concepts/variables-and-data-context/advanced-using-page-state.md).
Keep reading to learn more about interacting with and customizing Display Temporary Information or Render Document bricks.
---
# 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.md?ask=&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.
