You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Add a performance considerations section to the internationalization guide so readers understand the trade-offs of adding multiple translations.
Changes
New "Performance considerations" section in /guides/internationalization covering build/deploy time, repository size, search and AI indexing, maintenance overhead, and runtime performance.
Feedback basis
Recent contextual feedback on /guides/internationalization flagged that the guide did not address the performance impact of adding multiple translations. The new section answers that question directly, distinguishing between build-time and runtime costs and pointing back to the existing translation workflow guidance for ongoing maintenance.
Other pages in the feedback window (/api/introduction, /quickstart, /status) had no actionable signal and were intentionally left unchanged.
Note
Low Risk
Documentation-only MDX additions with no application, auth, or deployment logic changes.
Overview
Adds a Performance considerations section to the internationalization guide (English, Spanish, and French) immediately before the FAQ, with anchor performance-considerations in the localized pages.
The new content explains how scaling translations affects build/deploy time (per-locale page builds), repo size (MDX and localized media), search and AI indexing (separate indexes; partial pages still surface), maintenance overhead (source changes fan out; links to external translation provider guidance), and clarifies that runtime page loads are not slowed by language count—only the requested locale is served.
Reviewed by Cursor Bugbot for commit ed32ae0. Bugbot is set up for automated code reviews on this repo. Configure here.
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
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.
Summary
Add a performance considerations section to the internationalization guide so readers understand the trade-offs of adding multiple translations.
Changes
/guides/internationalizationcovering build/deploy time, repository size, search and AI indexing, maintenance overhead, and runtime performance.Feedback basis
Recent contextual feedback on
/guides/internationalizationflagged that the guide did not address the performance impact of adding multiple translations. The new section answers that question directly, distinguishing between build-time and runtime costs and pointing back to the existing translation workflow guidance for ongoing maintenance.Other pages in the feedback window (
/api/introduction,/quickstart,/status) had no actionable signal and were intentionally left unchanged.Note
Low Risk
Documentation-only MDX additions with no application, auth, or deployment logic changes.
Overview
Adds a Performance considerations section to the internationalization guide (English, Spanish, and French) immediately before the FAQ, with anchor
performance-considerationsin the localized pages.The new content explains how scaling translations affects build/deploy time (per-locale page builds), repo size (MDX and localized media), search and AI indexing (separate indexes; partial pages still surface), maintenance overhead (source changes fan out; links to external translation provider guidance), and clarifies that runtime page loads are not slowed by language count—only the requested locale is served.
Reviewed by Cursor Bugbot for commit ed32ae0. Bugbot is set up for automated code reviews on this repo. Configure here.