A single source for all your UX content

You can add content to your library in several ways: Import components from external files (coming soon), design tools, or directly create them in Frontitude's web app.

Frontitude’s Copy Library is included in all Free, Team, and Organization plans. However, exporting content from Frontitude's web app and handing it off to developers is available only on paid plans.

Yes, of course. Frontitude's Copy Library stores all the content guidelines your design team needs to maintain consistent product language. Currently it can be used as an internal style guide, but in the future we plan to allow you to share it publicly.

Once you attach text elements to an existing component or create a new one in Frontitude’s web app, you can attach its content guidelines to it. The copy guidelines will be updated and displayed on all attached instances for the entire team to view when they reuse it.

By attaching copy to existing components, you can translate once and reuse it everywhere. This will save you a lot of translation time and costs, and also help you ensure high-quality, consistent translations.

Copy components can be reused directly from your copy library into the design using Frontitude's web app or the design tool plugin.

To help you build an organized copy repository, we have applied a naming convention that is built from a 4-level hierarchy. You can read our official guide to learn more about it.

Export copy in JSON and CSV formats for handoff to developers, translators, or feeding into other tools. Developers will soon be able to pull the latest copy directly from their environment using Frontitude's dev tools.

Yes, definitely. Frontitude acts as a single source of truth that helps teams manage the product copy through the entire product development life cycle. Frontitude stores all the relevant information such as content guidelines, discussions, and different iterations so that you can have everything documented.

By keeping all of your product copy in one place and having it connected with the design, localization, and development processes, supporting new languages becomes more like pulling the trigger rather than pushing mountains.