Internationalization

ShipAny uses next-intl for built-in internationalization support. It can be enabled with simple configuration.

Project Internationalization

Project internationalization includes page titles, SEO information, login form text, and other content visible after launching the ShipAny project.

In the i18n/messages directory, configure page content through [locale].json files. By default, Chinese and English are supported. In the i18n/messages/ directory, you can find en.json and zh.json files. Before project deployment, modify the content to match your project’s requirements.

You can use AI to help generate content:

Prompt
update content of this file, for my new project "Flux AI", which is an AI Image Generator, with keywords "flux ai, ai image generator"

i18n-message

Landing Page Internationalization

Landing page content is configured in the i18n/pages/landing directory through [locale].json files.

By default, en.json and zh.json files are supported. Before project deployment, modify the content to match your project’s requirements.

Reference Prompt:

Prompt
I want to build a landing page for my product named "Flux AI Image Generator", please update the landing page json file, content reference @Web @https://www.flux.ai/

update-landing

Supporting More Languages

In addition to the default en and zh, if you need to support more languages like Japanese (ja), Korean (ko), French (fr), etc., you can follow these steps for multi-language configuration:

  1. Add corresponding language files like ja.json, ko.json, fr.json etc. in both the i18n/messages directory and i18n/pages/landing directory.

  2. Modify the i18n/locale.ts file to add support for more languages

i18n-locales

  1. Modify the middleware.ts file to add support for more languages

i18n-mid

  1. Preview the website to see the new languages supported

i18n-preview

References

next-intl