Repository navigation
i18n(pt-br): pair three pages with their English versions by namespace - #2625
Open
bruno-andrade-azion wants to merge 1 commit into
Open
bruno-andrade-azion wants to merge 1 commit into
bruno-andrade-azion wants to merge 1 commit into
Conversation
Three pt-br pages carried a namespace that differs from their English version, so the language switcher, hreflang and the pt-br sidebar treated them as untranslated: - Changelog previous years: documentation_changelog_anos_anteriores - Terms of Service, November 10, 2020: ..._10_november_2022 (typo) - Terms of Service, March 30, 2023 (en) / April 26, 2023 (pt-br): corresponding revisions, published on a different date in each language The pt-br side now uses the English namespace. The pt-br changelog page is retitled "Changelog de anos anteriores" so its sidebar row is not a second "Changelog". The two Runtime API pages that wrote `namespace: >-` keep the value on one line, in both languages. The slugcheck ratchet baseline drops from 6 to 3. The remaining single-language pages are legal texts with no counterpart: the Marketplace Agreement (en), the 25 November 2022 Terms of Service (pt-br) and the two ANPD clause pages (pt-br).
bruno-andrade-azion
requested review from
a team and
marcus-souza-azion
as code owners
November 10, 2026 17:31
8 of 14 tasks
This branch has not been deployed
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.
What & why
Related issue: MM-16257
Pages affected:
/pt-br/documentacao/produtos/changelog/anos-anteriores/↔/en/documentation/changelog/previous-year//pt-br/documentacao/contratos/tds/10-novembro-2020/↔/en/documentation/agreements/tos/10-november-2020//pt-br/documentacao/contratos/tds/26-abril-2023/↔/en/documentation/agreements/tos/30-march-2023//{en,pt-br}/…/devtools/runtime/api-reference/readable-byob-reader/and…/stream-default-writer/(frontmatter layout only)Three pt-br pages now pair with their English version. Language versions pair by the
namespacefrontmatter. In these three pages the pt-br namespace differed from the English one, so the language switcher and hreflang did not link the two versions. The pt-br sidebar rows also opened the English page. In each case the pt-br side now uses the English namespace, because English is the source and the navigation trees key on it:documentation_changelog_anos_anteriores→documentation_changelog_previous_years.…_10_november_2022was a typo for…_10_november_2020.The pt-br changelog page was titled just "Changelog". Once paired, its sidebar row would have read "Changelog" right under "Visão geral", so it is now "Changelog de anos anteriores", which matches the English "Changelog previous years".
Two namespaces move onto one line.
readable-stream-byob-readerandwritable-stream-default-writerwrotenamespace: >-with the value on the next line, in both languages. The site's parser already read the value and paired these pages. Tools that read frontmatter line by line, such as agrep "^namespace: …"lookup, did not. The value is unchanged.The slugcheck baseline drops from 6 to 3 (
ci/baselines.json, viapnpm ci:ratchet slugcheck --update), so the three fixed pairs cannot regress.Four pages stay in one language on purpose. Each is a legal text that exists in only one language, and pairing it would mean writing a legal translation, which is Legal's call. None of them changes in this PR:
How I checked it:
gray-matterpass over every page, the same parser the site uses. Before: 4 namespaces only in English, 6 only in pt-br and 2 written as>-. After: 1 only in English, 3 only in pt-br, none written as>-, and no duplicate namespaces.pnpm lint:slugchecklists exactly the 3 pt-br legal pages above.pnpm ci:ratchet slugcheckpasses at baseline 3.pnpm lint:navcheckpasses. The three "has no Portuguese page; the row falls back to English" warnings for the fixed pairs are gone. The one for the Marketplace Agreement remains.--checkpasses on the 8 changed files. ESLint has nothing to check, because CI runs it only on code files.docs_gate.py --check) reports the same 14 findings before and after, all in body text this PR does not touch. The four P0 findings are false positives: the "TODO" they flag is the Portuguese phrase "TODO O RISCO".linkcheck.pyreports 0 unpaired namespaces among the changed files, down from 3. It also reports 23 broken links, all in the body of the pt-br previous-years changelog and all already onmain. They point to old/produtos/URLs, and the page is already on the broken-link list in MM-16193.pnpm build:localpasses with Node 26: 2,092 pages, and the frontmatter test passes. In the built HTML:hreflangalternate, in both directions. In production today, the pt-br April 26, 2023 page has no English alternate;i18nPageson each of the six pages carries the counterpart URL, as it does on the March 3, 2023 pair used as a control;sidebar-trees.jsonlinks the three rows to the pt-br pages, where it used to fall back to/en/;linkcheckratchet does not run locally under Node 26, so CI covers it.Type of change
feat)fix) — typo, broken link, wrong informationdocs) — rewrite, expansion, upkeepi18n)refactor/chore) — reviewed by UXE, no content mixed inAuthor checklist
type(scope): summary(see GOVERNANCE.md §4)title,description,meta_tags,namespace,permalink,last_reviewed— none of these pages carrieslast_reviewed, and the pt-br April 26, 2023 terms have nometa_tags; the legal pages' missingmeta_tagsbelong to MM-16262pt-brupdated in this PR or follow-upi18nissue created: both languages are in this PR; the four legal pages in only one language need Legal, as noted in MM-16257pnpm build:local(build + frontmatter check) without errors