The hard part of a multilingual help center is not translating the first batch of articles. It is keeping every language current while the product continues to change. Begin with shared categories, article templates, and a terminology glossary.
Assign an owner and review date to every critical article. When a product or policy changes, update the source language first and track the status of every localized version so outdated answers do not linger.
Prioritize content using search terms, searches with no results, and repeated questions from support conversations. This keeps the help center focused on what customers actually need instead of article volume alone.