> For the complete documentation index, see [llms.txt](https://docs.lufavo.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.lufavo.com/roomfolk/theme-settings/colors.md).

# Colors

**Theme settings → Colors**

Roomfolk uses color schemes rather than individual color settings scattered through the theme. You set up a scheme once, and any section can be pointed at it.

## How schemes work

Every section has a **Color scheme** setting near the bottom of its settings. Change a scheme here and every section using it updates at once.

Roomfolk ships with five:

| Scheme   | Used for                                                                                           |
| -------- | -------------------------------------------------------------------------------------------------- |
| Scheme 1 | The default. White page, dark text. Most sections.                                                 |
| Scheme 2 | A very slightly tinted page, for separating a section from its neighbours without a hard edge.     |
| Scheme 3 | Dark page, light text.                                                                             |
| Scheme 4 | Your accent color as the background. Used for the announcement bar and the FAQ section by default. |
| Scheme 5 | A warm neutral.                                                                                    |

You can edit any of them, and add more with **Add scheme**.

## What is in a scheme

| Color                  | What it controls                                                                                           |
| ---------------------- | ---------------------------------------------------------------------------------------------------------- |
| Background             | The page color behind the section.                                                                         |
| Background gradient    | An optional gradient that replaces the flat background.                                                    |
| Text                   | Body text and headings.                                                                                    |
| Button                 | The fill of primary buttons, and the accent color used for the third hero heading line, kickers and links. |
| Button label           | Text on primary buttons.                                                                                   |
| Secondary button label | The outline and label of secondary buttons.                                                                |
| Shadow                 | The color shadows are drawn in.                                                                            |

## Colors the theme works out for itself

You do not set borders, muted text, input backgrounds or placeholder text. Roomfolk derives them from the background and text colors of each scheme, which means two things worth knowing:

* A scheme always holds together. Change the background from white to near-black and the borders, muted text and fields follow.
* **Contrast is protected.** Muted text — post dates, testimonial attributions, product excerpts — is calculated to stay legible against its own background. All five shipped schemes clear the accessibility threshold for body text.

If you set a scheme with text and background too close together, the derived colors follow it down. Keep a clear difference between the two.

## Badge colors

**Theme settings → Badges** has separate schemes for the **On sale** and **Sold out** badges, so they stand out against whatever scheme the product card uses. Both default to scheme 4.


---

# 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.lufavo.com/roomfolk/theme-settings/colors.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.