Skip to main content

v0.0.2

Internationalization release for the Next.js application template.

SectionHistory / Releases
UpdatedJul 6, 2026
AuthorTemplate Maintainers
Versionv0.0.2
Reading time2 min

v0.0.2

v0.0.2 adds a reusable localization foundation across the main template flows. It introduces next-intl, English and Russian message catalogs, localized metadata, and translated core UI copy.

Highlights

  • Added next-intl to the template stack.
  • Added English and Russian message catalogs for main feature areas.
  • Localized page titles, descriptions, Open Graph metadata, and Twitter metadata.
  • Moved core UI copy into translation namespaces instead of hard-coded strings.
  • Added shared helpers for server and client translation consumers.
  • Updated environment examples for locale and analytics configuration.

What changed for template users

The template now has a default bilingual setup with supported locales en and ru. Route metadata, forms, navigation, auth pages, account settings, workspace management screens, and shared UI copy resolve through message catalogs.

The default locale is controlled through PUBLIC_DEFAULT_LOCALE.

Upgrade notes

  • next-intl is part of the default stack.
  • Translation files live under src/messages/.
  • Configure the default locale with PUBLIC_DEFAULT_LOCALE.
  • Yandex Metrika now expects NEXT_PUBLIC_YM_COUNTER_ID.

Quality

The release adds tests for i18n request setup, page translation helpers, localized metadata, translated runtime components, localized forms, schema-backed validation copy, environment access, and global error behavior.

Related pages