In other words a way to branch to/from a Community file
I publish a design system (DS) to the Community and have frequent updates to fix issues and add/update components.
Community members duplicate this DS to their Organizational account to use in their own projects. They have reported to me that once they import the Figma file into their org and use it as a library they have no way of getting my latest updates easily and without breaking changes into their production design files that refer to the original “duplicated” file.
So it would be great if there was a way to publish “get latest” or “subscribe to changes” in a community file. (Instead of having to restart design file from scratch in the latest version of the Design System).
Librairies features are not an option as they are specific to an ORG and cannot be accessed through the community. And Swapping in this use case does not work well at all.
This would be great for everyone as it would allow Figma to always ship with latest official components from the big design systems from Apple, Google, Microsoft and any other design system available in the community.
(If it mean anything Sketch has had this feature for years now)
This would function exactly like branches currently used by design teams in Figma:
Publisher owns the Main Branch.
When changes occur in the Main branch all branches are notified and can opt in to the changes they want. Or just not update at all.
So no unwanted changes would pollute either Main nor your own personalized branch.
It could even be optimized into a second feature where branches could be submitted to the Main branch to crowd source work (like you already do inside your Org).
Sketch goes a different route where you just “get the latest” file from Apple to start your file from which is essentially the same as getting a file from the Figma Community. This works for small short term projects but not so well for long term stuff.
Now that Figma has announced their Marketplace for Community files it becomes even more relevant as it may be more profitable to Subscribe to an asset and it’s updates then it would to have multiple concurrent versions on the community.