> 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.md).

# Developer Concepts

If you've read about the [Platform Overview](/platform-overview.md) and got a chance to [Building Your First Mod](/developing-mods/building-your-first-mod.md) but want to learn more, explore these Developer Concepts to learn design patterns and best practices for accomplishing what you need with PixieBrix.

* [Text Template Guide](/developing-mods/developer-concepts/text-template-guide.md): useful for referencing variables in text or running nunjucks templates to perform functions throughout your mod
* [Types of Mods](/developing-mods/developer-concepts/types-of-mods.md): essential for understanding options for triggering a mod and best practices for configuring triggers effectively
* [Using Bricks](/developing-mods/developer-concepts/using-bricks.md): bricks are the building blocks of PixieBrix and this section helps you understand how to best work with them
* [Variables and Data Context](/developing-mods/developer-concepts/variables-and-data-context.md): mods store contextual data and produce data throughout the mod run that you can access and store
* [User Input](/developing-mods/developer-concepts/user-input.md): learn about collecting information and verifying data with users as they run your mods
* [Working With APIs](/developing-mods/developer-concepts/working-with-apis.md): useful for interacting with other tools for your automation
* [Working with Markdown](/developing-mods/developer-concepts/working-with-markdown.md): useful for styling forms and interfaces
* [Control Flow](/developing-mods/developer-concepts/control-flow.md): create multiple paths of execution based on outcomes from previous bricks
* [Transforming Data](/developing-mods/developer-concepts/transforming-data.md): modify from bricks to get information in the format you need
* [Building Interfaces](/developing-mods/developer-concepts/building-interfaces.md): style modals and sidebar panels for interacting with users during automation and displaying responses


---

# 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.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.
