fix(content-docs): allow translating doc labels in sidebars.js

[Josh-Cena]

Pre-flight checklist

• I have read the Contributing Guidelines on pull requests.
• If this is a code change: I have written unit tests and/or added dogfooding pages to fully verify the new behavior.
• If this is a new API or substantial change: the PR has an accompanying issue (closes #0000) and the maintainers have approved on my working plan.

Motivation

I noticed that some labels on the Docusaurus website remains untranslated, e.g. https://docusaurus.io/zh-CN/docs/next/i18n/tutorial. I realized this is because these labels are defined in sidebars.js, which we don't extract.

This PR is not the best solution, but requires the least work (otherwise we would need to parse the raw sidebars.js in getTranslationFiles again), so...😅

Test Plan

Test links

Deploy preview: https://deploy-preview-_____--docusaurus-2.netlify.app/

Related issues/PRs

#4542

[netlify]

✅ [V2]

Name	Link
🔨 Latest commit	3e5d21b
🔍 Latest deploy log	https://app.netlify.com/sites/docusaurus-2/deploys/62ab210f2bc14200088021fa
😎 Deploy Preview	https://deploy-preview-7634--docusaurus-2.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site settings.

[github-actions]

⚡️ Lighthouse report for the deploy preview of this PR

URL	Performance	Accessibility	Best Practices	SEO	PWA	Report
/	🟠 89	🟢 100	🟢 100	🟢 100	🟢 90	Report
/docs/installation	🟠 84	🟢 100	🟢 100	🟢 100	🟢 90	Report

[github-actions]

Size Change: 0 B

Total Size: 801 kB

ℹ️ View Unchanged

Filename	Size
website/.docusaurus/globalData.json	52.6 kB
website/build/assets/css/styles.********.css	106 kB
website/build/assets/js/main.********.js	603 kB
website/build/index.html	38.9 kB

_{compressed-size-action}

[slorber]

LGTM 👍 that's what I had in mind

Would just prefer to not have "docLink" in translation key.

[slorber]

why is the key "docLink" instead of just "doc"? I mean, we use "category" and not "categoryLink". It looks better to use the exact same term as the sidebar item type?

Was wondering if we don't want to use different keys for "doc" and "ref"?

[Josh-Cena]

Was wondering if we don't want to use different keys for "doc" and "ref"?

Not necessarily. A "ref" item is always accompanied by a "doc" item and we probably want to reuse the label for the two items, if they are the same.

[slorber]

hmmmm, why not 👍

Someday there will likely someone who will want different translations for different items that share the same label 😅 currently there's potential for conflicts, but this looks like a niche use-case so let's see if anyone complains

[Josh-Cena]

In that case we would need to differentiate each label independently. ref/doc is a pretty arbitrary cutoff, but each label being translated independently is... not too weird, just inconvenient.