# Plugin CSS takes priority over theme CSS?

**URL:** <https://meta.discourse.org/t/plugin-css-takes-priority-over-theme-css/144828>\
**Category:** Product Support\
**Created:** [March 19, 2020, 2:15pm UTC](https://meta.discourse.org/t/plugin-css-takes-priority-over-theme-css/144828 "2020-03-19T14:15:07Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![david](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/david/32/157490_2.png) [@david](https://meta.discourse.org/u/david)\
**Post date:** [March 19, 2020, 3:15pm UTC](https://meta.discourse.org/t/plugin-css-takes-priority-over-theme-css/144828/2 "2020-03-19T15:15:36Z")

</div>

Hmm yes, you’re right. We load core, then themes, then plugins

> <https://github.com/discourse/discourse/blob/main/app/views/common/_discourse_stylesheet.html.erb#L11-L17>

I think core → plugins → themes would be a better order, and would match the pre-[plugin-debundling](https://github.com/discourse/discourse/commit/5bd6b70d985e2736f56d2bec6cce56bee0227b1f#diff-b7cd0bbfe681e2c8d48db57817e9d6b5) behaviour. What do you think @awesomerobot @Johani @jordan.vidrine?

@WorldIsMine a workaround is to increase the [specificity](https://www.w3schools.com/css/css_specificity.asp) of theme’s CSS.

---

_[View the full topic](https://meta.discourse.org/t/plugin-css-takes-priority-over-theme-css/144828)._
