Issues with Wireframe Imports in Figma After Editor/2.6 Update
Since the editor/2.6 update, I am finding that wireframes imported into Figma are not connected to their respective Figma library components. Any others experiencing this?
Since the editor/2.6 update, I am finding that wireframes imported into Figma are not connected to their respective Figma library components. Any others experiencing this?
I generated a fairly large sitemap/wireframe in the Site Builder app. Then I cloned the 2.6 Figma starter in my Figma account and imported the whole thing through the Relume Figma plugin. All of the section components were named correctly (eg. “Header / 84 /“), but none of them appeared as instances of the local Figma components from the library, they are just regular layers.
I did another example from scratch, starting a new Relume Site Builder project, with just a single page. Cloned a fresh copy of the 2.6 Figma starter too. That example had the same behavior.
In the latter case, I didn’t make any modifications using the new editor features.
Ah this is a different issue thats actually not an issue but done by design. You can find a thread here https://relumecommunity.slack.com/archives/C02MS2V0FSP/p1725481823135949
So you are saying that this was an intentional change in behavior as part of yesterday’s update?
Let me put this another, more specific, way…
Before the update, imported wireframes were comprised of Figma component instances. The layers were purple, and the desktop/mobile instances on the page were “connected” to the actual components in the local Figma Starter file. Clicking on the component icon in the right-hand panel would take me to the local component instance.
After the update, imported wireframes are comprised of normal Figma layers. There is no connection to the components in the Relume Figma library that comes nested in the Starter file.
I am providing further clarification here because I don’t think the thread you linked to above addresses the issue that I’m discussing. Though I will review it again…
Perhaps I spoke too soon. You clearly state in that thread that bringing in all components in a “detached state” is intended behavior.
I will confess, I am not a fan of this change. Maintaining the relationship to the core component is very helpful for developer handoff, especially if they are using the Relume React Component library (which they often are). I get that it doesn’t really “break” that workflow, but it does make it harder - takes away some quality of life features for devs. Some thing they really like(d) about Relume was the ability to select a component instance in Figma, and:
Click to the core symbol to see the desktop/mobile layouts for that component side by side
Click the component documentation link to go straight to the documentation (example) for reference.
This allows them to quickly see if the component is supported in the React library with a direct link, and if not find a similar component they could use as a starting point.
Designers could also modify the local components if they wanted to make fast modifications that propagate across the site, without having to make their own local component and clumsily replace all of the instances in the wireframes. It’s not awful to have to make local components, but it doesn’t allow them to pick and choose when to do so.
Most of all, our team appreciates Relume for it’s speed. This slows things down a bit. Just offering some constructive feedback!
On the bright side, we were pondering when it does/doesn’t make sense to create new local components, and this kind of answers that question. 😆