i18n(fr): update guides/content-collections and related files

[ArmandPhilippot]

Description (required)

Adds changes from #12322, #13427, and #13435 to the French translation of guides/content-collections, modules/astro-content, content-loader-reference, and to the files that required a link update.

Note

integrations-reference.mdx is also updated in #13448 so we might have a Git conflict

Related issues & labels (optional)

• Suggested label: i18n

[netlify]

✅ Deploy Preview for astro-docs-2 ready!

Built without sensitive environment variables

Name	Link
🔨 Latest commit	33c91aa
🔍 Latest deploy log	https://app.netlify.com/projects/astro-docs-2/deploys/69b9bf2a5a1f8a0008d8b616
😎 Deploy Preview	https://deploy-preview-13431--astro-docs-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 project configuration.

[astrobot-houston]

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
fr/guides/cms/cloudcannon.mdx	Localization changed, will be marked as complete.
fr/guides/cms/keystatic.mdx	Localization changed, will be marked as complete.
fr/guides/content-collections.mdx	Localization changed, will be marked as complete.
fr/guides/integrations-guide/markdoc.mdx	Localization changed, will be marked as complete.
fr/guides/integrations-guide/mdx.mdx	Localization changed, will be marked as complete.
fr/guides/markdown-content.mdx	Localization changed, will be marked as complete.
fr/guides/media/cloudinary.mdx	Localization changed, will be marked as complete.
fr/guides/migrate-to-astro/from-create-react-app.mdx	Localization changed, will be marked as complete.
fr/guides/migrate-to-astro/from-gatsby.mdx	Localization changed, will be marked as complete.
fr/guides/migrate-to-astro/from-nextjs.mdx	Localization changed, will be marked as complete.
fr/reference/content-loader-reference.mdx	Localization changed, will be marked as complete. 🔄️
fr/reference/errors/file-glob-not-supported.mdx	Localization changed, will be marked as complete.
fr/reference/errors/file-parser-not-found.mdx	Localization changed, will be marked as complete.
fr/reference/integrations-reference.mdx	Localization changed, will be marked as complete.
fr/reference/modules/astro-content.mdx	Localization changed, will be marked as complete.
fr/tutorial/6-islands/4.mdx	Localization changed, 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.

[ld-web]

That's clean ! Compared to the size of modifications I didn't have to comment or suggest that much modifications.

I hope it will help !

[ld-web]

That's clean ! Compared to the size of modifications I didn't have to comment or suggest that much modifications.

I hope it will help !

[ArmandPhilippot]

Thanks a lot for the review and the brainstorming, really helpful! 🙌🏽

I think I addressed all the feedback except the one to fix in the English version first. If the fix comes first, I'll apply it. If the approval comes first, we can fix that in a following PR!

[ld-web]

Nice ! I'll open a PR about the English version tonight then.

Thanks !

[ArmandPhilippot]

Thank you again, glad to have some help with all the v6 changes! 🙌🏽 And also, for your willingness to get involved and for being nitpicky with the wording (I like that)!

I'm taking this as an implicit approval because I followed each suggestions, but do not hesitate to check "Approve" in the "Files changed" tab.

For English docs (not just typo), we usually expect maintainers approval (even if regular contributors approval are always helpful, because this means someone already double-checked what is being sent).

But, for translations native speakers approvals are important. First, this is also a reassurance for the author of the PR (ie. did I misunderstood this or not). And mostly, if a maintainer speaking the language is not available, this gives a good clue for another maintainer this is ready and they can merge this (ie. they don't need to scroll to see the last comment, on desktop at least there is an indication in the sidebar).

This can be helpful when an English PR updating the same file is ready to be merged... maybe the approved translation should be merged first to avoid checking all the changes again. I'm thinking about this because the Cloudflare integration update is soon to be outdated. 😄

(Nothing wrong! Just trying to explain how we work and why explicit approvals are important for us 😉 )