惯性聚合 高效追踪和阅读你感兴趣的博客、新闻、科技资讯
阅读原文 在惯性聚合中打开

推荐订阅源

博客园 - 聂微东
爱范儿
爱范儿
博客园 - 三生石上(FineUI控件)
Recent Announcements
Recent Announcements
大猫的无限游戏
大猫的无限游戏
MongoDB | Blog
MongoDB | Blog
A
About on SuperTechFans
M
MIT News - Artificial intelligence
V
Visual Studio Blog
云风的 BLOG
云风的 BLOG
The GitHub Blog
The GitHub Blog
Jina AI
Jina AI
P
Proofpoint News Feed
博客园_首页
酷 壳 – CoolShell
酷 壳 – CoolShell
T
The Blog of Author Tim Ferriss
G
Google Developers Blog
宝玉的分享
宝玉的分享
Engineering at Meta
Engineering at Meta
Last Week in AI
Last Week in AI
aimingoo的专栏
aimingoo的专栏
罗磊的独立博客
N
Netflix TechBlog - Medium
人人都是产品经理
人人都是产品经理

Sanity.io

A Board Game agent built using Sanity Context and Vercel's AI SDK | Sanity Build a prototype with Claude Code that your whole team can edit | Sanity What’s New - May 2026 | Sanity I built a London pub guide with v0 and the Sanity MCP in six hours. Here's what I learned. | Sanity Build a conference concierge with Agent Context and Anthropic | Sanity Build a content-aware Telegram agent with Vercel AI SDK and Chat SDK | Sanity How I used Agent API to generate photos for my family’s recipes | Sanity What’s New April - 2026 | Sanity Better context, better matches: An AI love story (for dogs) | Sanity How to write for an agent | Sanity Content Agent, meet Slack: AI content operations in your workflow | Sanity Structure powers intelligence | Sanity Your agent needs better content. Here's how to give it. | Sanity How to serve content to agents (a field guide) | Sanity Sanity TypeGen GA: Automatic TypeScript types for content and GROQ | Sanity Sanity is now available on the Vercel Marketplace | Sanity The logo soup problem (and how to solve it) | Sanity Content Releases: From scattered updates to coordinated publishing | Sanity What's New - February 2026 | Sanity How we solved the agent memory problem | Sanity v0 Builder Challenge: The winners | Sanity Introducing: Sanity Agent Skills | Sanity Content Agent: Days of work in one conversation | Sanity Our Sanity Values | Sanity Open Source Pledge 2025: Stepping up when it matters | Sanity v0 builder challenge: $3000 in prizes | Sanity Why AI Breaks Without Structured Content Operations | Sanity What’s New January - 2026 | Sanity BFCM 2025: What teams built when infrastructure stopped being the problem | Sanity How AI shaped holiday shopping and what it means for content in 2026 | Sanity
Internationalization is more than translating words | Sanity
Simeon Griggs · 2025-09-02 · via Sanity.io

In Episode 17 of the Code && Content podcast, Jan Amann, creator of next-intl, joined me to discuss how his package went from a part-time hobby to the go-to solution for localization in React applications.

next-intl was created from Jan's real-world experience of developing multi-lingual and multi-region applications and having to copy patterns between projects. Eventually rolling up those patterns into the library we know today.

It even supports the Next.js app router, which, based on React server components, required a major rewrite almost a year in the making.

More than words

Localizing a web application is much more than just translating words on the page. You have to think about currencies, dates, regions versus markets, product availability, cultural expectations and more.

Further, you likely want authors to be able to collaborate and constantly update internationalized content, as well as either automating or commissioning translations.

Internationalization involves layers upon layers of complexity which are non-negotiable for multilingual and multi-market companies.

If there is even a slight chance that your web application will require localization at some point later on, it is best to begin with it in mind as early as possible in a project. Adding you first alternative language is far more difficult than adding a third.

Code-first approach

next-intl is designed to promote best-practice developer experience while still giving you the flexibility to localize your app in the way you like. This pairs perfectly with Sanity Studio schema which is defined in code.

A multi-dimensional content model that takes in considerations of language, regions and markets can't be easily defined by clicking around a settings panel. It is best driven by code.

Your language and market settings can be shared between the content model that configures your editing admin panel and the front-ends your users interact with.

There are official plugins available for Sanity Studio to setup localization in the most common way. But as always you are free to customize your content models however you need.

Resources