Introduction
Stringtale lets people edit static UI text directly in a React application, without having to touch the code. Think labels, notifications, helper text, empty states and validation messages. Developers still decide what goes into the repository and what gets deployed.
It is not a CMS. The copy that ships still lives in your repository. Stringtale sits around that code and handles the editing workflow.
What is Stringtale?
Stringtale is a collection of libraries and tools that adds in-context editing for static UI text to a React application. Developers integrate Stringtale into a supported project, wrap the text that should be editable in <Value> tags and enable Stringtale in a test or preview environment. You can also use the CLI Codemod to wrap eligible static text across the codebase.
Editors can then change Stringtale-enabled text directly on the page. When they save their changes, Stringtale stores them as pending edits. Developers can bring those edits back into the source code with the CLI, or use the GitHub Action to create a pull request. From there, the changes follow the normal Git review and release workflow.
Stringtale currently supports React on the front end with Next.js or Express.js on the server side.
Why use Stringtale?
A lot of small UI copy lives in code, even though the person who wants to change it may never work in that codebase. Without Stringtale, a tiny wording change often ends up as a ticket, Slack message or interruption for a developer.
With Stringtale, editors can make the change where they see it. Developers no longer have to find and retype every piece of copy, but the change still comes back through Git and can be reviewed before it ships.
That removes a lot of small copy work from the development queue without adding a CMS just for interface text.
Who is Stringtale for?
Stringtale has two main roles in the editing workflow: Developers and Editors.
Developers have access to the codebase. They integrate Stringtale, decide which static text becomes editable and remain responsible for the Git, review and release workflow.
Editors are the people who change Stringtale-enabled text through the in-page editing interface. They do not need access to the codebase or Git. An Editor can be a product owner, copywriter, designer, marketer, client or another team member responsible for interface copy.
For agencies, Workspaces and Projects can be used to separate client work and scope Editor access to the relevant projects.
Whichever setup you use, the division of responsibility stays the same: Editors can make static text changes themselves, while Developers retain control over what is reviewed, merged and deployed.