Community forum for knowledge and support

Updated 6 months ago

Optimizing Figma Workflow: Leveraging Reusable Components Across Multiple Design Files

At a glance

The community member wants to create individual design files for different pages (e.g. Blog, Pricing) instead of having them all in one file, but still apply the same edited components to each new file. They ask if they can publish the Relume components to the Figma library and apply it to the new design files.

The other community members discuss this use case, noting that while publishing the Relume Figma Kit to a Figma Library is a good approach, there may be concerns about how the Relume Figma Plugin will handle placing components if they are only available in the library and not local to each file. They also discuss how this workflow may scale and the challenges of maintaining multiple instances of the Relume Figma Kit.

There is no explicitly marked answer, but the community members provide suggestions and discuss the potential issues with the proposed workflow.

hi everyone
I want to make every design a single file instead of stacking them in one file (for example Blog and Pricing Page are different file)
but I also want to apply the edited components to every new file
what is the best workflow I can achieve in Figma?
Can I publish the relume components to the Figma's library and apply it to the new design file?

M
H
5 comments

very interesting use case, I'd be curious how this scales.

You are on the right track though - you would have a single Relume Figma Kit turned into a Figma Library and publish it. Once published, you can start new files, and include this library.

My only concern is if the Relume Figma Plugin will know what to do to place components if all you have is a library - I think it needs components to be local and there's no real easy way to maintain multiple instances of a Relume Figma Kit at the moment.

Hi thanks for the reply
yes, your concern is what I learn currently
the newly imported Relume will create a set of new local component, even if I already include the library in the file

I worked for 3 companies using Figma and in our workflows, each design file is bonded with a task's ticket (Jira or Notion).

It is very likely we design Blog, Pricing, or other website pages in different tasks. But the components on the website should be consistent. This is my use case though.

And I assume for the product design, at least each feature should have its own design file instead of design the whole product in a single design file.

Understood - makes sense. I dont think we've considered this use case with the Figma Plugin so I will have to communicate this to the team - likely a pretty big undertaking and not something we could whip up quickly.

That's understandable
Judging from the current workflow, I assume your ICP is more like the agency instead of internal design team (website or product), am I right?

Yeah no doubt. We’ll expand soon enough!

Add a reply
Sign up and join the conversation on Slack