Cesar

Matt J. thanks for the video, helpful to see what you're talking about. basically what you're showing in there is what previously was automatically happening (Relume would import components that were already linked to the wireframes). so, after the update, it seems like a major step backwards to me. I have additional feedback so feel free to send me a link to schedule something to cesar@studiohouse.nyc. thanks and looking forward to it!

I imagine everything works fine/better going from Relume → Webflow

yep, my main usecase (currently) is going from Relume → Figma for lengthy visual design activity

we're having the same issue post update, André M. — I'm also against the change (if intentional)

Chester L. this might be related to something I brought up earlier this week? [thread here]

Matt J. haha, you've been super helpful! 😁🧡 admittedly, I'm using Relume for my first client project and even though I tried doing upfront education, I'm sure there's improvements to my workflow I can make (fwiw, I lean more towards a designer/Figma power user than a front-end dev/Webflow expert) I guess I just don't completely understand the change since while it wasn't the mainline usecase, it was working for my workflow (setting up IA and wireframes in Relume then more detailed visual design, layout updates, and client reviews in Figma, eventually moving to Webflow) I'd actually be more than happy to jump on a quick call, just so I'm understanding your guidance above 👆🏼 and to lend insight into my (potentially wrong 😝) process — lmk the easiest way to set that up!

cc Dan

I see the logic here to map the Relume components to Figma components, but apart from being a significant change (for a detrimental experience to my personal workflow), in the scheme of the broader system of templates/components in the Relume Library and importing them into Figma, automatically detaching the components doesn't really make sense to me as it doesn't leverage the inherent design system features of Figma it seems like others are experiencing the same troubles with the change — if this was made for a legal or technical reason, that would be understandable. otherwise, it feels like a step backwards to how I was able to move from Relume to Figma to Webflow I spent a half day recreating a (Figma) componentized page today, where before that would have taken me seconds. I would urge you and the team to consider changing this back. thanks!

Matt J. I just tried what you suggested by importing via the plugin into a duplicate of the latest Figma Kit (v.2.6). the plugin seems to actually import everything from Relume now (yay!), but the workflow still created a net-new "Relume Components" page in the Kit file...and only about 1% of the components are actual Figma components (boo!)

I've previously just been able to import via the Figma plugin, which creates a separate "Relume Components" page in my file