[jolenam]

While there’s a chance we expand to other types of assets in the future, we want to tackle text first. We think text is often more cross-functional than images or other assets — it’s worked on by people from legal, marketing, customer success, in addition to engineers and designers — but there isn’t a unified suite of tools focused on text right now. There are lots of areas around text we still want to tackle and integrate into an end-to-end solution: localization and internationalization, A/B testing, intelligent suggestions and linting, etc. A lot of these are text-specific use cases, which allows us to do things like help teams build out a component library dedicated to text, and then surface component suggestions based on text in their mockups.

[CodeWriter23]

There is a unified set of tools for working on text, either Office 365 or Gsuite, both with their +/- but definitely get the job done. They have revision control, visualization, etc. the problem is finding the dang file 6 months from now...

From my perspective, the problem to solve here is to have an authoritative repo of assets accessible via API, CLI, cloud dashboard, ERP add-on. IMO that's the value play. It answers the "do I have the latest X" in everything from an SOP document to a software build, and enables the responsible parties to push updates across the organization seamlessly. Also, will probably help with the "which dang file is that in" problem products like Teams try to answer but still fail miserably at.

[jolenam]

We definitely agree that there’s huge potential in becoming the “authoritative repo,” or as we like to call it — the single source of truth — for all assets, accessible by tools used by every role. Hoping to focus on text first, but not ruling this out for the future.

What we’ve also seen from customers is that it can be hard to work on product text in document tooling like Office 365 or GSuite because those external docs feels detached from the context of the designs and the app, and require separate maintenance and manual copying + pasting to move it into the tools where product development is happening (ex: mockups, the codebase). We’re hoping to address this at Ditto with lots more future integrations (like you mentioned!) with other design tools, project management tools, etc.