lingo.dev VS Next-js-Boilerplate

RAL configuration. Each augmented engine contained 72 glossary terms per locale pair (70 custom translations plus 2 non-translatables), a brand voice profile (formal EU regulatory register), and 13 locale-specific instructions. Glossary terms were extracted from a training set of articles separate from the test set used for evaluation. Example entries: EN "provider" → PT "prestador" (not "fornecedor"); EN "high-risk AI system" → PT "sistema de IA de risco elevado" (not "sistema de IA de alto risco"). At inference time, only terms matching the current paragraph are retrieved and passed to the model — glossary size does not bloat the context window. Engines were configured on Lingo.dev as stateful localization engines — persistent context applied to every request.

If you've read my previous articles on HTML5 elements you didn't know you need or CSS modal windows, you know we like unusual tech at Lingo.dev. These upcoming JavaScript features solve real problems that have annoyed developers for years.

At Lingo.dev, we've been using this a lot deep inside our localization API, and it's dramatically simplified our text processing pipeline. What used to require multiple specialized libraries and server-side processing can now be handled directly in the browser with just a few lines of code.

As you know, we love unusual tech at Lingo.dev. So when in my last essay, David commented he was surprised to not see "dialog" HTML element, it hit me - wait, but there's so many HTML5 elements that we don't even know about!

Wait, you can build modal windows without JavaScript? Yep, that's CSS secretly laughing at JavaScript behind its back. At Lingo.dev, we love diving into weird engineering rabbit holes that make other devs do a double-take.

At lingo.dev, we're always on top of the latest models to ensure our translations are perfect. So when Meta released Llama 4, I immediately dug into what makes it special and how we developers can leverage its power without the infrastructure headaches.

In this post, I'll walk you through how to build an automated CI/CD translation pipeline using Lingo.dev and Knock that will handle localized notifications for your app without requiring any manual translation work from your team. We’ll introduce some tools that can help you scale your application to a global audience, automate translations locally using Lingo.dev's CLI, and finally integrate that CLI into a CI/CD pipeline so that translations are automatically created when developers open a pull request.

Hey! Max here, one of the co-founders - great question!

Technically - it's a compiler plugin: it augments build artifacts, so that extracting text from the app into JSON files for further translation is no longer required.

Since we're solving the problem at compile time, React code remains the same, but the app becomes just one cli command away from being fully translated into other languages!

Here's me speedrunning (~2min?) the localization of a typical next js app from english to spanish: https://github.com/replexica/replexica/blob/main/getting-sta...

Security: Arcjet Rate limiting and bot protection without thinking about it.

I put this all together into a setup I reuse - nothing hidden, everything customizable. If anyone's curious, the whole thing is documented here: https://github.com/ixartz/Next-js-Boilerplate

What does your stack look like? Curious if anyone's using different setups.

- AI code review

It’s free and open source (MIT). Today the project sits around 11.8k GitHub stars and 2.2k forks. I’m still actively maintaining it and adding features.

Repo: https://github.com/ixartz/Next-js-Boilerplate

Why I built it

Spinning up auth, a DB, i18n, tests, and lint/format/CI for each new app was repetitive. This gives me (and hopefully you) a production-ready base in minutes, with opinionated defaults you can start.

I’m open to suggestions and feedback, what would you like to see next? I’ll hang around in the comments to answer questions.

Free Next.js SAAS boilerplate that supports, auth, database, i18n and more. When it comes to free boilerplates, do check our website store, where we provide templates, Nextjs and Tailwind with Firebase along at decent price 😁

Great job by the Next.js team on this release, I just updated my Next.js boilerplate project to 15.3: https://github.com/ixartz/Next-js-Boilerplate

It works perfectly!

Next Boilerplate

Huge fan of PGlite.

It's the perfect solution to have Postgres without the need of Docker. With just `npm install`, you can have a Postgres instance on your computer. So, it's extremely easy to onboard a new developer in your team.

And, the good news, PGlite works perfectly with Next.js.

I'm using PGlite in local and development environment with Next.js Boilerplate: https://github.com/ixartz/Next-js-Boilerplate

Repo: ixartz/Next-js-Boilerplate

I've built a starter in Nextjs 14 with auth: https://github.com/ixartz/Next-js-Boilerplate