# Changing Front Text Colors on Status (New, Learning, Review)

**URL:** <https://forums.ankiweb.net/t/changing-front-text-colors-on-status-new-learning-review/51832>\
**Category:** Help\
**Created:** [November 12, 2024, 2:24am UTC](https://forums.ankiweb.net/t/changing-front-text-colors-on-status-new-learning-review/51832 "2024-11-12T02:24:35Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![Danika\_Dakika](https://sea2.discourse-cdn.com/flex002/user_avatar/forums.ankiweb.net/danika_dakika/32/17815_2.png) [@Danika\_Dakika](https://forums.ankiweb.net/u/Danika_Dakika)\
**Post date:** [November 12, 2024, 4:42am UTC](https://forums.ankiweb.net/t/changing-front-text-colors-on-status-new-learning-review/51832/2 "2024-11-12T04:42:59Z")

</div>

> [@Allow CSS styling based on card state](https://forums.ankiweb.net/t/allow-css-styling-based-on-card-state/13196/4):
>
> I’m just going to list what I’ve learned from reading the above: The “Custom scheduling” javascript is a monkey patch, while it runs the states object exists, but states is not accessible from the normal card design. If we want to expose states, it can be injected directly into the HTML. (shown later) I’m assuming states is not exposed on purpose to avoid API surface increase. Custom scheduling: // expose states e = document.createElement("script") e.text='var states='+JSON.stringify(states)…

---

_[View the full topic](https://forums.ankiweb.net/t/changing-front-text-colors-on-status-new-learning-review/51832)._