next-intl VS next-saas-starter

next-intl Library: https://github.com/amannn/next-intl

We start with a project that was bootstrapped with create-t3-app. For internationalization we use next-intl and set it up as described in the getting started guide. With this initial project setup we can jump into implementing localized error messages.

When starting a new project with Next.js these days, next-intl and zod are my go to libraries for internationalization and schema validation, respectively. Of course, when using zod for client-facing validations I would like to translate potential error messages. The package zod-i18n can be used to achieve this for i18next, a popular alternative internationalization library. This means that by using this library as starting point one can quickly achieve zod translation with next-intl.

As we mentioned earlier, the Next.js works well with existing i18n libraries (react-intl, lingui, next-intl, and similar). In this tutorial, we will use the react-intl.

next-intl

Thanks! Do you mean the slider with partners logos? https://github.com/Blazity/next-saas-starter/blob/master/views/HomePage/Partners.tsx

Github: https://github.com/Blazity/next-saas-starter

And here's the demo: https://next-saas-starter-ashy.vercel.app/ :D

Checkout the source code https://github.com/Blazity/next-saas-starter (stars are greatly appreciated :D). It contains far more pages and components than the ones showed on homepage, so please checkout other pages too :D