In the next few guides, we’ll walk you through the fundamentals of setting Ditto up for your team. By the end, you’ll have a single source of copy truth for your team that allows you to reuse text and is connected to design and development. Here’s an overview of what we’ll cover:
This order is based on what we’ve seen work for teams, but if you have string files from your codebase, you can also skip straight to part 2 to import those first if you'd like!
In order to build your team’s source of copy truth in Ditto, you’ll need to get some copy into your workspace! You can do this easily by importing text from your Figma files.
Each Figma file will get brought into Ditto as its own project. In the next section of this guide, you’ll learn how to componentize your text so that it can be reused across projects.
For the best import experience, use Ditto’s Figma plugin directly in the Figma file. You can also use Ditto’s web app.
Figma plugin
Web app
You can do this for as many Figma files as you’d like. Remember: each Figma file maps 1:1 to a Ditto project.
Connecting a Figma file to Ditto isn’t just a one-time import — you’ll be able to continuously sync changes back and forth between the Figma file and corresponding Ditto project. This makes it easy to ensure your Figma mockups are always up-to-date with the latest copy.
To pull the latest changes from Ditto into a Figma file:
Head to the next section to learn how to componentize your text →