> Documentation index: [llms.txt](https://www.i18next.com/llms.txt). Every page is also available as Markdown at its URL plus `.md`.

# Blog

- [The history of i18next, from 2011 to version 27](https://www.i18next.com/blog/the-history-of-i18next.md): i18next began in December 2011 as a translation library for single-page apps. The decisions taken since still shape how it works today: one core for every environment, plugins for everything around it, and code for version 1 that still runs with a layer.
- [i18next 27 and react-i18next 18: what changes and how to upgrade](https://www.i18next.com/blog/i18next-27-react-i18next-18.md): i18next 27.0.0 and react-i18next 18.0.0 came out on 2026-11-07. They change defaults most setups had to override, keep the logger and the React options per instance, refuse language codes that look like markup, and make Trans render values as written. What changes for your app, and a prompt that upgrades it.
- [Who uses i18next: at least 1,188 of the 100,000 most linked websites](https://www.i18next.com/blog/who-uses-i18next.md): We searched the scripts of the 100,000 most linked websites for i18next's code. At least 1,188 run it in their own code, from X, NBA and DeepL to Lufthansa, Strava and UEFA: the data, the method and its limits.
- [How to translate an Astro site with i18next](https://www.i18next.com/blog/astro-i18n.md): Astro's i18n routing gives each language its address; plain i18next adds t(), plurals and fallbacks while the site is built, and sends no JavaScript to the browser. i18next-cli with its Astro plugin keeps every language complete.
