Content Source edition 1.1.0
Localization Workbench
Review translations and let visitors choose their language.
Keep application strings, translation drafts and reviewed locale exports together. Publish an approved selection to the included browser runtime and let visitors switch languages in your app.
Example scenario
Review a translation, then make it selectable
Prepare a flat file of interface strings, review a translation and publish the approved selection. Connect the included browser runtime to your app so visitors can switch languages with a source-language fallback.
From setup to the result
- Import source strings and choose target locales and terminology.
- Draft manually or through your OpenAI account, then review and approve.
- Export the approved bundles and select them for a runtime release.
- Connect app keys to the browser runtime and let visitors switch languages.
What the package handles
What you can build with it
- Versioned flat JSON strings, terminology checks and reviewed translation exports.
- Explicitly published browser releases with an approved source-language fallback.
- A framework-neutral runtime, safe text rendering and a language selector.
Supported behavior
- Flat JSON maps of 1–500 application strings
- Simple {variable} placeholders, including repeated occurrences
- Manual or OpenAI-assisted translation drafts, terminology checks and human approval
- Approved JSON exports and explicitly published language releases
- Framework-neutral browser runtime, safe text rendering and language selector
Before you choose
Will it fit your project?
Who it is for
- Products preparing plain-text interfaces for more languages.
- Teams coordinating translation review and runtime language selection.
Runtime and connections
Current packages run on Node.js 22.13+ and PostgreSQL 17. You provide hosting and connect the package to your existing app. The included guide describes the supported integration; this is not a hosted service.
Depending on the features you enable, setup can require your own OpenAI accounts and credentials. Their usage, plans and transaction charges are separate from the source purchase. Check the supported behavior below before choosing a connection.
A useful handoff to your coding agent
How setup works
The source package includes local setup instructions, an integration guide, examples, help articles and verification resources. Your agent can use those files without signing in to a hosted reference page.
- Check the requirements. Your agent inspects the application, runtime, database and supported connections before making changes.
- Configure your installation. Answer the product-specific questions below, connect your own accounts where needed and retain the configuration privately.
- Connect and verify. Use the included checks and a representative workflow, then verify any chosen external service separately before relying on it.
Questions to prepare
- Which source and target languages use plain-text strings with simple placeholders?
- Which terms need prescribed translations, and who reviews language quality?
- Which approved translations and source-language fallback should browsers receive?
- Where should the app display its language selector and translated strings?
What your agent checks
- Preserve every key and repeated simple placeholder.
- Reject approval of incomplete or stale translations.
- Load an explicitly published release and switch languages.
- Change source or an included bundle and block new runtime reads until republication.
Scope of this edition
Important limits
Flat JSON maps of 1–500 plain strings with simple {variable} placeholders. ICU/plurals, nested JSON, HTML/XML and rich text are outside this release. Reviewers judge language quality; publishing strings does not edit or deploy the host app.
- ICU/plurals, HTML/XML and nested JSON are rejected or unsupported
- Glossary checks are exact case-sensitive strings, not linguistic quality judgments
- Exports do not edit customer repositories or publish translations automatically
- Runtime publication is explicit; source or included bundle changes block subsequent reads until republished
- Previously delivered browser snapshots remain on an open page until refreshed
Before you decide
Will this work with my existing app?
The package runs on Node.js 22.13+ and PostgreSQL 17. Your coding agent connects it to your application using the included integration guide and supported interfaces. Check the requirements, supported behavior and limits on this page; compatibility with every framework or hosting provider is not promised.
What will my agent need from me?
Your goals, the relevant app details and permission to configure your own accounts. The setup questions on this page help prepare that handoff. Keep credentials in your own private environment; do not paste secrets into a public support request.
What happens if setup fails?
The package includes verification and troubleshooting resources so your agent can inspect the failure and resume the documented setup. Initial setup and reproducible-defect support lasts 30 days from purchase. The refund policy covers material defects we cannot fix, alongside applicable statutory rights.
Is this a subscription?
Helpful Mods sells the source package once. There is no monthly maintenance subscription or automatic renewal. Hosting and connected services have their own costs. Optional major upgrades require a separate purchase.
Can I buy this now?
Purchases are not open yet. You can inspect the product information and use the library planner while checkout is being prepared. A plan is not an order and does not grant source access.