Repository navigation
docs(kb): compare next-intl and gt-next workflows - #642
Merged
Merged
Conversation
![cursor[bot]](https://avatars.githubusercontent.com/in/1210556?s=60&v=4){kind=small}
pie575
changed the title
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
pie575
enabled auto-merge (squash)
October 16, 2026 23:27
- Lead with the direct answer: next-intl renders supplied translations; gt-next also generates them - Add translation, routing, plurals, delivery, and license rows to the comparison table - Rephrase H2s as questions, add a Common questions section and Key takeaways - Move Profound into a production-use section alongside other customers - Link general-translation-vs-i18n-libraries and multilingual-nextjs-seo Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
kevinwu98
approved these changes
Oct 16, 2026
…chor Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Compares next-intl and gt-next for teams deciding whether to retain their catalogs or change their Next.js integration. It covers using GT with existing next-intl messages, Server Component and client-boundary APIs, App Router delivery, and Profound's production use. Pricing links to the canonical page; the article avoids the generic feature pitch shared by earlier drafts.
The no-files recommendation and App Router walkthrough are consolidated into their established pages in #630. This article has no dependency on unpublished cross-PR links.
Validation: content checks, validator tests, script typecheck, production build, and browser rendering passed. Existing code fences are unchanged. A sentence-overlap check and editorial review found no repeated pitch with the React shortlist in #643; this is an editorial check, not a search-ranking measurement. Hosted translation was not executed.