Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

i18n(zh-cn): Add flotiq.mdx #10090

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

i18n(zh-cn): Add flotiq.mdx #10090

wants to merge 1 commit into from

Conversation

Nin3lee
Copy link
Contributor

@Nin3lee Nin3lee commented Nov 22, 2024

Description (required)

Add flotiq.mdx

Related issues & labels (optional)

@github-actions github-actions bot added the i18n Anything to do with internationalization & translation efforts - ask @YanThomas for help! label Nov 22, 2024
Copy link

netlify bot commented Nov 22, 2024

Deploy Preview for astro-docs-2 ready!

Built without sensitive environment variables

Name Link
🔨 Latest commit d3fc3ed
🔍 Latest deploy log https://app.netlify.com/sites/astro-docs-2/deploys/67402d79a060ec00081a3ec4
😎 Deploy Preview https://deploy-preview-10090--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 configuration.

@astrobot-houston
Copy link
Contributor

Lunaria Status Overview

🌕 This pull request will trigger status changes.

Learn more

By default, every PR changing files present in the Lunaria configuration's files property will be considered and trigger status changes accordingly.

You can change this by adding one of the keywords present in the ignoreKeywords property in your Lunaria configuration file in the PR's title (ignoring all files) or by including a tracker directive in the merged commit's description.

Tracked Files

File Note
zh-cn/guides/cms/flotiq.mdx Localization added, will be marked as complete.
Warnings reference
Icon Description
🔄️ The source for this localization has been updated since the creation of this pull request, make sure all changes in the source have been applied.

@sarah11918
Copy link
Member

Just commenting for maintainers that my preference would be to change this to merge into next and see if it "just works" and if so, let's add it there.

If not, then I think this one new page should be fine to merge into v4 docs as it doesn't seem to contain any outdated links, or affect any existing pages.

@liruifengv
Copy link
Member

Just commenting for maintainers that my preference would be to change this to merge into next and see if it "just works" and if so, let's add it there.

If not, then I think this one new page should be fine to merge into v4 docs as it doesn't seem to contain any outdated links, or affect any existing pages.

I think we can wait V5 release. Then merge this PR.

Copy link
Member

@sarah11918 sarah11918 left a comment

Choose a reason for hiding this comment

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

OK! Just putting a block on this so it does not get accidentally merged into v4 docs.

See you in v5, @Nin3lee ! 😄

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
i18n Anything to do with internationalization & translation efforts - ask @YanThomas for help!
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants