# Custom Theme for 'Global' variables

**URL:** <https://forum.inductiveautomation.com/t/custom-theme-for-global-variables/58608>\
**Category:** Ignition\
**Tags:** ignition81, perspective\
**Created:** [April 19, 2022, 7:43pm UTC](https://forum.inductiveautomation.com/t/custom-theme-for-global-variables/58608 "2022-04-19T19:43:48Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![jlandwerlen](https://avatars.discourse-cdn.com/v4/letter/j/bc8723/32.png) [@jlandwerlen](https://forum.inductiveautomation.com/u/jlandwerlen)\
**Post date:** [April 19, 2022, 7:43pm UTC](https://forum.inductiveautomation.com/t/custom-theme-for-global-variables/58608/1 "2022-04-19T19:43:48Z")

</div>

I would like to create a theme to be used for global variables. Essentially variables like a color to be used for motor running/stopped, valves open/closed, etc. So if I create this theme and name it ‘myTheme’, if I import into each of the entry point CSS (dark, dark-cook, dark-warm, light, light-cool, light-warm) then if I select any one of themes my custom theme will still work? And, will this also cover me from upgrades and restarts?

---

<div class="post-metadata">

**Author:** ![pturmel](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/pturmel/32/3295_2.png) [@pturmel](https://forum.inductiveautomation.com/u/pturmel)\
**Post date:** [April 19, 2022, 8:06pm UTC](https://forum.inductiveautomation.com/t/custom-theme-for-global-variables/58608/2 "2022-04-19T20:06:42Z")

</div>

> [@jlandwerlen](#):
>
> And, will this also cover me from upgrades and restarts?

It should work, but upgrades will wipe this out. You can't modify the supplied themes.

---

<div class="post-metadata">

**Author:** ![jlandwerlen](https://avatars.discourse-cdn.com/v4/letter/j/bc8723/32.png) [@jlandwerlen](https://forum.inductiveautomation.com/u/jlandwerlen)\
**Post date:** [April 19, 2022, 8:15pm UTC](https://forum.inductiveautomation.com/t/custom-theme-for-global-variables/58608/3 "2022-04-19T20:15:43Z")

</div>

That’s what I’m worried about and trying to clarify. Maybe I read wrong, but I thought entry point CSS files are not affected. Entry point being what I show in the photo…

 ![12](https://us1.discourse-cdn.com/inductiveautomation/original/3X/2/0/20776fd764219249729c11806217f9e631ae2c10.jpeg)

I’m only modifying the entry point CSS, not the folders. I edited each of the entry point CSS to import my theme, so any selected theme should work.

This is from the README, “Note, changes to `light.css` and `dark.css` entry points will not be discarded on startup to provide you with the ability to override certain rules declared and inherited from the corresponding theme directories (see section on overriding or adapting themes).”

Am I reading that correctly?

---

<div class="post-metadata">

**Author:** ![pturmel](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/pturmel/32/3295_2.png) [@pturmel](https://forum.inductiveautomation.com/u/pturmel)\
**Post date:** [April 19, 2022, 8:19pm UTC](https://forum.inductiveautomation.com/t/custom-theme-for-global-variables/58608/4 "2022-04-19T20:19:04Z")

</div>

Oooo! I missed that. You are probably fine. Carry on!

---

<div class="post-metadata">

**Author:** ![jlandwerlen](https://avatars.discourse-cdn.com/v4/letter/j/bc8723/32.png) [@jlandwerlen](https://forum.inductiveautomation.com/u/jlandwerlen)\
**Post date:** [April 19, 2022, 8:23pm UTC](https://forum.inductiveautomation.com/t/custom-theme-for-global-variables/58608/5 "2022-04-19T20:23:40Z")

</div>

Geez, I completely missed this in the README (didn't read far enough). But this works for me.

## Overriding or Adapting Themes

Overriding or adapting themes is easy by leveraging the "C" in CSS (Cascading Style Sheet). Simply add your own CSS import pointing to your own custom style sheet containing the rulesets that you want to override or adapt AFTER any existing imports. For example, to override something declared in IA's owned light theme, add your own import in the `light.css` entry file like so:

**light.css**

```python
@import "./light/index.css" 
@import "./custom/overrides.css"

```

We do not attempt to rewrite this file on startup unless it does not exist.
