New Relic documentation exists on these sites:
You can toggle between languages with a button in the top menu bar.
Every doc's frontmatter includes its translation status.
If there is no
translate: element in the frontmatter, the doc has not been translated into any other languages.
translate: element has a language abbreviation, such as
jp, then the doc has been translated, will be translated, or is under consideration for translation. For example:
---title: 'NRQL reference'translate:- jp- krmetaDescription: "A detailed reference list of clauses and functions in NRQL, the New Relic query language."redirects:- /docs/insights/using-nrql
The site runs an automatic job once a day to automatically translate changes to docs into target languages.
The site's frontend uses the doc's translation status information to display the SEO
hreflang element for a page. This tells search engines that the page also has a version available in the specific language.
<link rel="alternate" href="https://docs.newrelic.com/jp/" hreflang="ja" />
When you make changes to our English docs, you may get an unpaired translation error on GitHub. Here are scenarios where you would make changes to our i18n folder:
- When you delete an mdx file, delete the corresponding mdx file in the
/jp/folders. You do not update the yaml file.
- When you move an mdx file from folder X to folder Y, you need to move that same mdx file to folder Y in
/jp/. You do not update the yaml file.
- When you move an mdx file to a new folder, you need to create that new folder in
/jp/, then move the mdx file into it. You do not update the yaml file.
If you're uncertain about what you need to do when making changes to our i18n folder, you can run the i18n utility instead of manually deleting or moving files yourself.