Documentation

Messagevisor is a Git-based translation management toolkit for teams that want definitions, tests, examples, generated datafiles, and runtime behavior to live in the same repository.

The docs are organized to help you move from "what is this?" to "how does this specific behavior work?" without having to guess which page fills in the missing detail.

Learn#

These pages explain the overall model and the main development loop.

• Quick start
• Projects
• Configuration
• CLI

Concepts#

These pages explain the design philosophy behind Messagevisor.

• GitOps
• Translations as code

Model#

These pages define the core authoring entities that make up a Messagevisor project.

• Locales
• Inheritance
• Formats
• Messages
• Attributes
• Segments
• Targets
• Namespaces
• Overrides

Operate#

These pages cover the workflows you use while authoring, validating, building, and reviewing project output.

• Linting
• Testing
• Examples
• Evaluation
• Building datafiles
• Export and import
• Catalog
• Code generation
• Deployment

Integrate#

These pages focus on runtime use, extensibility, and surrounding tooling.

• SDKs
• Frameworks
• Modules
• Parsers
• Plugins
• Datasource

Multi-set workflows#

If your repository models multiple environments or release stages, start here.

• Sets
• Promotions
• Environments
• State files

Use cases#

Real-world scenarios showing how Messagevisor fits into product engineering workflows.

• Decoupling translation releases from code deployments
• Environment-specific translations
• Audience-targeted copy variants
• Managing regional language variants
• Deprecating and retiring message keys
• Platform-specific copy
• Testing translations before they ship
• Establishing ownership of translation content
• Auditable compliance and legal copy
• Promoting translations through environments
• RTL language support without application rework
• Consistent number and date formatting across locales
• Copy variants for A/B tests
• Multi-brand or multi-product translations in one repository
• Onboarding non-engineers to the translation workflow

Reference#

• Glossary
• FAQ
• Roadmap
• Contributing

How to use these docs#

• Read Projects and Configuration first if you are setting up a repository.
• Read Locales, Messages, and Targets together if you are shaping your content model.
• Read Inheritance, Export and import, and Catalog together if translation work happens outside Git and returns through CSV or JSON.
• Read Testing, CLI, and Catalog together if you are debugging behavior or onboarding teammates.
• Read Building datafiles and SDKs together if you are wiring generated artifacts into an application.
• Read Frameworks after SDKs when you want examples for Next.js, Astro, Express, or Fastify.
• Read React SDK and React Intl compatibility together if you are migrating an existing React Intl application.
• Read Sets, Promotions, and Environments if you are modeling multiple deployment stages in one repository.