Feature/custom color field

[j-ferber]

Added a custom color field to the CMS so they can edit the color of the components.

Can current be tested on: http://localhost:3000/admin/index.html#/~/example-actions

[vercel[bot]]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
inreach-website	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Apr 20, 2024 4:40pm

[ShawnAviles]

Just to provide what I found regarding the issue of having each button have its corresponding background color:

• TinaCMS uses a separate styling for the component rendered in the Admin Panel
  • This causes the extended tailwind colors from not being rendered for the background color
  • We would need some way to update or alter the Tina Stylesheet. maybe there is something in the docs but looking up Tailwind, TinaCMS, and Custom Component is very niche in general so it's been hard to find anything about it
• I also looked into using the MantineTheme colors instead. When using that it gives an error about the theme being used outside of the Provider. I think this is due to how TinaCMS handles the styling differently for the Admin panel too

I think keeping the colors how they are no is a design decision from the Tina team to prevent crazy styling choices from being used as well as handle some past CSS issues they had

I think another approach we can try would be to have the hex values within an object outside of that component so we can map over them and set the background style to that hex using a basic style prop. But that means our color system would exist in 3 places (Tailwind Config, Mantine, and here) which wouldn't be the best.

Anyways, we can come back to this after the MVP