Skip to content

README: the three translation methods and when to use them - #62

Merged
lann merged 1 commit into
mainfrom
readme-translation-methods
Aug 10, 2026
Merged

README: the three translation methods and when to use them#62
lann merged 1 commit into
mainfrom
readme-translation-methods

Conversation

@lann

@lann lann commented Aug 10, 2026

Copy link
Copy Markdown
Collaborator

Docs-only follow-up to #58#61: a decision table (build-time envelope / runtime-packaged / runtime-explicit) with what each ships to production and when to pick it, linking the examples, the tools/translate deploy recipe, and the #16 design note.

Operator request: the delivery work (#58-#61) created three distinct
ways to obtain a translation and the README never says which to pick.
A decision table after Quick start: build-time (envelope, no translator
shipped — the browser default), runtime-packaged (defaultTranslator, for
dynamic components, paired with the artifact cache), runtime-explicit
(Translator.create/fromExports, for custom sourcing/sharing). Points at
the examples, the tools/translate deploy recipe, and the #16 design note
for depth.
@lann
lann enabled auto-merge August 10, 2026 22:42
@lann
lann merged commit c966262 into main Aug 10, 2026
4 checks passed
@lannbot
lannbot deleted the readme-translation-methods branch August 23, 2026 16:51
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant