# How to make CSS customizations

For developers and to make minor CSS style modifications, use the Code Editor and add your custom CSS overrides at the bottom of `theme.css` located in the **Assets** folder.

![](https://content.gitbook.com/content/0xb0gSOhjZME0es9RuNh/blobs/hApQSnOUrF38YAx1tbo3/theme-css.jpg)

### How to open the code editor

Click on the ellipses (three dots) icon at the top of the Theme Editor to view theme actions, choose Edit code.

![](https://content.gitbook.com/content/0xb0gSOhjZME0es9RuNh/blobs/l1ryvMwPTDABdrjyjQj6/access-theme-code.gif)

### Alternatives and "theme.dev.css"

As you have probably noticed, "theme.css" is minified and you won't be able to easily change the styles. This is where the "theme.dev.css" file comes in handy.

{% hint style="success" %}
This file is not minified and holds the exact same code but in a much more user-friendly layout. While you can certainly change the styles in it, these changes won't take effect on your live store. The reason for this is that this file is not read by default.
{% endhint %}

To activate it, you need to access the "theme.liquid" file and replace the instances of "theme.css" on lines 9 and 44 with "theme.dev.css".

![](https://content.gitbook.com/content/0xb0gSOhjZME0es9RuNh/blobs/OOPSXQMkWfIGJmtZfELU/activate-dev-css.gif)

{% hint style="info" %}
**Note:** Minified CSS is slightly faster so using "theme.css" is also slightly faster.
{% endhint %}


---

# Agent Instructions: 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:

```
GET https://palo-alto.presidiocreative.com/palo-alto-4.0/custom/css-customizations.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.