Getting started
Concepts
Understanding these core concepts helps explain why Messagevisor works the way it does and how to get the most out of it.
Foundations#
Ways of working#
Why these concepts matter#
Messagevisor treats translation behavior as part of the product system, not as a side table of strings. Messages can have:
- metadata
- tests
- examples
- target filters
- locale inheritance, and
- conditional overrides
Keeping those definitions in Git makes them reviewable by engineers, product managers, localization leads, and compliance stakeholders using the same pull request history.
How the model fits together#
At authoring time:
- Messages define the strings and variants
- Locales define language variants, direction, and formats
- Attributes and Segments describe runtime audiences
- Targets decide which app surface receives which content
- Tests and Examples make behavior visible before release
At release time:
- Build turns definitions into datafiles (JSON files)
- Deployment publishes those files (to a CDN or along with your application)
- SDKs consume them in applications
- Catalog gives humans a browsable experience of the project

