WIP / POC — [Feature] theming / customization

[MildTomato]

to do:

• allow for override of styles if ThemeProvider is being used
• add a config wrapper for target app to use for purging either default theme file, or custom theme file

I'm trying to look at removing css modules completely

we could also look at leaving in some css class names purely for the same of making it easier for a developer to target elements if they need to override something with css rather than tailwind classes.

[willopez]

@MildTomato This theming feature would be very useful, is this still planed for sometime in the future? in the mean time, I guess forking and changing the theme would be the way to customize?

[MildTomato]

@willopez yep it is. I did a first pass on it in alpha brach but I wasn't happy with it.
I want to change it so the tailwind classes are more explicit. like bg-panel-primary, rather than bg-gray-300.
Then it would be much easier to customize.

It also creates way too many css properties currently as well, so I also want to fix that up really.

[willopez]

OK, got it. And I agree that making class names explicit will make it easier to customize. I am open to help with this effort, how can I help?

[MildTomato]

@willopez honestly, and this will sound boring.. possibly branching off alpha branch and basically going through all the classNames in the theme file and renaming them all to be explicit.

I'm not that sure what the structure could be yet, although I've started planning it a little bit in Figma and I have the following names for things. But it's a bit of a work in progress.

[MildTomato]

Saying that, the name/structure in that figma tokens json isn't very useful.
As we'll probably want to keep to using tailwind standard of naming things - so flipping it.

So form.input.error.bg would be bg-form-input-error

I'm still not entirely sure this is a good idea, as we'll end up with a lot of classes.
Something else could be using arbitary class names and read from css properties.

Like, bg-[var(--form-input-error-bg)]

[MildTomato]

Supabase UI is being deprecated.

As part of that, we are closing Pull Requests in this repo for now.

---

We are moving the components to the main mono repo at https://github.com/supabase/supabase.

The auth component has been moved to it's own repo and package. https://github.com/supabase-community/auth-ui. You can also read the docs for auth ui here.