Movabase Docs
User guide

Project Management

Managing projects

Project Management

This guide covers everything you need to manage your projects effectively in MovaBase.

Project Dashboard

The project dashboard is your central hub for managing translations, files, and project configuration.

Overview of Project Interface

When you open a project, you will see a clean interface organized into main sections:

ComponentPurposeLocation
Project HeaderShows project name, emoji, and descriptionTop of page
Navigation TabsSwitch between main project sectionsBelow header
Main Content AreaDisplays selected section contentCenter of page
SidebarLanguages, files, download/upload optionsLeft side (if applicable)

The project dashboard is designed to give you quick access to all project features without navigating away from your current context.

NEEDS_MEDIA

MovaBase projects have three main tabs that organize different aspects of project management:

Translations Tab

This is where you will spend most of your time, managing translation keys and values.

FeatureDescription
Translation TableMain editor for viewing and editing translations
Tree ViewHierarchical view of translation keys
Language ColumnsSide-by-side view of all languages
Search & FilterFind specific translations quickly
Bulk ActionsSelect and operate on multiple translations

Info Tab

Displays comprehensive project information and statistics:

SectionContent
Project DetailsName, description, emoji, download mode
Linked ProjectIf connected to another project
Snapshot MetricsTotal keys, language count, linked keys
Language CoverageBreakdown of keys per language with coverage percentage

Settings Tab

All configuration options for your project:

SectionContent
GeneralDownload mode, linked project configuration
IntegrationsBitbucket connection and sync settings
API & AccessAPI key management for programmatic access

Project Statistics and Metrics

The Info tab provides valuable insights into your translation progress:

Key Metrics Available

MetricDescriptionUse Case
Total KeysCount of unique translation keys in projectTrack project size and complexity
Languages ConfiguredNumber of languages added to projectEnsure all target languages are covered
Linked Keys in UseNumber of keys coming from linked projectsMonitor shared translations
Language CoveragePercentage of keys translated per languageIdentify gaps and priorities

Understanding Language Coverage

Language coverage helps you track translation progress across all your target languages:

Regularly review language coverage to identify which languages need more attention or translation resources.

Coverage is calculated as: (translated keys for language / total keys) × 100

Example coverage breakdown:

LanguageTranslated KeysCoveragePriority
English (default)150/150100%Source language
Spanish120/15080%Needs work
French90/15060%High priority
German45/15030%Critical

NEEDS_MEDIA

Project Settings

Access project settings to configure behavior, integrations, and access control.

Accessing Settings

Navigate to Settings tab by clicking "Settings" in the project navigation. The settings panel has three sections.

Project Information

Basic project details you can update:

FieldDescriptionEditable
Project NameDisplay name shown throughout interfaceYes
DescriptionOptional context about projectYes
Icon (Emoji)Visual identifier for the projectYes
OrganizationWhich organization owns this projectNo (fixed)

Changing project name or icon affects how it appears in dashboards and organization lists, but does not impact your translations or export structure.

Download Mode Configuration

Choose how your translations are structured when exported:

You can switch between modes at any time without losing data. The change only affects how translations are exported, not how they are stored.

Project Linking Setup

Connect your project to another project to share translation keys and values.

Understanding Linked Projects

Linked projects allow you to:

  • Share translation keys between related projects
  • Maintain consistency across similar applications
  • Reduce duplicate work
  • Keep translations in sync across projects

Use linked projects when you have multiple applications sharing common translations (e.g., mobile app and web app sharing authentication translations).

To connect your project to another:

  1. Open Settings
  2. Navigate to the "General" section
  3. Choose which project to link to from dropdown
  4. Select source language and target language mapping
  5. Save Changes

Linked translations will now appear in your project with a badge indicating their source.

Deleting Projects

When a project is no longer needed, you can delete it entirely:

Deleting a project permanently removes all translations, files, and associated data. This action cannot be undone.

To delete a project:

  1. Navigate to Settings tab for the project you want to delete
  2. Review all project information to confirm you are deleting the correct project
  3. Click delete button and confirm the action when prompted

NEEDS_MEDIA

Project Linking

Project linking enables sharing translations between related projects, helping you maintain consistency and reduce redundant work.

What is Project Linking

Project linking creates a connection between two projects within the same organization, allowing:

  • Automatic sharing of translation keys
  • Consistency across related applications
  • Single source of truth for common translations
  • Easier maintenance across projects

Benefits of Linked Projects

BenefitDescriptionExample
ConsistencyEnsure same translations across projectsMobile and web app using same "Login" translations
Reduced DuplicationDo not translate same key twiceCommon error messages shared between apps
Centralized UpdatesUpdate once, reflect everywhereChange "Sign In" text across all linked projects
Smaller BundlesShared keys do not duplicate in exportsReduce translation file sizes

Use Cases for Project Linking

Consider linking projects when:

Configure linking from project settings:

Step-by-Step Configuration

  1. Choose Source Project - Select project that will be the source of shared translations. This is typically your main or reference project.
  2. Select Source Language - Choose which language from the source project contains the translations you want to share.
  3. Map to Target Language - Select which language in your current project should receive these shared translations. This can be different from the source language name.
  4. Save and Verify - Save configuration. Navigate to your translations tab and verify that linked translations appear with a badge indicating their source.

Only translations for keys that exist in the linked project will be shared. New keys added to the current project will not automatically appear in the linked project unless they already exist there.

Managing Linked Languages

After linking projects, you can manage how shared translations behave:

Understanding Language Mapping

ScenarioSource ProjectTarget ProjectResult
Direct MappingEnglish (en) to Spanish (es)English keys shared to Spanish in target
Language Code Matchen to enKeys shared between same language codes
Cross-LanguageEnglish (en) to French (fr)English source shared as French translations

Identifying Linked Translations

Linked translations are visually indicated in the translation table:

  • Badge: Shows "Linked from [Project Name]" or similar indicator
  • Visual Distinction: Different styling or icon to separate from local translations
  • Source Information: Hovering may show which project the translation comes from

You can still override linked translations in your target project. Your local value takes precedence over the linked value.

Conflict Resolution

When both local and linked versions exist for the same key:

SituationPriorityResult
Only Linked ExistsUse linked valueDisplay shared translation
Only Local ExistsUse local valueDisplay your translation
Both ExistUse local valueYour translation overrides linked
Local is EmptyUse linked valueFallback to shared translation

Be careful when overriding linked translations. Changes may not be visible in the source project, leading to inconsistencies.

NEEDS_MEDIA

Project Info Panel

The Info tab provides a comprehensive overview of your project configuration and current state.

Viewing Project Details

Basic project information displayed prominently:

DetailDescriptionLocation
Project NameDisplay name of your projectHeader with emoji
DescriptionContext about projectBelow name
Project IDUnique identifierInfo section
Download StructureFile-based or language-basedInfo section
Linked ProjectConnected project ID (if any)Info section

Understanding Project Metadata

Additional technical details about your project:

MetadataDescriptionUse Case
Created AtWhen project was createdAudit trail
Updated AtLast modification timestampTrack recent activity
Organization IDWhich organization owns this projectMulti-tenant support
Linked Project IDConnection to another projectProject linking feature
Download ModeExport structure settingFile organization

Project metadata is automatically maintained and updated. You do not need to manually track timestamps or IDs.

Export Format Information

The Info panel shows your current export configuration:

SettingOptionsDescription
FormatJSON, PO, iOS .strings, Android .xmlDetermines export file type
StructureFile-based or language-basedDetermines folder/file organization
Linked TranslationsEnabled or disabledShows if project linking is active

Best Practices for Project Management

Project Organization

Team Collaboration

Clear project structure and well-documented settings help new team members get up to speed quickly and make informed decisions.

Maintenance

Regular project maintenance ensures healthy translation management:

TaskFrequencyPurpose
Review CoverageWeeklyIdentify translation gaps
Check Linked ProjectsMonthlyVerify connections are still needed
Audit SettingsQuarterlyConfirm settings match current needs
Clean Up TranslationsBi-annuallyRemove unused or obsolete keys

Troubleshooting

Common Issues


Part 3 of 14: Project Management Complete

Next: Language Management

On this page