Skip to content

docs(kb): strengthen GT guidance and validate examples in #663 - #679

Merged
kevinwu98 merged 19 commits into
kb/informational-articlesfrom
codex/kb-663-review
Oct 23, 2026
Merged

kevinwu98 merged 19 commits into
kb/informational-articlesfrom
codex/kb-663-review

Conversation

@pie575

@pie575 pie575 commented Oct 22, 2026 •

Copy link
Copy Markdown
Contributor

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-articles head (d782d7d1). This PR contains 15 article-specific commits and should be reviewed against that branch. It does not merge or publish the parent.

Article Change and reason
GT vs. TMS Restore Faster / Cheaper to run / Higher quality / Lower risk, current Cursor proof, catalog-first adoption, and scoped JavaScript runtime independence. Retain accurate competitor automation and human-service evidence.
What is a TMS? Explain the code-connected alternative through context, generation, review, and retained catalogs; leave detailed vendor selection to the comparison hub.
Make a website multilingual Include GT in the approach table and distinguish source authoring, generated files, and existing-library adoption.
AI translation accuracy Include GT's production workflow in the comparison; distinguish CLI/service generation from SDK rendering and WMT findings from GT evaluation.
JSON translation Add the GT option, import reviewed catalogs before generation, scope the worked config to English/German, and retain target-plural validation.
Markdown translation Restore the repository-release comparison, shared terminology, reuse, and built-in review; preserve the AST demonstration and syntax checks.
SRT translation Add the recurring-release option; reject malformed/nonpositive timings and invalid inputs, with explicit checker limits and video review.
iOS localization Preserve Xcode agent capabilities; add import-first generation, target-plural handling, raw review, cross-product context, and current Ramp evidence.
Launch checklist Restore useful GT guidance at the relevant pass conditions, including branches, variables, review, configured automation triggers, and local/CDN delivery. Keep the release record; remove repeated FAQs.
Next.js SEO Clear inherited alternate metadata for unpublished pages, select a published x-default, and connect reviewed generation to the publication map.
Locale routing Replace the duplicated partial language parser with a tested routing decision over a resolved preference; explain the supported all-prefixed configuration.
Language switcher Complete the globe and Escape/focus behavior; add tested GT links with active-language state.
Pseudo-localization Explain how pseudo tests complement real translations and release review without assuming every German string expands.
Key naming Correct the component id prop versus translation-function $id option.
Hardcoded strings Remove an obsolete Locadex plan gate and specify the configured compiler/build path for automatic JSX injection.

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:

  • All repository validator tests, content validators, internal links, script typecheck, unchanged OpenAPI regeneration, production content build, and whitespace checks pass. CI-equivalent run used Node 22.
  • Published gt@2.26.6, gt-next/gt-react@11.4.14, and generaltranslation@9.5.7 checked. JSON/Markdown/SRT/XCStrings file discovery and inline extraction run locally.
  • Next 16.4.2 production fixture passes routing, supplied French metadata, inherited-alternate clearing, publication filtering, eight sitemap URLs, and locale-aware link checks.
  • Routing/subtitle positive and negative cases pass. Chromium checks cover switcher keyboard/focus/cookie behavior and representative article rendering.
  • Independent critique covered every substantive addition/deletion, with all editorial findings resolved.

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 under kb/validation/2026-10-22-pr663-*.

User-feedback follow-up:

  • Restore the exact linked Starter $0 platform-fee/unlimited-users/projects/languages comparison and the portable-file takeaway. Broaden customer evidence to current Ramp, Cursor, and Profound deployments, linked to the Enterprise page.
  • Restore the original evidence-led AI-accuracy summary; keep the GT workflow explanation in the body.
  • After the separate scope review, remove the extra switcher event-target guard and SVG detail, and restore original case-insensitive locale matching. Retain Escape/focus restoration and the other accepted fixes. Targeted browser and routing checks pass.
  • KB, reference-link, internal-link, and production-build checks pass for this follow-up; independent critique approved all changed passages.

pie575 added 15 commits October 22, 2026 10:40
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.
@pie575
pie575 requested review from a team as code owners October 22, 2026 17:41

@cursor cursor Bot left a comment •

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Stale comment

Risk: medium. This updates 15 public knowledge-base articles with user-facing guidance and copyable examples, which is above the low-risk approval threshold. Human review is needed, and no reviewers were assigned.

Open in Web View Automation 

Sent by Cursor Approval Agent: Pull Request Router

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.

@cursor cursor Bot left a comment •

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Stale comment

Risk: medium. This updates 15 public knowledge-base articles with user-facing guidance and copyable examples, which is above the low-risk approval threshold. Human review is needed, and no reviewers were assigned.

Open in Web View Automation 

Sent by Cursor Approval Agent: Pull Request Router

@cursor cursor Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Risk: medium. This updates 15 public knowledge-base articles with user-facing guidance and copyable examples, which is above the low-risk approval threshold. Human review is needed, and no reviewers were assigned.

Open in Web View Automation 

Sent by Cursor Approval Agent: Pull Request Router

@kevinwu98
kevinwu98 added this pull request to stack #684 October 22, 2026 21:15
@kevinwu98
kevinwu98 merged commit 165e378 into main Oct 23, 2026
8 checks passed
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>
@kevinwu98
kevinwu98 deleted the codex/kb-663-review branch October 23, 2026 01:42
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants