Skip to content

i18n(fr): update manual-setup.mdx#3772

Merged
ArmandPhilippot merged 2 commits intowithastro:mainfrom
ArmandPhilippot:i18n/fr-update-manual-setup
Mar 24, 2026
Merged

i18n(fr): update manual-setup.mdx#3772
ArmandPhilippot merged 2 commits intowithastro:mainfrom
ArmandPhilippot:i18n/fr-update-manual-setup

Conversation

@ArmandPhilippot
Copy link
Copy Markdown
Member

Description

Adds changes from #3644 to the French translation of manual-setup.mdx.

@netlify
Copy link
Copy Markdown

netlify bot commented Mar 23, 2026

Deploy Preview for astro-starlight ready!

Name Link
🔨 Latest commit b1c44b4
🔍 Latest deploy log https://app.netlify.com/projects/astro-starlight/deploys/69c2936a3dcf97000812b332
😎 Deploy Preview https://deploy-preview-3772--astro-starlight.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.
Lighthouse
Lighthouse
1 paths audited
Performance: 100 (no change from production)
Accessibility: 100 (no change from production)
Best Practices: 100 (no change from production)
SEO: 100 (no change from production)
PWA: -
View the detailed breakdown and full score reports

To edit notification comments on pull requests, go to your Netlify project configuration.

@changeset-bot
Copy link
Copy Markdown

changeset-bot bot commented Mar 23, 2026

⚠️ No Changeset found

Latest commit: b1c44b4

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

@github-actions github-actions bot added i18n Anything to do with internationalization & translation efforts 📚 docs Documentation website changes labels Mar 23, 2026
@astrobot-houston
Copy link
Copy Markdown
Contributor

astrobot-houston commented Mar 23, 2026

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

Locale File Note
fr manual-setup.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.

Copy link
Copy Markdown
Member

@HiDeoo HiDeoo left a comment

Choose a reason for hiding this comment

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

Left a tiny question, but otherwise looks perfect to me as usual 🙌

Starlight est également compatible avec [l'option `legacy.collections`](https://docs.astro.build/fr/reference/legacy-flags/) où les collections sont gérées en utilisant l'implémentation de collections de contenu héritée.
Celà est utile si vous avez un projet Astro existant et que vous ne pouvez pas apporter de modifications aux collections pour utiliser un chargeur.
Starlight est également compatible avec [l'option `legacy.collectionsBackwardsCompat`](https://docs.astro.build/fr/reference/legacy-flags/#collectionsbackwardscompat) qui préserve certaines fonctionnalités héritées des collections de contenu de la v4.
Celà est utile si vous avez un projet Astro existant et que vous ne pouvez pas apporter de modifications aux collections pour le moment afin de migrer vers l'API de couche de contenu introduite dans la v5.0.
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.

Q: should we use the same as in Astro Docs, e.g. l’API Content Layer?

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.

Ah, I thought this was translated everywhere... I probably rushed this translation. Too tiny. 😅

I checked the Astro Docs repo locally, and it seems this is the only page where we use "Content Layer". The other pages (e.g. Content Loader Reference or Content Collections use "couche de contenu"). This is also what the i18n guide suggests.

So, I'd say we keep the translation and I'll update the Astro Docs file to also use the translated version?

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.

Oh, perfect, ignore me then. I just remembered seeing this translation here and assumed it was the one used everywhere 🙈

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.

Astro Docs PR ready withastro/docs#13582

I hadn't checked the Starlight repository! So, it seems we have 0 "couche de contenu" and two "Content Layer" in a card on Community content. Well, the card is pretty long already so I don't mind the inconsistency here... But, we could update that if we want. This doesn't seem to make the card bigger on desktop:

Screenshot of the updated card

@ArmandPhilippot ArmandPhilippot merged commit f8d15f3 into withastro:main Mar 24, 2026
16 checks passed
@ArmandPhilippot ArmandPhilippot deleted the i18n/fr-update-manual-setup branch March 24, 2026 13:41
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

📚 docs Documentation website changes i18n Anything to do with internationalization & translation efforts

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants