Community forum for knowledge and support

Updated 11 months ago

Experience with the new Figma to Webflow plugin and Webflow's Figma App

At a glance

The community members are discussing their experiences with the new Figma to Webflow plugin and Webflow's Figma App. They are interested in how this integration influences their workflow with Relume, a tool that helps designers build websites quickly. One community member notes that the Figma to Webflow plugin does not output client-first structured components, which can lead to broken components when used with Relume. They suggest that the plugin solves a broader problem of the Webflow learning curve. Another community member asks if the issue is only with the naming convention, which could be solved by naming layers client-first, or if it is also a structural problem.

Useful resources

Would love to hear people's experience with the new Figma to Webflow plugin and Webflow's Figma App.
https://www.youtube.com/watch?v=O9zGylVljbI

Anyone already syncing up their Figma and Webflow? And how do you feel this influences working with Relume?
Are we now creating the components from Figma and skipping the Relume plugin entirely?
What about the Class Syncs? So many questions!

M
P
2 comments

yeah unfortunately, at a fundamental level the Figma to Webflow plugin does not spit out client-first structured components. So in general the result with Relume is broken components, and there's no API or any way for us to prevent that.

This plugin solves a much more global problem for Webflow (and Web design) in general - the learning curve of Webflow. We are also at that same intersection and the core reason why Relume exists in the first place - to empower designers to build websites quickly.
https://relumecommunity.slack.com/archives/C030PMFM4GM/p1708707418550089

That is unfortunate . Is the only the naming convention (which we could solve by naming layers client-first), or also on a structure level?

Add a reply
Sign up and join the conversation on Slack