One of the biggest challenges of working on copy on a team is that copy is often scattered across a patchwork of tools that are disconnected from one another. One of the most common tools? Spreadsheets.
We often see teams use spreadsheets to track content that’s not mocked up, like error cases or variations. This content can quickly add up and cause overhead, as content in spreadsheets is usually tedious to keep updated, easily gets divorced from the visuals, and adds hours of manual copy and paste work for developers to implement.
At Ditto, our goal is to help teams build a unified copy process that connects copy across all the places where it lives and ensures everyone on a team works from the same source of truth. That’s why we’re excited to announce that, starting today, teams can import content from spreadsheets into Ditto! 🎉 Content and metadata imported from CSV files will get added to Ditto so that it can be worked on and synced alongside all other content.
Content spreadsheets often contain a lot of context outside of just the content itself, like review status or notes on implementation. When building spreadsheet import, we knew we’d need to support the ability to bring this additional information into Ditto upfront.
In the end, we tackled this with a special “mapping” step in the spreadsheet import flow in Ditto. On this screen, teams will be able to let us know exactly how each component should be configured based on the information in their spreadsheet. In addition to specifying which columns we should use for the name and text values of a component, teams can pull in information for fields like status, tags, notes, and developer IDs.
For example, if a column contains context developers need to know for implementation, those can get pulled into the notes field for each component. If there’s a column that’s critical for categorizing content, that information can get added as to the name of the component, or as a tag in Ditto.
Once content is imported from a spreadsheet into Ditto, it’ll now be in a tool that’s built for text, meaning teams will be able to work on, reuse, filter, and hand off that text much more easily. For example, teams will be able to:
To try it out, just head to your workspace’s component library in Ditto’s web app, click “New Component,” and then “Import from string file.” To learn more, check out our full help guide on spreadsheet import.