For non-English customers, being able to provide a completely localized experience to its user base is paramount. In previous versions of the API Developer Portal (i.e. 3.5), it was possible to do so out of the box. However, since the later versions of the API Developer Portal (Enhanced Experience), Broadcom has taken the decision to not allow localization of the API Developer Portal and instead decided to create a separate product (the API Hub) to allow customers to customize the experience to their liking.Unfortunately, the API Hub in question falls short on several aspects:
For all these reasons and more, the proposed API Hub is not a straightforward solution that replaces the localization options that were provided by the previous versions of the portal. Users that wish to upgrade from the 3.5 portal to this version have quite a surprise when they realize this.
Since some companies are legally obligated to provide a non-English experience to their users, I would therefore like to request that the Developer Portal has full localization support for all static and dynamic content, email templates, and user profiles. The Portal should provide a mean to set the default language to be used and should also store the language preference of users in their profiles (in the database) and not in the local storage of the browser (which is volatile).