Skip to content

docs: restructure i18n docs into top-level Flow section#5349

Open
Artur- wants to merge 8 commits intomainfrom
i18n
Open

docs: restructure i18n docs into top-level Flow section#5349
Artur- wants to merge 8 commits intomainfrom
i18n

Conversation

@Artur-
Copy link
Copy Markdown
Member

@Artur- Artur- commented Mar 12, 2026

Move localization documentation from a single page under Advanced Topics to a new top-level Flow Reference section with practical guidance on translation strings, language selection, component i18n, and number/date formatting. Advanced content (custom I18NProvider, RTL for custom elements) moves to a sub-page. Update all cross-references.

Move localization documentation from a single page under Advanced Topics
to a new top-level Flow Reference section with practical guidance on
translation strings, language selection, component i18n, and number/date
formatting. Advanced content (custom I18NProvider, RTL for custom
elements) moves to a sub-page. Update all cross-references.
@github-actions
Copy link
Copy Markdown

github-actions bot commented Mar 12, 2026

Preview Deployment

This PR has been deployed for preview.

URL: https://docs-preview-pr-5349.fly.dev

Built from 2f955b7

Comment thread articles/flow/i18n/custom-i18n-provider.adoc Outdated
@peholmst peholmst added the target/v25.1 Automatically cherry-pick to the v25.1 branch label Mar 25, 2026
Artur- added 6 commits April 7, 2026 15:20
DirMixin uses Polymer-style property definitions internally and
requires PolylitMixin as a compatibility layer when used with LitElement.
Move the Adding Right-to-Left Support to Custom Elements section out
of custom-i18n-provider.adoc into a dedicated custom-element-rtl.adoc
page, and simplify the I18NProvider configuration section to lead with
the Spring Boot bean approach.
Lead Translation Strings with view-side getTranslation() usage, then
explain default storage and link to Custom I18N Provider for other
sources. Use Spanish instead of Finnish in examples for broader
familiarity.

Rewrite Automatic Locale from Browser to correctly describe how the
initial locale is resolved against I18NProvider.getProvidedLocales(),
including how the default provider auto-discovers locales from
translations_*.properties filenames.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

target/v25.1 Automatically cherry-pick to the v25.1 branch

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants