Skip to content

Make more pages ready for translation#2855

Merged
Jutanium merged 9 commits into
mainfrom
yan/new-i18n-pages
Mar 16, 2023
Merged

Make more pages ready for translation#2855
Jutanium merged 9 commits into
mainfrom
yan/new-i18n-pages

Conversation

@yanthomasdev
Copy link
Copy Markdown
Member

@yanthomasdev yanthomasdev commented Mar 14, 2023

What kind of changes does this PR include?

  • New or updated content

Description

New 69 pages for our translators to enjoy! In this case, all the integrations, tutorial, CMS, and migration pages are now marked as i18nReady: true.

Preferably, we should merge #2852 before this one.

@netlify
Copy link
Copy Markdown

netlify Bot commented Mar 14, 2023

Deploy Preview for astro-docs-2 ready!

Name Link
🔨 Latest commit 59fcbad
🔍 Latest deploy log https://app.netlify.com/sites/astro-docs-2/deploys/641360bdeb34ef00071f83cc
😎 Deploy Preview https://deploy-preview-2855--astro-docs-2.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

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

@yanthomasdev yanthomasdev added the i18n Anything to do with internationalization & translation efforts - ask @YanThomas for help! label Mar 14, 2023
@github-actions github-actions Bot removed the i18n Anything to do with internationalization & translation efforts - ask @YanThomas for help! label Mar 14, 2023
Copy link
Copy Markdown
Member

@delucis delucis left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Impressive work here, @yan-thomas, thank you! Left one suggestion for the integration script.

Comment thread scripts/generate-integration-pages.ts Outdated
};

// Add pages titles that should be marked as `i18nReady: false` as part of this array.
const translationBlacklist: string[] = [];
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I’d suggest using “blocklist” instead of “blacklist” or a use-case specific name like i18nNotReadyIntegrations or something. We can also follow the same pattern as for #deprecatedIntegrations setting this inside IntegrationsPagesBuilder.

Maybe we want to block translation of Markdoc for now given it’s still very experimental?

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Fair points, I'll make these changes after arriving from college 🙌

@yanthomasdev
Copy link
Copy Markdown
Member Author

Done @delucis! Let me know if you have any other comments/suggestions 🙌

Copy link
Copy Markdown
Member

@dreyfus92 dreyfus92 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM! ✅ We need to start shipping new translations.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants