> For the complete documentation index, see [llms.txt](https://wiki.staffplusplus.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://wiki.staffplusplus.org/general-information/other/styling-the-guis/gui-structure.md).

# Gui structure

### GUIs structure

GUIs in staff++ have these main components:

* Container -> The inventory as we see it. 
* Item -> One item in the container represented by an itemstack. 
* Text -> Text consists of one or more TextParts.
* TextPart -> A TextPart holds certain written context.

Using the configuration files we can [select components ](/general-information/other/styling-the-guis/selectors.md)and change their styling.

#### Container

The container is the inventory we are showing.  Using styling we can change:

* The color of the title
* The size of the GUI

#### Item

An Item is a wrapper around an itemstack. Using styling we can change.

* The location of the item
* The color of the name

#### Text & TextParts

The Text component is used whenever we want to display some sort of text inside the component. The component contains one or more TextParts. Text is used for the title of the GUI and the name or Lore of an ItemStack. Every TextPart can be changed using styling:

* TextPart can be hidden/shown
* Color of TextPart can be changed.

### IDs and Classes

The above components can all be assigned 1 id and multiple classes.

#### ID

An id is given to a component to identify it, we can use this id to reference the component inside our style configuration.

**Class**

A class, just like an id, is used to reference a component. The main difference is that a class can reference multiple components. While an id must only reference one. 

A class is also more lenient in how it can reference components.


---

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

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://wiki.staffplusplus.org/general-information/other/styling-the-guis/gui-structure.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.