5 posts tagged with "i18n"

This article outlines the key considerations and technical details involved in implementing a "News Page" on a Docusaurus site, designed to list domestic and international news sources.

This article is a record from when it was written. For the continuously maintained procedure, see the technical documentation version.

1. Page Purpose and Key Features​

The primary goal was to build a personal information hub for quick access to reliable news sources. The page is built as a static site, emphasizing fast performance, usability, and maintainability.

When implementing Algolia DocSearch on a multi-language (i18n) site built with Docusaurus, I faced the challenge of search results containing mixed languages. It's common for situations to arise that harm the user experience, such as English pages appearing in search results when searching in Japanese.

This article is a record from when it was written. For the continuously maintained procedure, see the technical documentation version.

This article organizes the specific setup steps as a technical memo to solve this problem and achieve an optimal search experience that syncs with the site's display language.

This post is a memo organizing the process of internationalizing (i18n) the main UI components of a Docusaurus site: the navbar and footer.

For the basic i18n setup, see Procedure for Implementing Multi-language (i18n) Support on a Docusaurus Site.

Note that this article is a record from when it was written. For the continuously maintained procedure, see the technical documentation version.

1. Purpose​

The Docusaurus i18n feature is a mechanism for making site text multi-lingual. This time, I'll explain the process of adding new items to the navbar and footer and translating them from Japanese (the default) to English.

This article organizes the steps I took to implement multi-language support (i18n) on a Docusaurus site, enabling content switching between Japanese (default) and English.

Based on the official documentation, this guide also includes practical tips for real-world scenarios, such as commands for a Docker environment and reliable methods for verifying functionality before deployment.

See also the record of solving the routing and deployment issues that arose afterward, and the procedure for internationalizing the navbar and footer.

Note that this article is a record from when it was written. For the continuously maintained procedure, see the technical documentation version.

Prerequisites:

• Site Generator: Docusaurus (project already set up)
• Development Environment: Docker (local environment commands are also provided)
• Goal: To support two languages: Japanese (ja) and English (en)

This article is a record of the journey from identifying to resolving two tricky problems I encountered when adding internationalization (i18n) to a site built with Docusaurus v3: "client-side routing collapse" and "container startup failure on Cloud Run."

The basic i18n setup steps are covered in Procedure for Implementing Multi-language (i18n) Support on a Docusaurus Site.

Note that this article is a record from when it was written. For the continuously maintained procedure, see the technical documentation version.

Prerequisites:

• Site Generator: Docusaurus v3
• Hosting: Google Cloud Run
• Development & Deployment: Docker, GitHub Actions
• Package Manager: pnpm