> For the complete documentation index, see [llms.txt](https://docs.simplebooth.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.simplebooth.com/virtual-booth-setup/branding-and-customizations/splash-page-customizations/basic-customizations.md).

# Basic Customizations

Adjust the main components of your settings.

***

#### Header

The header appears at the top of your splash page and is one of the first things participants see when opening your booth.

* **Heading**: Add your main welcome message. This appears most prominently on the page (limit 80 characters).
* **Subheading**: Add a smaller line of text to welcome or prompt participants (limit 80 characters).

***

#### Color Scheme

Customize the appearance of the page. 

* **Text Color**: Choose a font color that stands out clearly against your background.
* **Background Color**: Solid and gradient (linear or radial) colors are supported, up to two (2) colors. 

***

{% hint style="success" %}

#### Plan Availability

:white\_check\_mark: Core, Plus, Pro, Select

:x: Lite
{% endhint %}


---

# 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://docs.simplebooth.com/virtual-booth-setup/branding-and-customizations/splash-page-customizations/basic-customizations.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.