Skip to content

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

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.

Sign up for GitHub

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

Merged
ArmandPhilippot merged 2 commits into from
Mar 24, 2026
+4 −2
Merged

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

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
1c0625a
i18n(fr): update `manual-setup.mdx`
ArmandPhilippot Mar 23, 2026
b1c44b4
Merge branch 'main' into i18n/fr-update-manual-setup
ArmandPhilippot Mar 24, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 4 additions & 2 deletions docs/src/content/docs/fr/manual-setup.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -77,8 +77,8 @@ export const collections = {
};
```

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

@HiDeoo HiDeoo Mar 24, 2026

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

@ArmandPhilippot ArmandPhilippot Mar 24, 2026

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

@HiDeoo HiDeoo Mar 24, 2026

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

@ArmandPhilippot ArmandPhilippot Mar 24, 2026

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


### Ajouter du contenu

Expand Down Expand Up @@ -132,3 +132,5 @@ import { FileTree } from '@astrojs/starlight/components';
Pour activer le SSR, suivez le guide [« Adaptateurs de rendu à la demande »](https://docs.astro.build/fr/guides/on-demand-rendering/) dans la documentation d'Astro pour ajouter un adaptateur serveur à votre projet Starlight.

Les pages de documentation générées par Starlight sont pré-rendues par défaut, quel que soit le mode de rendu de votre projet. Pour désactiver le pré-rendu de vos pages Starlight, définissez [l'option de configuration `prerender`](/fr/reference/configuration/#prerender) à `false`.

Si vous utilisez l'[adaptateur Cloudflare](https://docs.astro.build/fr/guides/integrations-guide/cloudflare/) pour activer le rendu côté serveur dans votre projet de documentation, assurez-vous d'[ajouter également l'option de compatibilité `nodejs_compat` à votre fichier de configuration Wrangler](https://developers.cloudflare.com/workers/runtime-apis/nodejs/#get-started).
Loading