Hello, I have a question. I'm using Relume to design with Figma, and I want to use the React/HTML components. The question is: I see the new color schemes on Figma, but I see that the Tailwind CSS config file is still using the following:
DEFAULT: "##FFFFFF", // bg-background, text-background, border-background
primary: "##FFFFFF", // bg-background-primary, text-background-primary, border-background-primary
secondary: "##EEEEEE"
tertiary: "##666666"
alternative: "##000000"
success: "##ECFDF3"
error: "##FEF3F2"
Are there ways to get these two things to work together?
Looks like Nour is on vacation - digging through some of our previous chats, it looks like having the figma components and the react components sharing the same variables is something that is actively being worked on but I don't have an ETA on that.
What about these color schemes not being the same is blocking you?
like: it forces me to come up with a tailwind system. to adapt to the new figma changes, without help
I think Relume needs to be more transparent about the fact that there is no standard solution yet, because I paid for the subscription under the impression that I could use the React/HTML components out of the box, as an integrated Relume-Figma-React system.
Please include a warning: "React is still not integrated with the new design system."
can you point me to some documentation? that can help me figure this thing faster please?
can you help point me to the messaging on our website or a popup that came up that indicated those expectations? You are not the first person to mention this and honestly, I'm tempted to go into the marketing site and just hide this messaging because its making people very angry.
the whole thing changed. I had an old project and it was integrated with figma. COOL.
but now they are 2 different systems, and no warning
okay, well we did recently have to make some updates to our color schemes and its not easy to get 1500+ components updated to those changes that were forced on us by other systems - so that is likely the disconnect.
the new design system works great on figma, as long as you don't have to many gradients, with different shades.
Okay well I guess one way I could try to help is show you the expectation of how to work with color schemes in Webflow - applying those same principles with tailwind and CSS.
https://www.loom.com/share/36c4d72d91264453af1beae10bd49a42?sid=4f9690c6-dcdb-477b-81b8-b5d43d7df7db
I tagged the person who would be best to help but as mentioned, they are on vacation. I am very technical and have been writing HTML/CSS for 20 years - but not that familiar with Tailwind or React to understand how to direct you specifically on moving forward. For me, it doesn't seem like it would be that big of a leap to apply the same principles via CSS and I would think having a framework like Tailwind with variables and mixins would/should make it even easier.
I did see that Figma released some access to their APIs to allow for tools like Cursor or Claude to read into a figma file and spit out JSON, so maybe thats also another path forward - I have not tested or played with that yet.
https://www.figma.com/blog/introducing-figmas-dev-mode-mcp-server/
Being a small team, we just dont have the resources to spit out 1500 components quickly whenever sweeping updates happen to our products or the ecosystem around it.
and those docs likely need to be updated as they were speaking the truth at one point but clearly not anymore
Thanks, I understand. The only thing I didn't like is the lack of a warning—that takes about 20 minutes to set up or less. And maybe some ideas on how you guys want to solve the problem, so we, the clients, can be a bit closer to the path before the changes are final.
If no warning is given, many HTML/React clients are going to be disappointed, and a system that has not been solved by the Relume team is being forced to be solved by the clients. Not a good deal
yeah I agree, I'll flag this with the team because I was not aware that there was that big of a disconnect between the systems.
I think i can make it work, but that defeats the idea of paying for react animated components out of the box
