Hello, there are no component instances when we import our wireframes to Figma from the Relume plugin, as you can see in our screenshot. A few weeks ago, that was the case. Is this normal?
If I import 150 pages on my Figma, I should therefore manually put the instance of my navbar and footer component for example on the 150 pages whereas before this was not the case, I do not understand this strategy
Have this same issue Mathieu N.! But I'm not importing 150 pages haha 馃槃
馃憢 also here for this
same issue here
Quentin G. Mathieu N. Brian W. Ben C. yeah this change was done intentionally to support the new editing features within site builder and being able to import those edits into your figma file. I think there are some things we can do to improve here and I really would love to hear or understand your workflow around keeping these components attached to the core components. DMs are open, I'm ready to learn from you guys - whatever you are willing to share, and however you are willing to share and I'll be sure to voice any concerns to the team.
Thanks for the response Matt J.. Am I missing some functionality here? If the import isn't linked to the components that populate in the "Relume Components" page, what is the purpose? Previously I have styled the parent components in order to make universal / large scale updates across the file. If I'm not mistaken that, is no longer a simple pathway. If my Figma ignorance is showing, please enlighten me. (responding publicly for visibility of others having this issue, but can DM if that is better) Thanks in advance
yeah the issues stems from a technical one - when you make edits in Site Builder - say you remove a secondary button or a tagline - we have to detach the component from the core components and apply those changes and then render your wireframes onto the canvas. Its my understanding that some users have been styling components before importing, thus propagating their styled components across the site. We're exploring a middle ground to allow this type of workflow to happen since we technically can't rollback the release with detaching components. If anyone in this thread would be interested in having a call where you walk us through your workflow in detail and answer some questions - we would be forever in your debt in helping us shape a better product. If anyone can provide a read-only to their figma file where they've designed in this manner, that could also be helpful. The proposed workaround is that you'd do all of your design work after you've imported wireframes. For sections that are either identical in layout and/or in design - you would make that a local component, and use Figma's bulk edit features to apply that component across all of your wireframes.
in short - propagating styled core components like you and several others have done for larger scale projects was not a use case that I was aware of, and I can't speak for the rest of the team but its understandable how we've disrupted this workflow and we'd love to come to a solution together
Thank you again for the response, Matt. More than happy to jump on a call to speak to this. I'm surprised to hear that this wasn't the initial intent with the Figma handshake
yeah like all things, we had to start somewhere. Having your site builder wireframes imported into figma with a click of a button is a big step forward - taking into account all the possible changes across all of the components is another step - now how can we turbo boost all of these things together? Next step!
Hi Matt J. , newbie here...is it possible to swap out the components in Figma now that they are no longer attached? I tried to do most of my edits in relume but now as I'm designing out the wireframe I'm realising I'd like to change some of the layouts, and I can't figure out how without having to start again or individually pasting in the component and manually swapping out the content. Is there a simple way to do this? Also, where I had global instances in relume - they are no longer connected in figma...is there a way to fix this?
