Best Practices for Keeping Figma Files in Sync

I’m seeking insights on how larger design teams manage Figma files in collaboration with development to keep everything in sync with production:

  1. Do you create page templates as part of your design system?

  2. Do you maintain a separate file (such as a sticker sheet) for page-level components?

  3. Or do you skip page templates and modify components directly in your working files, pushing updates to production once changes are finalised?

Please, help a friend out and share your approach.

Try this approach: Atomic Design | Brad Frost

1 Like

*** Not production, the master component file.

Sorry if it’s not what you’re looking for. We used this approach on our design system so

Yes, we create page templates as components—part of the Atomic Design.

Can you describe what are your page-level components? Is the separate file a sticker sheet?

We have a draft file where we modify components directly (for new features and stuffs, because we might need to break the components) but when we push to production we update the prod Design system so the prod file will update automatically. The devs will only look on that prod file for reference and not our drafts were we work to avoid confusion. It’s just a separation of Drafts and Live files.

1 Like

Thank you. Where do you keep the page components? Article is great thank you.

They are on the 3rd level of our DS library.

  1. Core (Styles/Tokens)
  2. Components (Components / Sets)
  3. Design Patterns (Templates / Blocks)
1 Like