# Modernizing the Foundation theme

**URL:** https://meta.discourse.org/t/modernizing-the-foundation-theme/395331
**Category:** Announcements
**Created:** [February 6, 2026, 5:52pm UTC](https://meta.discourse.org/t/modernizing-the-foundation-theme/395331 "2026-02-06T17:52:14Z")
**Posts on this page:** 1
**Showing post:** 65

<div class="post-metadata">

### Author: ![jordan.vidrine](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/jordan.vidrine/32/515563_2.png) [@jordan.vidrine](https://meta.discourse.org/u/jordan.vidrine)
#### Post date: [April 10, 2026, 11:56pm UTC](https://meta.discourse.org/t/modernizing-the-foundation-theme/395331/65 "2026-04-10T23:56:56Z")

</div>

Thanks for the pings everyone. This project is still in the works, amidst a ton of other things we are trying to keep in check. My plan is to merge some of the smaller items into core while keeping things like buttons, header, and anti aliased font behind the feature flag for now.

I have made room for this next week and will begin sharing some more updates then.

> [@Lilly](#):
>
> having 2 foundations with different classes is a pain for theme and component dev.

What sort of issues have you run into with your theme and component work with this feature turned on or off?

> [@Canapin](#):
>
> if the release will need `.uc-modernize-foundation-theme` as a parent selector or if it’s just temporary.

This is just temporary for now as it is scoped to the upcoming changes feature being enabled.

---

_[View the full topic](https://meta.discourse.org/t/modernizing-the-foundation-theme/395331)._