Translations
The language a visitor sees is set through a small number of channels, each owning a different surface: the widget's own UI, the standalone recording page, and the documents generated on the server.
The lang prop and attribute
The React component takes a lang prop, and the Custom Element observes the matching lang attribute — set it directly, or update it at runtime, and the widget's interface follows.
<livstick-widget-v2 uid="code" domain="example.com" lang="fr"></livstick-widget-v2>fullpage.html and the language query parameter
The standalone fullpage.html page reads its configuration from an embedded template, but it also accepts URL query parameters — and language is the only one of them that can change anything. No query parameter can override the API key, the domain, or a resume capability read from that same configuration; language is deliberately the sole exception.
language at container creation
On the API side, the language passed when a container is created determines the language of the recording journey shown to the recipient, and of the documents Livstick generates for that container — the card PDF, for instance, carries text translated into that language, not just a language-neutral layout.
What is not documented here
The exact catalogue of translation keys used across the widget, and the mechanism for supplying custom translations for a language the widget does not already cover, are not established in the repository at the time of writing. Rather than guess at a list or a file format, this page stops at what is verified above — treat the presence of a translation catalogue and a customization mechanism as likely, but unconfirmed.