​
What are Namespaces?

Namespaces are logical containers within a project that group related translations together. They help organize your translation keys by feature, component, or any other logical division that makes sense for your application. Think of namespaces as folders in a file system - they provide structure and help prevent naming conflicts while making translations easier to manage.

​
Why Use Namespaces?

Organization

Group related translations together for better maintainability

Separation of Concerns

Isolate different features or components to avoid conflicts

Team Collaboration

Allow different teams to work on different namespaces independently

Performance

Load only the translations you need, reducing bundle size

​
Namespace Structure

A typical application might use this namespace structure: 
Project: E-commerce Website
├── common/          # Shared UI elements
│   ├── buttons
│   ├── navigation
│   └── forms
├── product-catalog/ # Product listing and details
│   ├── filters
│   ├── search
│   └── product-card
├── checkout/        # Purchase flow
│   ├── cart
│   ├── payment
│   └── confirmation
└── user-account/    # User profile and settings
    ├── profile
    ├── orders
    └── preferences

​
Creating Namespaces

​
Via Dashboard

1

Navigate to Project

Go to your project dashboard and select the project you want to work with
2

Go to Namespaces Tab

Click on the “Namespaces” tab in your project navigation
3

Create New Namespace

Click “Create Namespace” and fill in the details.
By default new namespaces are created with main version.

​
Namespace Versioning

Each namespace can have different versions, allowing for independent updates.

​
Best Practices

​
Keep Namespaces Focused

Avoid creating overly broad namespaces that contain unrelated translations. This makes maintenance difficult and reduces the benefits of organization.

​
Good: Focused Namespaces

auth/              # Only authentication-related
product-search/    # Only search functionality
user-preferences/  # Only user settings

​
Avoid: Overly Broad Namespaces

misc/              # Too vague
frontend/          # Too broad
translations/      # Doesn't provide organization

​
Troubleshooting

​
Next Steps

Versions

Understand how to version your namespace translations

Releases

Package namespaces into deployable releases