TextDB
Translations Editors Can Actually Edit
Moves frontend system strings — form labels, buttons, confirmation messages — out of XLIFF files in the repository and into the database, where editors change the wording themselves. No deployment for a typo.
Editors, Not Developers
Wording changes happen in the backend module and take effect immediately, instead of going through a pull request and a release.
Self-Filling Catalogue
A key rendered for the first time creates its own record. The catalogue documents exactly the strings the site really uses, with no manual inventory.
XLIFF Import And Export
Upload an XLIFF file to bulk-load translations, or export the current filtered set as a ZIP to hand to a translation agency.
Environment, Component, Type
Every string is filed under an environment, a component, and a type, so a large catalogue stays navigable and a component can be exported on its own.
demo. This demo ships four seeded labels, each with a German translation — switch the module to the translated view to compare them side by side. The records are stored in the TextDB Translations folder in the page tree.
Want this in your TYPO3 project?
This instance runs the extension exactly as it ships. We are happy to walk you through it and discuss what it would take in your setup.
Talk to us