Conversation
|
@Vivian-04 Great news! 🎉 Based on an automated assessment of this PR, the linked Wave issue(s) no longer count against your application limits. You can now already apply to more issues while waiting for a review of this PR. Keep up the great work! 🚀 |
7b25f0b to
7ae8230
Compare
|
The QA logic currently treats every English navigation page as an untranslated page, then compares each page with itself. It also never exits nonzero. Please pair guides/stellar-quickstart.es with its English source, check only translated pages, wire the command into CI, and fail on drift. |
|
The QA logic currently treats every English navigation page as an untranslated page, then compares each page with itself. It also never exits nonzero. Please pair guides/stellar-quickstart.es with its English source, check only translated pages, wire the command into CI, and fail on drift. |
|
The latest merge still deletes the full docs.json file, and CI fails. Please restore the current develop config and keep this PR limited to localization QA. Remove the unrelated event schema file too. |
|
No problems. Apologies for the stress and errors. |
PR #162 [Wave 9] Add localization QA for translated documentation
Summary
This PR adds a localization QA script to check translated documentation pages for:
Changes
localization-qa.js(new file): Standalone Node.js script that performs comprehensive localization QA on the Wraith Protocol documentation. The script:docs.jsonto define supported translated pages from the navigation structure.md/.mdxfiles and extracts front matter metadataQA Results
Running the script against the current documentation reveals:
docs.jsonnavigation (excludingCLAUDE.mdandPR_DESCRIPTION.md)localefront matter metadataThe QA script identifies structural issues that need to be addressed when adding translations for the documentation.
Checklist
docs.jsonnavigationType
feat- Adds new localization QA functionality for documentationTesting
The script executes successfully with Node.js built-in modules only (no npm dependencies required). It reports all QA checks and produces detailed output for each issue type found.
Closes #162