Repository navigation
docs(kb): strengthen GT guidance and validate examples in #663 - #679
Merged
Merged
Conversation
Restore the four reviewed benefits and current customer proof. Explain catalog retention, generation versus rendering, and independent local delivery while preserving scoped competitor evidence.
Replace the generic closing comparison with concrete generation, context and review mechanisms. Keep vendor selection detail in the comparison hub.
Explain generation and review alongside developer-owned routing, and distinguish inline source authoring from generated translation files.
Include GT where readers compare approaches, attribute extraction and generation correctly, and keep WMT evidence separate from GT quality claims.
Use a supported English-to-German message family, retain Polish validation guidance, and place existing-catalog import before generation. Add concrete context and review guidance.
Include syntax-aware GT generation and reuse in the decision table, and connect shared terminology to built-in review while preserving parser examples.
Reject malformed ranges and nonpositive durations, state checker limits, and explain GT for recurring subtitle updates with video review.
Preserve Xcode agent capabilities and native rendering while explaining import-first generation, target plural handling, shared terminology and current Ramp evidence.
Place context, review, variable handling and configured update tests beside their pass conditions. Keep the release record and remove repeated closing material.
Clear inherited alternate metadata and choose a published x-default destination. Connect reviewed translation generation to publication state and scope the routing recommendation.
Use a resolved preference so the routing example does not duplicate an incomplete language parser. Explain stable localized content URLs with the supported GT configuration.
Add the actual globe and Escape focus behavior, and demonstrate crawlable GT locale links with the active language identified.
Explain complementary pseudo and real-language testing without implying German always expands or that development previews substitute for reviewed release translations.
Distinguish the T component id prop from the translation-function $id option while preserving the naming and maintenance guidance.
Remove an obsolete Locadex plan gate and document the configured compiler and supported Next.js build path required for automatic JSX injection.
Restore the linked Starter price and portable-file takeaway. Use current Ramp, Cursor, and Profound deployments as broader adoption evidence.
Answer the title with the original scoped WMT finding. Keep the GT workflow explanation in the body.
kevinwu98
approved these changes
Oct 23, 2026
kevinwu98
added a commit
that referenced
this pull request
Oct 23, 2026
Resolve the conflict in kb/en-US/multilingual-nextjs-seo.mdx between #650's answer-engine rewrite on main and this branch's rewrite plus #679. - Keep #650's question headings, requirements table, URL-structure and library comparisons, locale layout with isLocaleSupported, and build script. - Keep #679's published-locales record, noindex with alternates: null, x-default fallback, and rendered head and sitemap output. - Prefix every locale, matching the rest of the KB set, and describe html lang as an accessibility signal rather than a Google language signal. 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.


This review restores concrete reasons to choose General Translation where #663 had reduced them to a closing product description, while preserving its useful technical corrections and examples.
Stacked on #663's current
kb/informational-articleshead (d782d7d1). This PR contains 15 article-specific commits and should be reviewed against that branch. It does not merge or publish the parent.idprop versus translation-function$idoption.The other 12 affected paths in #663 remain unchanged after review. Existing URLs, strong examples, reviewed comparison distinctions, and scoped customer evidence are retained. Live/main content and all 66 open PRs (including drafts and upstream branches) were checked for overlap; pending TMS/SEO edits still need reconciliation if those branches publish later.
Validation:
gt@2.26.6,gt-next/gt-react@11.4.14, andgeneraltranslation@9.5.7checked. JSON/Markdown/SRT/XCStrings file discovery and inline extraction run locally.No hosted translation generation, native Xcode build, or measured AEO uplift is claimed. Repository Actions target PRs to
main, so they may not run on this stacked base. Timestamped decisions, primary sources, reviewed heads, fixtures, limits, and independent critique are saved in memory-base underkb/validation/2026-10-22-pr663-*.User-feedback follow-up: