Top 5 reasons GNOME is awesome:

1. Distraction-free: we respect you and include personal digital wellbeing features

2. Accessibility: we work to make computing accessible to all

3. Design: we make a cohesive, modern experience that looks great

4. Free and Open Source: we preserve your freedoms

5. Privacy: your data is yours, and we respect that

If these resonate with you, consider supporting us today! We're aiming for 1,500 #FriendsOfGNOME by the end of the year.

https://donate.gnome.org

Donate to GNOME

Donate to the GNOME Foundation and make a difference to GNOME

@gnome But will libadwaita ever be themeable?
@CarbonCarrot @gnome you can already do it
@tragivictoria @gnome …by either recompiling or overwriting adwaita. Or writing a custom gtk.css, which only gets you so far w/o ugly importance hackery
@CarbonCarrot @gnome you realise you can just add theme to ~/.config/style.css, right? And it's going to work basically very similarly to gtk3. Instead of complaining on fedi you could as well just research the topic
@tragivictoria @gnome I don't think that lets you change everything w/o fighting adwaita for the highest specifity value, does it?
@CarbonCarrot @gnome do you want just theming or overwriting entire stylesheet?
@tragivictoria @gnome theming, but I've tried to override parts of adw w/ gtk.css and didn't manage to do so. How about you link to an example?
@CarbonCarrot @gnome It's open source software, the power to change anything is just one git clone and recompile away :)
@FineFindus @gnome but compiling means patience and making toolchains toolchain. And don't you DARE break ABI compat by accident…

@CarbonCarrot @gnome There is no such thing as free lunch.

I've generally found GNOME apps/libraries incredibly easy to build (e.g. just click on 'Run' in builder). I would also be very surprised if you managed to break ABI by changing the CSS :)

@FineFindus @gnome Welp I would've taken the approach of loading CSS from a user defined path instead of always adwaita but yes