Skip to content

Localization

The Language Customizations tab in the Partner Console provides partners with the ability to localize the Developer Hub experience. This includes configuring the portal name, navigation labels, compute and service type names, field descriptions, and all static text displayed across end-user pages.

Info

Language customization applies only to the Developer Hub.

The Language Customizations page supports the following capabilities:

  • Default Locale: Sets the initial language displayed when users access the Developer Hub.
  • Languages: Add new languages and configure translations for each.
  • Portal Navigation: Localize high-level portal and navigation labels.
  • Portal Interface Text: Localize field labels, descriptions, table headers, and static text.

Localization settings are inherited by all organizations under the partner.


Accessing Language Customization Settings

To access localization settings:

  • Log in to the Operations Console and navigate to Partners
  • Click one of the existing partner and click on Language Customizations tab

Default Locale

The Default Locale determines the language displayed when users first log into the Developer Hub. After login, users can switch to any configured languages using the in-product language selector.

Note

  • The default locale defines only the initial display language. Portal Navigation and Portal Interface Text settings can be configured in any language regardless of the selected default.
  • English, Turkish, and Japanese localization are supported by default.

Enable Language Options

The Enable Language Options toggle controls whether end users can view and switch between configured languages in the Developer Hub.

  • Enabled: All configured languages are displayed to end users, allowing them to select their preferred language.

  • Disabled: Language selection is hidden from end users, and the Developer Hub is displayed only in the configured Default Locale.

Note

This setting affects only language visibility for end users. Language configurations and translations remain unchanged in the Partner Console.

Language Customizations

Language Translations

Each language added under Languages appears as a separate tab.
Every tab contains two independent translation areas:

  1. Portal Navigation
  2. Portal Interface Text

Both sections must be saved separately.

Language Customizations


Portal Navigation

Portal Navigation defines the localized labels and descriptive text used across the left navigation menu and related portal UI sections. This configuration enables customization of navigation names, service types, and supporting descriptions for each supported language.

Setting Description
Navigation Labels Localized labels for primary navigation items such as Compute, Services, Workspaces, and other top-level menu entries.
Compute and Service Types Localized names for resource types such as Bare Metal, Virtual Machines, Notebooks, Applications, and similar service categories.
Descriptions Text displayed in navigation cards and landing sections to provide contextual information for compute and service types.
UI Metadata Attributes such as icons, label styles, and card-related metadata used to control visual presentation.

Localization values are defined using a JSON structure, allowing consistent and language-specific customization of portal navigation content.

Portal Settings

Note

  • The Save button is enabled only after changes are made to the portal navigation JSON.
  • If no changes are detected, the Save button remains disabled.
  • Portal Navigation localization settings are saved independently and applied based on the selected language or default locale configuration.

Portal Interface Text

Portal Interface Text defines all localized static and descriptive text displayed across the portal interface.

This includes:

  • Field labels
  • Field descriptions
  • Placeholder text
  • Table headers and column names
  • Action labels and button text
  • Status messages, empty states, and helper text

All values are managed using a JSON structure, enabling consistent translation and customization across supported languages.

Examples of configurable text include:

  • “Create”
  • “Delete”
  • “This field is required”
  • “Loading…”

Dev Hub Settings

Compare & Edit

The Compare & Edit option opens a side-by-side editor to compare the selected language against the latest English template.

  • The left pane displays the latest English JSON, which serves as the reference template.
  • The right pane displays the current translation for the selected language.
  • Newly added or missing keys are visible through the comparison view, making it easier to identify and update incomplete translations.

Changes made in this editor can be saved independently.

Example: Missing Translation Keys

In the example shown, the comparison view indicates an error because one or more keys present in the English template are missing in the selected language. This helps quickly identify newly introduced UI text that has not yet been translated and update the missing keys before saving.

Dev Hub Settings

Note

  • The Save button is enabled only after changes are made to the Portal Interface JSON.
  • If no changes are detected, the Save button remains disabled.
  • Portal Interface localization settings are saved independently and applied based on the selected language or default locale configuration.

Adding a New Language

Click Add Language to open the Add New Language dialog. Enter the name of the language you want to add (eg: German) and click Save.

Dev Hub Settings

Once the language is created:

  • A new tab is added for that language

Dev Hub Settings

  • Portal Navigation and Portal Interface Text Settings sections become available for customization
  • The portal name can be localized for that language
  • Navigation labels, compute types, and static text can be customized independently for that language

Info

Each translation section (Portal Navigation and Portal Interface Text) has its own Save button. Saving changes in one section does not affect the other.


How Localization Works After Configuration

Once languages and translations are saved in the Partner Console:

  • All configured languages automatically appear as selectable options in the Developer Hub
  • The Developer Hub UI displays portal-level labels based on Portal Settings for the selected language
  • Page content, table headers, field labels, descriptions, and static UI messages use the translations defined in Portal Interface Text
  • The localized portal name is shown in the Developer Hub header and navigation
  • Compute and service type names (e.g., Notebooks, Workspaces, AI/ML Jobs) are updated across all Developer Hub screens

End User Experience

1. Language Selection on the Login Page

Users can choose their preferred language directly on the Developer Hub login page. This selection determines the language used for the login interface and the initial session.

Japanese Login

2. Switching Language Inside Developer Hub

After logging in, users can switch between all configured languages using:

Developer Hub → Help → Language

Developer Hub Language List

Selecting a language updates:

  • Navigation labels
  • Compute and service type names
  • Portal name and section titles
  • Page descriptions, UI messages, and other static text

These updates are derived from the Portal Navigation and Portal Interface Text defined in the Partner Console.