Open
Conversation
- Add GitHub Actions workflow for auto-translating docs on push to main - Translate to 6 languages: Spanish, Dutch, French, Chinese, Italian, Japanese - Two-phase translation: catch-up (missing) + incremental (changed) - Deploy translations to prod branch for Mintlify - Zero-tolerance error policy with retry logic for transient failures - Validate OpenAI API key before starting translations
feat(i18n): Add automated translation workflow
- Catch-up phase: continue on errors, failed files picked up next run - Incremental phase: still fails on errors (user-changed files must succeed) - Add 400 status as retryable (OpenAI transient JSON parse issues)
- setup: checkout, install deps, detect changed files - translate-catchup: Phase 1 - translate missing pages - translate-incremental: Phase 2 - translate changed files - deploy: push to prod branch Each phase shows as separate box in GitHub Actions UI. Uses artifacts to pass translations between jobs.
…42) * fix: opt into Node.js 24 for GitHub Actions * fix(i18n): strip code fences from translations, translate nav labels Two critical fixes for translation quality: 1. MDX code fence issue: LLM was wrapping translations in ```mdx blocks - Updated prompt to explicitly forbid code fences - Added post-processing to strip fences if they appear - Added validation that output starts with frontmatter 2. Navigation labels: Sidebar group/tab names were staying in English - Updated update-docs-config.ts to translate labels via OpenAI - Added translation cache to avoid redundant API calls Both issues affected 63% of translated files (417/660). Re-run workflow to regenerate all translations. * feat(i18n): add OpenAPI spec translation Translates OpenAPI specification files (descriptions, summaries, titles) to all target languages while preserving technical fields. Changes: - Add translate-openapi.ts: Programmatically extracts translatable fields, batch translates them, preserves all technical fields exactly - Update workflow: Add translate-openapi job (runs parallel to MDX translation) - Update update-docs-config.ts: Add language-specific OpenAPI to API tabs This ensures API field descriptions (the gray text) are translated while property names, types, and technical values stay in English. * refactor(i18n): remove hardcoded glossary, rely on LLM understanding The explicit keepEnglish/brandTerms lists were unnecessary - GPT-4o naturally recognizes technical terms and preserves them. The prompt now provides structural guidance (what categories to preserve) rather than brittle hardcoded lists. Removed: - glossary.json - Glossary interface and loading code - Explicit term lists in prompt The prompt now describes WHAT to preserve (code blocks, inline code, URLs, technical acronyms) rather than listing specific terms. * feat(i18n): add German (de) language support * refactor(i18n): remove hardcoded term lists from OpenAPI translation --------- Co-authored-by: Frederic Schulz <fred@hyperlace.io>
…44) - MDX translation: 5 → 30 files concurrent (210 OpenAI calls max) - OpenAPI translation: 5 files × 7 languages concurrent - Fix invalid JSON in crawls.json (trailing comma) - Async file writes using fs.promises.writeFile - Single-line per-file logging: [file.mdx] es✓ nl✓ fr✓ de✓ zh✓ it✓ ja✓ Co-authored-by: Frederic Schulz <fred@hyperlace.io>
* fix(ci): set FORCE_JAVASCRIPT_ACTIONS_TO_NODE24 per job to silence Node 20 deprecation * fix(ci): pass OPENAI_API_KEY to deploy step for update-docs-config.ts --------- Co-authored-by: Frederic Schulz <fred@hyperlace.io>
01programs
force-pushed
the
fix/ci-node24-env
branch
from
2d6f729 to
ab25f2e
Compare
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
1 participant
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.
Quick bump for faster translation run.