The Best International & Localized Devportal for the DevPortal Awards category was first introduced in 2019. We will highlight the criteria that we think defines this category and provide examples based on prior year nominations.

Throughout our developer portal research and project work, we found that companies often address audiences with specific expectations in various regions. When you pay attention to accessibility, internationalization & localization elements, the overall user experience will be better and your users will be more likely to engage with your devportal.

This article collects various explanations, tricks and tools that enable inclusivity in the broad sense. The examples in this post are taken from some of the DevPortal Awards 2018 nominees.

Best international & localized portal

Our DevPortal Awards definition for this category: “Devportals that implement devices or content strategies to address cultural diversity, differences in language capabilities, local legal requirements and regional expectations.”

According to Wikipedia, internationalization (I18n) is the process of designing a software application so that it can be adapted to various languages and regions without engineering changes. Localization (L10n) is the process of adapting internationalized software for a specific region or language by translating text and adding locale-specific components. In short: internationalization — with its design and development practices — enables localization for target audiences that vary in culture, region, or language.

Cultural diversity & language capabilities

In her article on the role that UX writers play in localizing a regional product, Nina, of Honestbee design, states that “it’s more than just writing with correct grammar, it’s truly about using words that people can identify with.'' Some of the listed tips:

  • Adopt language inclusivity (avoid jargon, slang or idioms, and use gender-neutral pronouns).
  • Use the 30% rule for interface copy (some words become longer after translation: consider this in the UI design phase).
  • Build a team of content reviewers that are familiar with the language, specific user needs and the cultural habits.

Localization is more than translating and updating existing content: it aims at adapting a product, application or content to the language, cultural and other requirements of a specific target market, the “locale”. It might require the rethinking of logic and visual design. Localization can involve customization connected to:

  1. Numeric, date and time formats
  2. Use of currency
  3. Keyboard usage
  4. Collation and sorting
  5. Symbols, icons and colors

At the API the Docs London 2018 conference, Atsushi Nakatsugawa illustrated what the benefits of localization are, in comparison to translation only.

Local legal requirements & regional expectations

What do you need to run a global API business? You translate or localize content, and also:

  • Prevent misinterpretations and avoid content that users might consider as sensitive or inappropriate.
  • Pay attention to regional legal requirements (e.g. some regions don’t allow deep linking).
  • Take regional business restrictions into account.
  • Research local user expectations: this will influence your devportal’s ideal UX accordingly.

Example of product selection based on region (Orange)

The examples in this post are taken from some of the previous DevPortal Awards nominees and winners.

Developer Portal Categories

The Best Developer Portals of 2020 Learn more about the ten nomination categories for the Developer Portal Awards of 2020 and how you can submit a nomination.

Read more Nominate a Developer Portal

All Pronovix publications are the fruit of a team effort, enabled by the research and collective knowledge of the entire Pronovix team. Our ideas and experiences are greatly shaped by our clients and the communities we participate in.

About the author

Kathleen De Roo

Information Architect, Technical Content Writer

Kathleen started as a technical content writer, responsible for doing research and writing on developer portal aspects. As an information architect, she helps clients find out how to align business goals and user needs with the knowledge we gathered about devportals.

She holds master's degrees in history and in archival science & records management.