Private beta: first Linguana workflow
This historical beta note describes the initial integrations. For current availability, see Public launch and framework setup.
The first Linguana workflow helps teams connect an application, prepare languages, review the result, and publish when ready.
Added
- Connect an existing Vite application to Linguana.
- Find product text during the application build.
- Translate dynamic values and rich links with
t()and<T>. - Review language before publishing it.
- Keep the original language available if a translation is missing.
- Vite + React and TanStack Start setup paths.
Changed
- Documentation is organized around getting started, using Linguana, automation, and reference.
- CI guidance separates pull-request checks from development translation and production release.
Fixed
- The setup flow focuses on connecting your own application instead of the repository demo.
- Setup examples distinguish build tokens from browser-safe publishable keys.
Known limitations
- The SDK packages are public on npm under the
@linguanahq/*scope. The earlier@linguana/*package names were never published and should not be used. - Vite + React and TanStack Start are the current integrations.
- Production publication remains an explicit dashboard action.
Migration
If you used a source workspace or prerelease instructions with @linguana/* imports, replace the public SDK scope with @linguanahq/* and install the packages from npm. If you link to the docs from outside the site, use the new getting-started and use-linguana paths.
Connect an application, translate selected languages, and publish reviewed versions.
Last updated October 3, 2026
Did this page get you to a working result?