I18n by page
I18n by page keeps localization close to the page it explains.
Instead of treating translation as a detached global file, Collab.codes favors a model where each page can carry the language resources that support its product intent.
Why it matters
Business screens are not generic text containers.
A label, button, status, or validation message often depends on the process, role, and domain vocabulary behind that page. Keeping i18n near the page makes translation easier to review and easier to evolve with the feature.
What it enables
I18n by page can support:
- language-specific publication;
- page-level review;
- product vocabulary per business area;
- safer AI-assisted changes;
- clearer ownership of translated content.
Publishing model
Different language variants can be published together or separately depending on the build and publication process.
That makes localization part of product delivery, not a late manual step.
Current positioning
Web and desktop are the current focus. Other categories, including mobile and native targets, should be documented as planned or evolving until validated in public examples.