> For the complete documentation index, see [llms.txt](https://norbertrostaing.gitbook.io/blinderkitten/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://norbertrostaing.gitbook.io/blinderkitten/first-steps/some-infos-about-the-interface.md).

# Some infos about the interface

BlinderKitten is built on top of the user interface OrganicUI.

When you select somthing in any list or grid, the selected content will be displayed in the "Inspector" tab. This tab will contains every information about the selected item and will allow you to edit all fields.

When you need to work on a defined list, for example fixtures, you can double clic on the tab you want to focus. Organic UI will hide other tabs and let you focus on one list with the inspector aside.\
To leave this view, double clic again on the focused tab.

You might think that your current layout is nice for programming but not handy during your live show. Organic UI let you create as many layouts as you want and store /recall them as you want in the menu view -> layout


---

# 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://norbertrostaing.gitbook.io/blinderkitten/first-steps/some-infos-about-the-interface.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.