Data-Synced Design at Scale
Data-Synced Design at Scale
A Figma plugin that connects structured data straight into design files, so one update can generate or amend thousands of assets automatically.
A Figma plugin that connects structured data straight into design files, so one update can generate or amend thousands of assets automatically.
The problem
The problem
I kept seeing the same bottleneck. Marketing teams, e-commerce brands, agencies, all manually updating text, prices, regions, and campaign variations across dozens or hundreds of Figma files. It's slow, repetitive, and every manual copy and paste is a chance for something to go wrong.
I kept seeing the same bottleneck. Marketing teams, e-commerce brands, agencies, all manually updating text, prices, regions, and campaign variations across dozens or hundreds of Figma files. It's slow, repetitive, and every manual copy and paste is a chance for something to go wrong.
What I built
What I built
The plugin connects your structured data directly to Figma components. Update the data once, and it automatically generates or amends every linked asset, instantly.
From one master component, you can produce multiple formats, multiple sizes, multiple language variations, or a full campaign rollout, all synced from a single source.
The plugin connects your structured data directly to Figma components. Update the data once, and it automatically generates or amends every linked asset, instantly.
From one master component, you can produce multiple formats, multiple sizes, multiple language variations, or a full campaign rollout, all synced from a single source.
How it Works
01
Connect Data
Connect Data
02
Populate Data
Populate Data
03
Sync & Generate
Sync & Generate
01
Connect Data
02
Populate Data
03
Sync & Generate
Reflection
Reflection
The hardest part was handling nested variants without breaking the underlying component structure. Figma's component system isn't built to be driven by external data, so keeping every linked instance in sync without introducing broken overrides took some trial and error. Next, I'd like to extend it beyond layout, so a single dataset can drive content decisions too, not just which variant to show, but what that variant should say.
The hardest part was handling nested variants without breaking the underlying component structure. Figma's component system isn't built to be driven by external data, so keeping every linked instance in sync without introducing broken overrides took some trial and error. Next, I'd like to extend it beyond layout, so a single dataset can drive content decisions too, not just which variant to show, but what that variant should say.