Cisco Meraki used Localize to deliver its dashboard in 13 languages and extend human-translated Japanese content to nearly 200 help articles. Working with regional teams and an external translation partner, Meraki built localization workflows around the technical content its customers rely on.
Results at a glance
Cisco Meraki provides cloud-managed networking solutions. Its dashboard gives IT teams a central place to configure and troubleshoot their networks, while its documentation provides detailed guidance for deploying and managing Meraki products.
Making those resources available in other languages required a localization process that could accommodate technical terminology and an evolving application.
Meraki’s dashboard was a dynamic web application serving multiple organizations. The team needed to identify the content that belonged in translation and exclude content that didn’t.
Japanese content required particular attention. The complexity of Meraki’s products called for human translation and review, with regional specialists involved in maintaining the dashboard.
Documentation introduced another challenge. Meraki was planning a phased localization effort across a library of approximately 1,800 articles, starting with Japanese. Its initial approach involved working with an external translation agency and manually duplicating documentation pages.
The team needed a practical way to deliver those translations within its existing documentation site.
Meraki worked with Localize to support human translation by its Japanese and Russian teams. Localize’s Customer Success team trained contributors and helped them work through content detection and exclusion requirements.
Project-level translator permissions supported participation across teams. Glossary management, including bulk imports, gave contributors a way to manage the technical terms used throughout the application.
For Japanese, the workflow established an ongoing role for Meraki’s Japan team, which maintained human translations as dashboard content changed.
Meraki tested Localize on its MindTouch documentation site, then worked with Localize and translation partner RWS to establish an import-and-export process for human translation.
Localize delivered the translated content in the browser. That approach let Meraki use its existing documentation pages without creating separate language subdirectories for the Japanese rollout.
Preparing the source content also mattered. During the initial handoff, the teams identified duplicate content coming from administrative pages. Localize helped refine phrase detection so the translation file better reflected the articles intended for readers.
By the time of the 2021 case-study record, Meraki’s dashboard was available in 13 languages. Its Japan team maintained Japanese dashboard translations through regular updates.
The documentation project had also brought human-translated Japanese content to nearly 200 help articles, with Localize delivering the translations within the existing site.
Meraki’s experience shows why technical localization needs clear ownership alongside content delivery. Regional specialists handled language work, the external agency supported documentation translation, and Localize helped connect those contributors to the content they needed to maintain.
Talk to a Localize expert about managing multilingual web applications and help content with the right translation and review process.
