> For the complete documentation index, see [llms.txt](https://help.brickspacelab.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.brickspacelab.com/paper/advanced-customizations/using-custom-css/popular-css-customizations/change-heading-color.md).

# Change heading color

This guide shows how to change the text color of headings within a section using the theme editor's built-in custom CSS field.

1. In the theme editor, navigate to the section you want to edit.
2. In the settings panel, scroll to the bottom and expand **Custom CSS**.
3. To apply the change across your entire storefront instead, navigate to **Theme settings > Custom CSS**.
4. Paste the following code into the input field and replace `#000000` with your desired hex color code. For example, `#000000` (black) could be changed to `#ffffff` (white).

```css
h3 { color: #000000; }
```


---

# 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://help.brickspacelab.com/paper/advanced-customizations/using-custom-css/popular-css-customizations/change-heading-color.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.
