+
+# Community Team
+
+The Community Team is a wide-ranging team that is in charge of managing all Quilt community spaces, as well as its social media accounts and public relations tasks. Because this work varies a lot, the Community Team is split up into several sub-teams, which have specific responsibilities.
+
+## Keyholder
+
+The keyholder is a trusted community member who acts as the de-facto owner of Community Spaces that don't support shared ownership, such as Discord. They assist with server management when required by the platform, but are otherwise uninvolved in the Community Team.
+
+
+
+
+## Community Managers
+
+Community Managers are administrative Community Team members that deal with the day-to-day tasks of maintaining Quilt's community spaces, as well as supporting and managing the rest of the community team. They're responsible for properly running elections, interviewing and training new Community Team members, managing the structure of Quilt's community spaces, writing and receiving feedback on Quilt's community policies.
+
+
+
+
+
+## Moderators
+
+Quilt's Moderator team is responsible for daily moderation tasks in Quilt community spaces. This includes conflict resolution, defensive and reactive moderation tasks and general rule and policy enforcement. Moderators are the backbone of any Community Team, and Quilt's is no exception -- a diverse, active Moderator team has always been instrumental for Quilt's success.
+
+
+
+
+
+## Events Team
+
+The Events Team is responsible for organising and managing events within our community spaces, which can include anything from AMAs to fully-blown online modding conventions. While they aren't Moderators, they are always backed up by the rest of the Community Team, and also have the ability to directly moderate events.
+
+
+
+
+
+## Outreach Team
+
+The outreach team is responsible for communications outside of and within Quilt. They write blog posts, manage social media and website content, and run developer meetings, among other things.
+
+
+
+
+
+# Development Teams
+
+Development teams are responsible for specific parts of The Quilt Project, which itself comprises a number of projects. Developent teams operate largely independently, allowing for self-governance as long as the relevant RFCs are followed.
+
+## Build Tools
+
+The build tools team is responsible for several projects that are instrumental for creating Quilt mods, including compilation tooling and build system plugins. This team is responsible for the following projects:
+
+
+
+
+
+
+
+
+
+
+
+
+
+## Chasm
+
+The Chasm team is responsible for maintaining Chasm, the Collision Handling ASM toolset. Chasm aims to provide a safer backend for modifying JVM bytecode at runtime, allowing for more compatible mixins and extra bytecode modification frontends.
+
+**Note:** You may see projects with "ASMR" in the name on the QuiltMC GitHub organisation. This was the old, internal codename for Chasm, so those projects are associated with the Chasm team.
+
+This team is responsible for the following projects:
+
+
+
+
+
+
+
+
+
+
+## Community Tooling
+
+The Community Tooling team is responsible for projects that power Quilt's community spaces, such as custom Discord bots. This team is responsible for the following projects:
+
+
+
+
+
+
+
+
+
+## Infrastructure
+
+The Infrastructure team is responsible for Quilt's service infrastructure, including managing cloud platforms, server tooling, file repositories and API services for modders. This team is responsible for the following projects:
+
+
+
+
+
+
+
+
+
+
+
+## Kotlin
+
+The Kotlin Team is responsible for maintaining the Quilt Kotlin Libraries (QKL), a set of libraries based off QSL and designed for use with the Kotlin programming language. These libraries provide an official way to use Kotlin on Quilt, as well as wrappers for QSL and the Minecraft codebase for easier use in Kotlin.
+
+
+
+
+
+
+
+
+
+
+## Loader
+
+The Loader team is responsible for projects relating to Quilt Loader, the project that actually handles loading mods into the game. This also includes projects like the installer and libraries used for parsing and generating mod metadata. This team is responsible for the following projects:
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+## Mappings
+
+The Mappings team is responsible for projects relating to remapping obfuscated names to human-readable names. This includes tools for matching names, mappings storage formats, javadoc generation tools, and much more besides. This team is responsible for the following projects:
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+# Quilt Standard Libraries (QSL)
+
+The QSL team is responsible for maintaining a library of modules that provide extra APIs for modders to use when creating their mods. These APIs are designed to make certain tasks easier, and to help mods remain compatible with each other.
+
+The QSL team contains a subteam responsible for the Quilted Fabric API compatibility module.
+
+This team is responsible for the following projects:
+
+
+
+
+
+
+
+
+
+
+## Sub-Team: Quilted Fabric API
+
+
+
+
+
+# Triage Teams
+
+Triage teams aren't directly involved with development, but they're still very important. They're mostly responsible for reviewing pull requests to active Quilt repositories, ensuring that they're up to spec and ready be merged. This allows for the development teams overseeing these repositories to focus on development, rather than reviewing PRs.
+
+## Mappings
+
+This team is responsible for handling triage tasks for the following projects:
+
+
+
+
+
+
+
+
+
diff --git a/src/pages/fr/about/timeline.mdx b/src/pages/fr/about/timeline.mdx
new file mode 100644
index 000000000..5e47a64aa
--- /dev/null
+++ b/src/pages/fr/about/timeline.mdx
@@ -0,0 +1,105 @@
+---
+title: Chronologie
+description: La chronologie officielle de Quilt - du début à aujourd'hui.
+layout: /src/layouts/Page.astro
+---
+
+import Header from "@parts/timeline/Header.astro";
+import Item from "@parts/timeline/Item.astro";
+import rtlSettings from "@data/RtlSettings";
+
+import site from "@data/Site";
+
+
+ 2021
+
+
+ Le serveur Discord de l'initiative Quilt est créé, comme un lieu temporaire pour mettre en place un plan initial pour le projet Quilt.
+
+
+
+
+
+ i509VCB présente le serveur de l'initiative à ses premiers membres
+
+
+
+
+
+ Le serveur Discord de la communauté Quilt est créé, afin de fournir un espace communautaire officiel et public. Pendant que les choses sont encore en train d'être mises en place et planifiées, des invitations à usage unique sont distribuées à des membres de confiance et éminents de la communauté Fabric -- le serveur n'est pas rendu public immédiatement.
+
+
+ Pour susciter l'intérêt et savoir ce que la communauté des moddeurs pense de Quilt, l'un des membres fondateurs publie un [Pastebin "divulgué"](https://pastebin.com/spNgyCMD) sur un serveur de théâtre. Le document contient des informations sur la gouvernance et la politique de modération d'un nouveau projet nommé "Fabrique", un faux nom utilisé pour éviter de dévoiler les projets de Quilt avant qu'ils ne soient prêts à être rendus publics.
+
+
+
+
+
+ Le message qui relie le document Pastebin "divulgué".
+
+
+
+
+
+ L'organisation GitHub de Quilt a atteint la limite de minutes gratuites pour Github Actions, ce qui signifie que ses dépôts doivent être rendus publics. Il ne faut pas longtemps pour que les gens les trouvent !
+
+
+
+
+
+ i509VCB et Prospector parlent des personnes qui ont trouvé le fork du dépôt Loom.
+
+
+
+
+
+ Le serveur Discord de la communauté Quilt est officiellement rendu public, les invitations appropriées étant créées et distribuées. Près de 350 utilisateurs rejoignent le serveur en ce premier jour, ce qui est emblématique de l'intérêt des gens pour le projet et sa communauté.
+
+ Le même jour, le serveur Discord Quilt Toolchain est mis en place et ouvert au public. Ce serveur a été conçu pour les discussions sur le développement des projets, comme un endroit où les gens peuvent travailler ensemble sur Quilt et ses projets, et pour que tout le monde puisse avoir un aperçu des processus de développement de Quilt.
+
+
+
+
+
+ Earthcomputer et i509VCB partagent des "crabes de célébration" sur le nouveau serveur Toolchain
+
+
+
+
+
+ Sur le serveur communautaire, une partie de [skribbl.io](https://skribbl.io) a été jouée pour célébrer l'ouverture du serveur au public. Au cours de cette partie, un joueur a été chargé de dessiner une citrouille, et beaucoup de joueurs ont deviné "ananas". Ce dessin est rapidement devenu le préféré de la communauté, et Ananas était né - la première mascotte de la communauté de Quilt.
+
+
+
+
+
+ Les utilisateurs spamment la nouvelle émote Ananas
+
+
+
+
+
+ Quilt entre officiellement dans sa première version bêta ce jour, attirant un afflux de nouveaux utilisateurs et une quantité incroyable de soutien et de commentaires positifs. À la fin de la journée, Quilt chargeait joyeusement les mods Quilt et Fabric, et avait [mis en ligne QSL sur Modrinth](https://modrinth.com/mod/qsl).
+
+
+
+
+
+ Graphique des nouveaux arrivants sur le Discord du projet Quilt au moment de la sortie de la version bêta.
+
+
+
+
+
+ Quilt met officiellement fin au serveur Discord Toolchain, en fusionnant ses canaux avec le serveur Discord principal, anciennement le serveur communautaire - dans le but de rapprocher les développeurs des utilisateurs.
+
+ Ce serveur a été mis en lecture seule trois jours plus tard, mais il est toujours possible d'y accéder - au cas où quelqu'un aurait besoin de se référer à un sujet déjà évoqué.
+
+ Aujourd'hui
+
diff --git a/src/pages/fr/blog/2021-04-18-this-is-quilt.md b/src/pages/fr/blog/2021-04-18-this-is-quilt.md
new file mode 100644
index 000000000..f7d09e0e1
--- /dev/null
+++ b/src/pages/fr/blog/2021-04-18-this-is-quilt.md
@@ -0,0 +1,43 @@
+---
+title: "This is Quilt"
+date: 2021-04-20 9:00:00 -00:00
+authors:
+ - Haven King
+ - ToffeeMax
+layout: /src/layouts/Post.astro
+---
+
+This is the Quilt Project: An open, community-driven modding toolchain designed primarily for Minecraft. Quilt builds on many of the technologies developed by [the Fabric Project](https://fabricmc.net) and is designed to take what worked well and expand on it further.
+
+
+
+## Why the Fork?
+
+While the Fabric Project has made significant progress towards an open and advanced mod loader, it has recently slowed down in technical innovation and failed to address several organizational issues. There are a number of changes the Quilt Project will put into place in the future to differentiate ourselves:
+
+- Governmental Structure -- Quilt's organizational structure has been designed with openness in mind; no one person holds all the keys.
+- Separation of Concerns -- Those in charge of technical concerns should not be making important community decisions, and vice versa. Quilt's teams each control a very specific aspect of the project.
+- Quilt Loader Plugins -- Will allow other parties to change mod loading behavior in new and exciting ways.
+- Dependency Downloading -- Users will no longer have to download every single dependency for each of their mods.
+- Cleaner Bytecode Modifications -- A safe, deterministic alternative to "Mixin" or modifying bytecode by hand.
+- Faster Iteration & Experimentation -- The Quilt project aims to fail fast. We would rather try something and fix it then spend countless months debating whether to move forward with it in the first place.
+
+## Important Documents and RFCs
+
+Quilt makes use of a Request for Comment system to drive major organizational changes. The RFCs are designed to make clear what changes are on the horizon, allow for comment from the community and as a maintained location for how specific parts of The Quilt Project work (eg Governance).
+
+You can view these documents (accepted and not) via our [GitHub Repository](https://github.com/QuiltMC/rfcs); please use this space to submit new RFCs and comment on currently open ones.
+
+The process of RFCs is outlined in [RFC-0001](https://github.com/QuiltMC/rfcs/blob/master/structure/0001-rfc-process.md).
+
+## Who is involved?
+
+To view an approximate membership, our [GitHub organization](https://github.com/QuiltMC) is a good starting place. This list is not exhaustive as it may not include members who are part of the community team.
+
+## Can I mod on Fabric and Quilt?
+
+Fabric mods will be able to run on Quilt initially. There may be a point in the future where this is no longer possible.
+
+## I have more questions!
+
+We have written a FAQ which hopes to provide answers to some common questions. If something is not covered there, please ask on our [Discord](https://discord.quiltmc.org).
diff --git a/src/pages/fr/blog/2021-09-19-quilt-sept-update.md b/src/pages/fr/blog/2021-09-19-quilt-sept-update.md
new file mode 100644
index 000000000..78f6fcdfb
--- /dev/null
+++ b/src/pages/fr/blog/2021-09-19-quilt-sept-update.md
@@ -0,0 +1,94 @@
+---
+title: "Quilt September Update"
+date: 2021-09-19 15:00:00 -00:00
+authors:
+ - ToffeeMax
+layout: /src/layouts/Post.astro
+---
+
+It has been a few months since the last update on the Quilt Project.
+
+Quilt has progressed far since that initial "This is Quilt" blog with: new teams set up; several important RFCs being published and developments in many key areas.
+
+
+
+## Clean Room RFC-33
+
+[RFC-33 has been merged](https://github.com/QuiltMC/rfcs/blob/master/rfc/0033-quilt-mappings-and-clean-room.md). This RFC changes how Quilt is dealing with other mappings (such as MojMap, MCP and Yarn).
+
+Key Take-Aways:
+
+- Quilt's fork of Yarn will be renamed to "Quilt Mappings" (QM)
+- All restrictions on referencing mappings projects (other than Quilt Mappings) within Quilt's community and development spaces will be lifted
+
+The reasoning, possible outcomes, drawbacks and smaller changes are outlined further in the RFC document.
+
+### Quilt Mappings
+
+As noted above, Quilt Mappings (QM) exist and are open to contributions.
+
+## Quilt Standard Library (QSL)
+
+The Quilt Standard Library (Quilt's separation of the current Fabric API into distinct modules -- see [RFC-9](https://github.com/QuiltMC/rfcs/blob/master/rfc/0009-qsl-structure.md)), now has the resource loader and base (for events).
+
+We are looking for help testing the resource loader. This can be done by using the snapshot maven repo with `org.quiltmc.qsl.core:resource-loader:1.0.0-SNAPSHOT`.
+
+QSL is seeing new additions on top of the reorganization into modules.
+
+## Quilt Mod JSON
+
+The Quilt Mod JSON has now been mostly implemented. The design of this is outlined in [RFC-2](https://github.com/QuiltMC/rfcs/blob/master/specification/0002-quilt.mod.json.md).
+
+The majority of the work left is smooth out issues in the loader.
+
+## QuiltFlower
+
+QuiltFlower (Quilt's Fork/Maintained version of FernFlower/ForgeFlower) has seen some smaller changes.
+
+These changes should make de-complied code more readable. An example of this can be seen in the following images:
+
+**Output produced by FabricFlower**
+
+
+**Same output, produced using QuiltFlower**
+
+
+## New Moderators
+
+Quilt's community spaces are always looking for new moderators. If you think you'd be a good fit and like to be involved, you can submit an application via ModMail.
+
+Some key documents to be aware of **before** applying:
+
+- [The Quilt Code of Conduct](https://quiltmc.org/community/code-of-conduct.html)
+- [Quilt's Rules](https://quiltmc.org/community/rules.html)
+- [Our Moderation Ethos](https://quiltmc.org/community/moderation.html)
+- [RFC-7 (The Community Team Structure)](https://github.com/QuiltMC/rfcs/blob/master/structure/0007-community-team.md)
+
+If the qualities outlined in the above documents, seem like you... please step forward and apply. The interview process will follow the steps outlined in RFC-7 (TL;DR):
+
+- Apply Via ModMail
+- Interview with a Community Manager (and the wider Community Team)
+- Community team holds a vote based on the interview
+- Result of the vote given to interviewee, and if successful the applicant will become a Trainee Moderator
+
+## Modding with Quilt & Fabric
+
+### Can I mod with Quilt at the moment?
+
+It is currently not possible to mod with the Quilt framework.
+
+However, progress has been made. We are currently waiting on a Gradle Plugin.
+
+**We are looking for contributors.** If you would like to help out with this part of the project, please reach out in [#build-tools-general](https://canary.discord.com/channels/833872081585700874/884090296068091965/885866814410723358) and express interest. A member of the relevant team will reach out.
+
+### Are things still compatible with Fabric?
+
+Things are largely compatible with loading mods.
+
+Mixin Plugins may not be possible to maintain compatibility. We may consider contributing to some mods that use them, to aid in replacing them.
+
+## Round-off
+
+That is all for now! When there are more things to talk about, they will be published here; for more bleeding edge changes and updates on the project, follow along on our [Discords](https://discord.quiltmc.org).
+
+Thank-you to the Quilt Project's team for helping flesh this out; it would have otherwise been just an update on moderators.
diff --git a/src/pages/fr/blog/2021-11-10-quilt-oct-update.md b/src/pages/fr/blog/2021-11-10-quilt-oct-update.md
new file mode 100644
index 000000000..04fc803e6
--- /dev/null
+++ b/src/pages/fr/blog/2021-11-10-quilt-oct-update.md
@@ -0,0 +1,79 @@
+---
+title: "Quilt's (VERY LATE) October Update"
+date: 2021-11-10 14:00:00 -00:00
+authors:
+ - ToffeeMax
+layout: /src/layouts/Post.astro
+---
+
+It is now _well_ past the End of October and closer to Halloween then I'd like to admit. Here is some of the more fleshed out updates about the Quilt Project:
+
+
+
+## Quilt Mappings are now usable in Loom!
+
+Have you wanted to use mappings other than Yarn or MojMap?
+
+Quilt Mappings is a Yarn derivative that allows inspiration from MojMap. This allows for Quilt Mappings to map the obscure constants in Minecraft code and more.
+
+However, this can mean that Quilt Mappings maybe be different from Yarn.
+
+[The provided gradle plugin](https://github.com/OroArmor/quilt-mappings-on-loom) allows Quilt Mappings to be used in Loom and Fabric environments. Currently, it is 1.17.1+ only; with no plans of backporting to earlier versions.
+
+Benefits of Quilt Mappings:
+
+1. Faster turn around.
+ - For the past couple weeks, Quilt Mappings has been out before intermediary. While this doesn't help too much in loom, it is something to look forward to in the future.
+2. Consistent names.
+ - Quilt Mapping names are never mismatched, meaning you won't find issues where names swap between versions.
+3. Familiarity of Yarn with the completeness of MojMap.
+ - While not complete, Quilt Mappings has the goal of 100% mapping coverage for Minecraft. Any help toward this goal would be appreciated as well!
+
+### How to use Quilt Mapping (Gradle Plugin)
+
+How to use Quilt Mappings:
+
+#### settings.gradle
+
+```groovy
+pluginManagement {
+ repositories {
+ maven { url = "https://maven.oroarmor.com" }
+ }
+}
+```
+
+#### build.gradle
+
+```groovy
+plugins {
+ // ...
+ id "quilt-mappings-on-loom" version "2.0.0"
+}
+
+// ...
+
+dependencies {
+ mappings(loom.layered {
+ addLayer(quiltmappings.mappings("org.quiltmc:quilt-mappings:${minecraft_version}+build.${project.quilt_mappings}:v2", true))
+ })
+}
+```
+
+## New Moderators
+
+Quilt's community spaces are always looking for new moderators. If you think you'd be a good fit and like to be involved, you can submit an application via ModMail.
+
+Some key documents to be aware of **before** applying:
+
+- [The Quilt Code of Conduct](https://quiltmc.org/community/code-of-conduct.html)
+- [Quilt's Rules](https://quiltmc.org/community/rules.html)
+- [Our Moderation Ethos](https://quiltmc.org/community/moderation.html)
+- [RFC-7 (The Community Team Structure)](https://github.com/QuiltMC/rfcs/blob/master/structure/0007-community-team.md)
+
+If the qualities outlined in the above documents, seem like you... please step forward and apply. The interview proccess will follow the steps outlined in RFC-7 (TL;DR):
+
+- Apply Via ModMail
+- Interview with a Community Manager (and the wider Community Team)
+- Community team holds a vote based on the interview
+- Result of the vote given to interviewee, and if successful the applicant will become a Trainee Moderator
diff --git a/src/pages/fr/blog/2022-03-22-quilt-enters-beta.md b/src/pages/fr/blog/2022-03-22-quilt-enters-beta.md
new file mode 100644
index 000000000..3ee0854a7
--- /dev/null
+++ b/src/pages/fr/blog/2022-03-22-quilt-enters-beta.md
@@ -0,0 +1,56 @@
+---
+title: Quilt enters Beta
+date: 2022-03-22 5:30:00 -00:00
+authors:
+ - Southpaw1496
+layout: /src/layouts/Post.astro
+---
+
+In February's final bi-weekly developer meeting (which you can listen to [as a podcast](https://anchor.fm/quiltmc-dev-meetings)), an exciting announcement was made: **Quilt is releasing its first beta on April 20th, 2022**.
+
+
+
+It's a huge milestone in our development process, and we could never have done it without our [incredible teams](https://quiltmc.org/about/teams) and supporting community.
+
+It is important to remember that this is a **beta**, not a full release. Beta software is intended for testing, ironing out issues and having space to develop features ahead of a full release. This means that a beta release will have some features missing, and may be unstable.
+
+## Instability
+
+Beta software is inherently unstable. This means that there could be a lot of bugs and crashes, but it also means that _anything could change at any time, with no regard for compatibility between one version and the next._
+
+It may be frustrating, but trying different approaches and iterating is an essential part of our development, and during this pre-release stage it is essential to not be held back by backwards compatibility.
+
+## Missing Features
+
+Beta software is also generally missing features that will be included in the full release, and Quilt is no exception. All our projects are at a stage where we feel that they are usable, but most of them are still missing features that will be included in the final release. Namely:
+
+- Mods will be built using a fork of Fabric's Loom with Intermediary, instead of Quilt-Gradle with Hashed MojMap.
+- The Chasm bytecode transformer is not yet ready for use and will not be available.
+- Loader plugins will not exist.
+- QSL (Quilt Standard Libraries) will not be automatically downloaded as a dependency.
+- Many QSL Modules will not be available to use.
+
+## Why we're releasing now
+
+To address the elephant in the room, we're not releasing Quilt on 4/20 for the memes. April 20th is actually the one-year anniversary of the Community Discord server, a very significant event in Quilt's history. Besides this, we're releasing our tools in an unfinished state for two reasons:
+
+- Quilt is relatively unknown outside its community, and we hope that by showing that Quilt is more than just an idea, the project will gain some traction, and start being taken more seriously by people in the modding sphere.
+- Both our developers and our (future) users are very important to us, and we want your feedback and ideas on how to improve what we've made, while we still have the flexibility of being in the development stage to change and break things, without having to worry about backwards compatibility.
+
+## Stay in the Know
+
+While we are currently confident that we can make the April 20th target, the truth is that software development is often unpredictable, and estimates aren't always representative of when a target is met. If you want to stay up-to-date with developments, we recommend joining our [Community Discord Server](https://discord.quiltmc.org), and/or [following us on Twitter](https://twitter.com/Quilt_MC).
+
+You can even [subscribe to this blog via RSS](https://quiltmc.org/feed.xml) and get updates delivered straight to your RSS reader of choice.
+
+We also hold a Public Developer Meeting on the [Toolchain Discord Server](https://discord.quiltmc.org/toolchain) every second Saturday at 5PM UTC, where the teams get together and discuss the progress made on their respective projects, and also answer questions from the community. Even though it's called a Developer meeting, anyone interested in Quilt's future development is welcome.
+
+## Get Involved
+
+If you want to get involved, we could always use some extra help. A list of current openings for positions on our various teams can be found on the [Openings page](https://quiltmc.org/openings), but if none of them speak to you, or if you want to contribute without joining a team, the best thing to do is to join the [Toolchain Discord Server](https://discord.quiltmc.org/toolchain) and offer your expertise.
+
+## Conclusion
+
+We'd like to thank everyone who has come with us on the journey so far, including our developers and our wonderful community. This is Quilt's biggest step since we ran out of GitHub Actions minutes and had to go public, and we never could've done it without all of you.
+
+Quilt is closer than ever, and we can't wait.
diff --git a/src/pages/fr/blog/2022-03-29-introducing-blanketcon.md b/src/pages/fr/blog/2022-03-29-introducing-blanketcon.md
new file mode 100644
index 000000000..0e29afcb0
--- /dev/null
+++ b/src/pages/fr/blog/2022-03-29-introducing-blanketcon.md
@@ -0,0 +1,17 @@
+---
+title: Introducing BlanketCon!
+date: 2022-03-29 7:00:00 -00:00
+authors:
+ - LemmaEOF
+layout: /src/layouts/Post.astro
+---
+
+Heya! Lemma here to announce a big project we've been working on for a while now! From May 6th to May 7th this year, ModFest and Quilt are proud to be hosting **BlanketCon**, an in-game Minecraft modding convention powered by Quilt Loader! We'll be making a custom world where you can check out old favorites and newcomers alike! Come talk to devs and attend panels, keynotes, and more!
+
+
+
+If you're a Minecraft mod developer, **we want you here at BlanketCon**! Submit whatever mods you'd like to feature in the con; size or poularity doesn't matter! The server will be running on the Quilt Loader beta, with support for both Fabric and Quilt mods, but if you develop for Forge, Sponge, Paper, or any other modding framework, you're still more than welcome to hold an event - despite being Quilt-run, we want this to be a celebration of Minecraft modding as a whole! You can apply to host a booth or an at-con event at [https://blanketcon.modfest.net/signup/](https://blanketcon.modfest.net/signup)!
+
+The con server will open on May 5th at 6 PM UTC, with the opening ceremony beginning an hour later! You can see the full schedule as it's created, as well as all confirmed booths on the BlanketCon site at [blanketcon.modfest.net](https://blanketcon.modfest.net)!
+
+If you have any questions, please don't hesitate to ask in the [ModFest](https://discord.gg/gn543Ee) or [Quilt](https://discord.quiltmc.org) discords! I hope to see you all there!
diff --git a/src/pages/fr/blog/2022-05-07-announcing-quilt-forum.md b/src/pages/fr/blog/2022-05-07-announcing-quilt-forum.md
new file mode 100644
index 000000000..6fd146308
--- /dev/null
+++ b/src/pages/fr/blog/2022-05-07-announcing-quilt-forum.md
@@ -0,0 +1,37 @@
+---
+title: Announcing the Quilt Forum
+date: 2022-05-07 4:30:00 -00:00
+authors:
+ - Southpaw1496
+layout: /src/layouts/Post.astro
+---
+
+Hey everyone! I and the rest of the Community Team are excited to announce the final result of just over six months of planning, development, and a not insignificant amount of DevOps headaches. Namely, Quilt's new community space, **the official Quilt Forum**. The forum is being hosted and kindly sponsored by Starchild and their upcoming startup, Starchild Systems.
+
+
+
+You may have some questions about why we've launched a forum, and what will happen to our existing Discord spaces, but before we answer those, let's get one universal question out the way:
+
+## Where do I sign up?
+
+The forum is live now at [https://forum.quiltmc.org](https://forum.quiltmc.org), and you can sign up with a standard email and password, or using GitHub or Discord OAuth. Please make sure to read our [Privacy Policy](https://forum.quiltmc.org/privacy) if you have questions or concerns about how your data is handled and managed.
+
+With that out of the way, let's address some other common questions.
+
+## Why do we need a forum?
+
+Currently, our primary community space is the official [Quilt Community Discord](https://discord.quiltmc.org), and while it is very good for short-form discussions and has served us well, a forum provides two distinct advantages over Discord: **Openness**, and **Control**.
+
+### Openness
+
+One major problem with Discord is that it is a closed platform. To read the announcements and discussions we have in the Discord, you need to have a Discord account, and you need to explicitly join the server. This creates a barrier to entry for those wishing to learn more about Quilt and see what we're doing beyond what's on the website, which many people won't bother to pass. With a forum, while you still need an account to participate in discussion, if you're just looking, you can just visit it. There's no form to fill out, no password to create. A forum will also be indexed by search engines, meaning that any discussions or support requests can easily be found by future modders with a quick search query.
+
+### Control
+
+The other major advantage that a forum has over Discord is that it is fully owned and operated by us. Currently, if Discord goes down, we'd all be completely unable to communicate, but having a forum provides a backup place to use if this happens (and it works the other way around too). As well as this, Discord might someday change in a way that make it unsuitable for us to use, or it could even go out of business entirely, but a forum that is controlled by Quilt will exist as long as Quilt does. Even if Starchild Systems becomes unable to sponsor or host us in the future, we'll still be able to pack the forum up and move it elsewhere, while still preserving its community and discussion history.
+
+## What will happen to Discord?
+
+Not all that much. We'll link up some channels to feeds from the forum so that you can keep track of what's happening over there, but we have no plans to replace or otherwise deprecate Discord in favour of a forum. Discord is great for hanging out and having easy, short-form discussions, and it's still our main community space, something which we don't expect will change any time soon. Our Discord spaces will remain the active and cared-for places they are today, but the forum will also be available for those who prefer to use it.
+
+So what are you waiting for? Head over to [https://forum.quiltmc.org](https://forum.quiltmc.org) and join in the fun! Unless you don't want to, I suppose?
diff --git a/src/pages/fr/blog/2022-10-02-october-month-of-the-toberfests.md b/src/pages/fr/blog/2022-10-02-october-month-of-the-toberfests.md
new file mode 100644
index 000000000..7dfa59da9
--- /dev/null
+++ b/src/pages/fr/blog/2022-10-02-october-month-of-the-toberfests.md
@@ -0,0 +1,29 @@
+---
+title: "October: Month of the 'toberfests"
+date: 2022-10-02 19:20:00 -00:00
+authors:
+ - Southpaw1496
+layout: /src/layouts/Post.astro
+---
+
+October is most well known as a month of spookiness, of sugary treats, and of pumpkins (Pineapples, excuse me). But for developers, October is also a month of what I like to call "'toberfests", and today we're excited to announce that Quilt will be participating in two of them: Hacktoberfest and Modtoberfest.
+
+
+
+## But what **are** 'toberfests?
+Aside from the German beer festival Oktoberfest, the original and most famous 'toberfest is [Hacktoberfest](https://hacktoberfest.com). Began by Digital Ocean in 2013, Hacktoberfest is, at it's core, a challenge: during the month of October, you must contribute to four participating open-source projects, and the first 40,000 to complete the challenge get a choice of either a t-shirt or a tree planted in your name.
+
+Inspired by Hacktoberfest, several other groups have held smaller challenges, usually focused on a specific type of project. One of these, which this year Quilt is proud to be sponsoring, is [Modtoberfest](https://modtoberfest.com/), which focuses on contributions to the Minecraft community. While the prizes might not get you the street cred of a Hacktoberfest t-shirt, a tree will be planted for every accepted pull request, and if you submit four accepted pull requests, you will receive a sticker pack containing, among other things, something that no-one else will have: the world's **first** tangible Pineapple. Behold it in all its fruity glory!
+
+
+
+You also get a Quilt logo sticker, a Modfest sticker, a BlanketCon 2022 and some others, to complete the collection.
+
+
+
+## How do I start?
+You can start by going to [https://hacktoberfest.com](https://hacktoberfest.com) and/or [https://modtoberfest.com/](https://modtoberfest.com/) and signing up. From there, all you need to do is find a participating project, see what you can contribute, and start coding!
+
+We have a full page with [guidelines for making contributions to Quilt specifically](https://quiltmc.org/en/toberfests), but a word of advice: maintainers of the projects you contribute to have to officially accept the pull requests that you open in order for it to contribute to your total, and most of them will only accept ones that are high-quality and show effort put in for its own sake, not tiny changes that are clearly made in pursuit of a t-shirt (or the opportunity to be able to hold a Pineapple in one's hands): your contributions should be made with love and genuinely benefit the project that you're submitting to. Make sure to discuss any changes you want to make with the project's maintainers before contributing, and make sure to follow the project's contribution guidelines from the start to minimize their workload in the review phase, and maximize your chances of getting accepted.
+
+Happy hacking!
\ No newline at end of file
diff --git a/src/pages/fr/blog/2022-11-27-adding-cloudflare-analytics.md b/src/pages/fr/blog/2022-11-27-adding-cloudflare-analytics.md
new file mode 100644
index 000000000..25e6d2d44
--- /dev/null
+++ b/src/pages/fr/blog/2022-11-27-adding-cloudflare-analytics.md
@@ -0,0 +1,56 @@
+---
+title: "Adding Cloudflare Web Analytics to quiltmc.org"
+date: 2022-11-26 23:45:00 -00:00
+authors:
+ - Southpaw1496
+layout: /src/layouts/Post.astro
+---
+Today, we're adding the Cloudflare Web Analytics to quiltmc.org. We know that analytics tools have a reputation of being both greedy and careless with user data, and that some people might feel that we're putting meaningless numbers before their privacy, which, given the general perception of web analytics, is not an unfair assumption. However, we have put thought and care into the decision, and so this article explains what data is collected, how we could use it, and how we collect it without impacting your privacy.
+
+
+
+#### Contents:
+- [Contents:](#contents)
+- [Analytics and Privacy](#analytics-and-privacy)
+- [What Data Is Collected](#what-data-is-collected)
+- [How We Could Use the Data](#how-we-could-use-the-data)
+- [Why Cloudflare?](#why-cloudflare)
+
+
+## Analytics and Privacy
+Analytics tools are not exactly known for their focus on user privacy. This is because the most well-known analytics tools are run by advertising companies, most notably Google Analytics, [which has an 85% market share in the analytics business, and is installed on over 55% of all websites](https://w3techs.com/technologies/overview/traffic_analysis). As well as collecting analytics for the website owner to use, these tools use various technologies (like cookies or local browser storage) to associate users with a central identity. Then, when a user visits a website, they log that user as having visited it to a central database.
+
+While knowing that a user visited a single website isn't very useful, if an analytics tool is installed on lots of websites (like how Google Analytics is on 55% of the web), it can get pretty accurate data of what websites a person is visiting and what they're doing there, which can then be used to target ads to them. The website owner essentially makes a deal with the analytics tool vendor: The vendor will provide collect and store the analytics data for free, and in return, they get to watch every user visiting your site, and use the data for whatever they want. This is a great deal for both the vendor and the website operator, but not so much for the website's users, and as a community-focused product, a deal that benefits us but hurts our users is not one that Quilt is willing to make. Fortunately, there is a better way.
+
+In more recent years, spurred on by the advent of the GDPR and similar privacy laws, many companies have developed more privacy-focused analytics products, one of which is Cloudflare Web Analytics. While there are many similar products available, we'll be talking about it specifically, since it's what we're using for quiltmc.org. Critically,[ it doesn't use cookies, local storage, fingerprinting, or any other technologies to associate you with an identity](https://www.cloudflare.com/en-gb/web-analytics/), which means **it cannot track you around the web**. This means we won't need to ask you to consent to cookies when you visit our site (even though it would be a great opportunity to make a drawing of Cozy nomming a cookie), because we still don't use any.
+
+## What Data Is Collected
+The following list are the main things tracked by Cloudflare Web Analytics. It's important to remember that because Cloudflare doesn't log your IP address or use any other fingerprinting technologies, it's impossible to associate any of this data with any specific person or group. If we looked at site visitor metrics, for example, we wouldn't be able to see who those visitors were, or what each one of them did; only that some people visited some pages, and some people visited others.
+
+Cloudflare Web Analytics collects:
+- **Visits:** When someone visits a page from an external or direct link, rather than an internal link in another part of the website.
+- **Page Views:** When someone successfully loads an HTML page on the website.
+- **[Core Web Vitals](https://www.cloudflare.com/en-gb/learning/performance/what-are-core-web-vitals/):** Performance metrics reported by most Chromium-based browsers and used in Google's search rank algorithms
+- **Country:** What country someone visits from, based on their IP address.
+- **Referrer:** What website a person came from.
+- **Device Type:** The type of device a person visited with: desktop, mobile, or tablet.
+- **Browser:** The browser a person used when they visited.
+- **Operating System**: What operating system the person used when they visited.
+- **Page Load Time**: How long each stage of page loading took.
+
+Additionally, Cloudflare Web Analytics [is fully GDPR-compliant](https://www.cloudflare.com/en-gb/gdpr/introduction/) and doesn't collect any information classed as Personally Identifiable Information (PII).
+
+## How We Could Use the Data
+Even though Cloudflare Web Analytics doesn't come with any privacy concerns, it does add complexity to the website that wouldn't be worth it if we just used the data it provides to make pretty graphs. However, there are real ways that we can use it to make the website better for the increasing number of people that visit it every day. Here are some examples:
+- The data about what countries our visitors are from will help us know which languages to prioritize for localization.
+- If we notice that a lot of visitors are coming from a particular social media post, video, or blog article, we can show it to the rest of our users as a way of saying thank you.
+- If we notice people with certain device types, operating systems, or browsers are having bad experiences (for example, slow page loads), we can look into optimizing the website for them so that they have a better experience.
+- If our Core Web Vital statistics are low for a large number of users, we can work on improving them to improve our SEO, since they are part of Google's search ranking algorithm.
+- If a page is loading slowly for a lot of people, we can see exactly which part of the process is getting stuck and fix it, without them having to go through filing a GitHub issue.
+
+As well as these more practical examples, there is another use for them, which is encouragement. Seeing Quilt's success in numbers, and how it's gradually growing and spreading through the web to more and more places, reminds us that what we're doing is in fact making an impact, even if it sometimes feels like Mojang breaks half our tooling every couple of minor releases. We know that our growth interests our community, too, and while it's not possible to make the analytics completely public, if all goes well we plan to write a series of blog articles every so often about the website's analytics, starting with December's analytics in January.
+
+## Why Cloudflare?
+Cloudflare has attracted a lot of controversy recently, most notably its initial refusal to stop providing service to the harassment forum Kiwi Farms, so it's not unreasonable to wonder why we're choosing to use their offering over one from another company. The reason is that almost all privacy-focused analytics tools are paid, since they can't fund themselves by selling or utilizing the user data they collect, while Cloudflare offers a generous free tier in the hope that you'll soon upgrade or try one of their paid products. There aren't any other really reputable companies offering good free tiers, and the tradeoffs of using Cloudflare do not outweigh the costs that would be incurred from going with someone else.
+
+I hope that after reading this article, your mind is at rest. As the world becomes increasingly chaotic in many respects, it's easy to think that we're going the same way as everyone else: launching something new without really thinking about it, and hurting our users in the process, but hopefully, you now understand the reasoning behind the decision. If you have any questions, you can visit `#discord-meta` in the [Community Discord Server](https://discord.quiltmc.org), or [the `Meta` section of the forum](https://forum.quiltmc.org/c/quilt/meta/).
diff --git a/src/pages/fr/blog/2023-02-04-five-installer-vulnerabilities.md b/src/pages/fr/blog/2023-02-04-five-installer-vulnerabilities.md
new file mode 100644
index 000000000..e429187b1
--- /dev/null
+++ b/src/pages/fr/blog/2023-02-04-five-installer-vulnerabilities.md
@@ -0,0 +1,136 @@
+---
+title: "Five vulnerabilities found in mrpack installer implementations"
+date: 2023-02-04 17:00:00 -00:00
+authors:
+ - Ambre Bertucci
+layout: /src/layouts/Post.astro
+---
+
+On Tuesday, 31st January, a member of the Quilt team discovered path traversal vulnerabilities in five different mrpack
+implementations, affecting MultiMC, PolyMC, Prism Launcher, ATLauncher and mrpack-install.
+
+This article serves as a write-up for the vulnerabilities, and the affected versions.
+
+
+
+# Affected software
+
+Below you can find a table detailing the affected and patched versions for each piece of software.
+
+| Software | Affected versions | Patched versions |
+|----------------|-------------------|------------------|
+| MultiMC | <= 0.6.16 | >= 0.7.0 |
+| PolyMC | <= 1.4.3 | >= 5.0 |
+| Prism Launcher | <= 6.1 | >= 6.2 ¹ |
+| ATLauncher | <= 3.4.26.0 | >= 3.4.27.0 |
+| mrpack-install | <= 0.16.2 | >= 0.16.3 |
+
+¹: version 6.2 of Prism Launcher contains a critical bug, we recommend installing 6.3.
+
+We recommend every user to upgrade to a patched version. If you can't, we recommend you to inspect any mrpack before
+installation.
+
+# Vulnerability details
+
+[mrpack](https://docs.modrinth.com/docs/modpacks/format_definition/) is a modpack format popularized by the [Modrinth®](https://modrinth.com)
+mod sharing platform.
+
+It allows modpack creators to define a [`files`](https://docs.modrinth.com/docs/modpacks/format_definition/#files) array
+to download various files, such as mods, during modpack installation. This can be open to path traversals by using
+an absolute path (if the implementation allows it) or relative directories (`/../`) to escape the installation
+folder and install a file in any directory the process has access to.
+
+# Attack vector
+
+While we recognize installing a modpack requires trust into the modpack maker once the modpack is run, we're of the
+opinion that installing a modpack shouldn't require trust. One scenario can also be imagined where one would install
+a suspicious modpack for checking its content, leading to infection in the process.
+
+Modrinth® confirmed they have checks in place preventing such a modpack from being installed, although this
+vulnerability still affects modpacks installed off-site.
+
+# Demonstration
+
+Below you can find some example `modrinth.index.json` files that once put into a mrpack would install a `pwned` binary
+inside the user PATH. They assume the relevant tool is installed at the default location, except for `mrpack-install`
+which will depend on the execution location.
+
+## MultiMC, PolyMC, Prism Launcher, mrpack-install
+
+```json
+{
+ "formatVersion": 1,
+ "game": "minecraft",
+ "versionId": "exploit-demo",
+ "name": "Exploit demo",
+ "files": [
+ {
+ "path": "..\\..\\..\\..\\..\\..\\..\\AppData\\Local\\Microsoft\\WindowsApps\\pwned.bat",
+ "hashes": {
+ "sha1": "f2f2afa63f7c46d966b460c6efa85505ec8e7d26",
+ "sha512": "88b0dfed128d1b1dac86ef825fad577bd2fe99d79a8eb73a826a6634e6d2edadfe2fd50aa69b1009c38c7f4d1bbdd7199e2425cf3035515a794646474b3b28e8"
+ },
+ "env": {
+ "client": "required",
+ "server": "required"
+ },
+ "downloads": [
+ "https://raw.githubusercontent.com/Akarys42/pwned/main/pwned.bat"
+ ],
+ "fileSize": 200
+ }
+ ],
+ "dependencies": {
+ "minecraft": "1.18.2"
+ }
+}
+```
+
+## ATLauncher
+
+```json
+{
+ "formatVersion": 1,
+ "game": "minecraft",
+ "versionId": "exploit-demo",
+ "name": "Exploit demo",
+ "files": [
+ {
+ "path": "../../../../Local/Microsoft/WindowsApps/pwned.bat",
+ "hashes": {
+ "sha1": "f2f2afa63f7c46d966b460c6efa85505ec8e7d26",
+ "sha512": "88b0dfed128d1b1dac86ef825fad577bd2fe99d79a8eb73a826a6634e6d2edadfe2fd50aa69b1009c38c7f4d1bbdd7199e2425cf3035515a794646474b3b28e8"
+ },
+ "env": {
+ "client": "required",
+ "server": "required"
+ },
+ "downloads": [
+ "https://raw.githubusercontent.com/Akarys42/pwned/main/pwned.bat"
+ ],
+ "fileSize": 200
+ }
+ ],
+ "dependencies": {
+ "minecraft": "1.18.2"
+ }
+}
+```
+
+# Advisories
+
+* MultiMC: none
+* PolyMC: [GHSA-3rfr-g9g9-7gx2](https://github.com/PolyMC/PolyMC/security/advisories/GHSA-3rfr-g9g9-7gx2)
+* Prism Launcher: [GHSA-wxgx-8v36-mj2m](https://github.com/PrismLauncher/PrismLauncher/security/advisories/GHSA-wxgx-8v36-mj2m)
+* ATLauncher: [GHSA-7cff-8xv4-mvx6](https://github.com/ATLauncher/ATLauncher/security/advisories/GHSA-7cff-8xv4-mvx6)
+* mrpack-install: [GHSA-r887-gfxh-m9rr](https://github.com/nothub/mrpack-install/security/advisories/GHSA-r887-gfxh-m9rr)
+
+# CVE entries
+
+At the time of publishing this article, CVE assignment is still pending.
+
+# Credits
+
+Vulnerability found and blog post written by Ambre Bertucci (Akarys)
+
+Research inspired by Silver
diff --git a/src/pages/fr/blog/2023-02-14-qfapi-call-for-contributors.md b/src/pages/fr/blog/2023-02-14-qfapi-call-for-contributors.md
new file mode 100644
index 000000000..d44e3860f
--- /dev/null
+++ b/src/pages/fr/blog/2023-02-14-qfapi-call-for-contributors.md
@@ -0,0 +1,26 @@
+---
+title: "Quilted Fabric API: A call for contributors"
+date: 2023-02-14 12:15:00 -00:00
+authors:
+ - Southpaw1496
+layout: /src/layouts/Post.astro
+---
+
+[Quilted Fabric API](https://github.com/quiltmc/quilted-fabric-api) is our fork of Fabric API which runs alongside QSL to ensure mods using the Fabric API can work on Quilt. Since almost all Fabric mods make use of the Fabric API in some way or another, it's a critical part of Quilt's compatibility with Fabric mods, but despite this, it is largely updated and maintained by a single person:
+
+
+
+
+
+She could really use some help, so if you are able and have the time to spare, it would be really cool (dare I say, based?) of you to come on down and give her a hand.
+
+## Do I need to join a team?
+Absolutely not! Although contributing is often linked to joining a team, we're actually very happy to accept external contributions as well. You mustn't feel like you need to commit to joining the team before helping, and it's generally better if we get to know you and your contributions a little before accepting you onto a team if you want to be on one eventually.
+
+## I don't feel like I know enough to contribute...
+Quilt is a big project, and you might think that it's deeply complicated and requires expert skill to contribute to, but as long as you have basic Java knowledge and are willing to learn, you can do lots of things that would be a big help to us. The more people that contribute, the faster development will progress, and the more viable it is for other developers to take breaks when they need so that they can keep doing their best work. Your help is valuable, even if you don't consider yourself a skilled programmer.
+
+## What can I do to help?
+We've created [a truckload of GitHub issues](https://github.com/quiltMC/quilted-fabric-api/issues) to get you started, so have a look and find something you think you can do. If you find something you want to take on, make sure to comment on the issue so that others know you're working on it and work doesn't get done twice. If you have any questions or would like to discuss changes that you're planning to make with the developers, come and join us on the [Toolchain Discord](https://discord.quiltmc.org/toolchain).
+
+Although this post is focused on Quilted Fabric API, we welcome contributions to all our projects, such as [Cozy](https://github.com/quiltmc/cozy-discord), [quiltmc.org](https://github.com/quiltmc/quiltmc.org), and [others](https://github.com/orgs/QuiltMC/repositories). Even if you can't code, you can still help in other ways, for example, by [translating the website into your language](https://github.com/QuiltMC/quiltmc.org/blob/stable/LOCALIZATION.md). Join the [Toolchain Discord](https://discord.quiltmc.org/toolchain) if you're interested!
diff --git a/src/pages/fr/blog/2023-04-26-the-statement.md b/src/pages/fr/blog/2023-04-26-the-statement.md
new file mode 100644
index 000000000..aa5e90a16
--- /dev/null
+++ b/src/pages/fr/blog/2023-04-26-the-statement.md
@@ -0,0 +1,519 @@
+---
+title: "The Statement"
+date: 2023-04-26 12:00:00 -00:00
+index: false
+authors:
+ - The Quilt Team
+layout: /src/layouts/Post.astro
+---
+
+
+# Preface
+
+On April 20th of 2023, the Keyholder of the Quilt project attempted a hostile takeover of the Community and Toolchain Discord servers, as well as the Quilt Community Collab program (QCC) server. This document serves as a write-up on the events that led to the attempted takeover, the takeover itself, and where we plan to go from here.
+
+This document _also_ exists to give background on our collaboration status with Forge. A dedicated statement was planned to be released prior to the takeover happening, but given they ended up heavily intertwined, they have both been merged into this one.
+
+The statement was written by more than 11 authors— please excuse us if you see discrepancies in writing styles.
+
+# Quilt Community Collab (QCC)
+
+Quilt Community Collab was created on November 2nd, 2021 as a continuation of a similar project that had been founded on March 1st of the same year. The program exists to provide tooling and a collaborative space for people running Minecraft-related communities to work together on moderation, community management and event planning.
+
+This collab program is occasionally misunderstood as a sort of "hit squad" attempting to "cancel" Minecraft community members and have them removed from as many servers as possible, largely due to rhetoric pushed by queerphobes, racists and other bigots that have been banned by communities taking part in the program. However, it does nothing of the sort — while communities there do occasionally mention bans that they've made, it primarily exists to support those communities in their community management work, on topics such as intersectionality, policy-writing and structural design. Even though bans can be shared there, other communities are not required to act, instead making their decision based on the provided evidence.
+
+The program was created by the Quilt Community Team, but it contains members from several other founding communities — one of which was Forge. Everyone involved saw this as a sign of good things to come; Forge has been well-known for its toxic community management practices over the years, and Forge taking part in the program was interpreted as a genuine dedication to solving those issues. This wasn't an entirely incorrect assumption, but only in a broad sense — a lot of the changes were surface-level, and didn't really address many of the deeper, more serious problems, as we'll see later.
+
+# External users involved
+
+## Kashike, aka The Keyholder
+
+Quilt, born from Fabric drama, has done its best to make sure no one person could take control of the server and become a dictator[\[1\]](#ref-1). For this reason, the Quilt initiative members created the role of the Keyholder, someone who is well-known in the Minecraft community while being totally uninvolved in the project. The keyholder was supposed to never intervene in the management of the project[\[2\]](#ref-2).
+
+Kashike was chosen to be the Quilt Keyholder by the founders of the project due to his involvement in various Minecraft projects, most of the time enacting this same role, or one with the same importance.[\[3\]](#ref-3)[\[4\]](#ref-4)
+
+IDs: `976461443580985425`, `105923848263753728`,[\[5\]](#ref-5) and `599644584611414033` (selfbot specific account, although his main has also been used to self bot)[\[6\]](#ref-6)
+
+## LexManos
+
+LexManos, or Lex for short, was the leader of the Forge project from its conception in 2011, to April 5th, 2023, when he stepped down as a result of the discovery of several transphobic tweets he liked on Twitter — more on that later. As an extremely prominent member of the Minecraft modding community, we believe he needs no further introduction.
+
+ID: `134030797756694528`
+
+## Curle (also Amethyst)
+
+Curle has been contributing to Forge for a few years, and has been informally holding management roles for a while now. While she is known for her poor moderation, such as repeatedly muting community members contacting the moderators, we didn't notice any overly problematic behavior up to that point.
+
+ID: `462617385157787648`
+
+## Larry
+
+Larry was part of the first wave of new moderators in Quilt. He joined on the day of opening, April 20th, 2021,[\[7\]](#ref-7) and applied for the position of Moderator on May 14th, 2021,[\[8\]](#ref-8) with only 11 messages on the server thus far[\[9\]](#ref-9). The first internal message in his application thread is a direct endorsement from Kashike: [\[10\]](#ref-10)
+
+> I can give a thumbs-up to Larry being someone trustworthy and good at moderation - I know him pretty well.
+
+This contradicts the first requirement to be a Keyholder, according to RFC 7[\[2\]](#ref-2):
+
+> Be able to show that they have no conflicting interests or personal wish to be in power
+
+Since then, over the span of two whole years, Larry sent only 524 messages in total in our community spaces, including internal channels — 477 messages on the community server, and 47 in the Toolchain server[\[12\]](#ref-12). For comparison, the median among the Community Team is 24,712, with the average being 45,620. For a more extreme comparison, the average message count, for every Discord member in the community server combined, is 1,038[\[13\]](#ref-13) — more than double of Larry's total.
+
+ID: `347959633518002177`
+
+## zml
+
+zml participated to Quilt's founding through the Initiative server. She is mostly known for her work at Sponge. This lead her to have privileged access to the internal channels.
+
+ID: `97139815404810240`
+
+# Staff members involved
+
+For context, here are the staff members involved:
+
+* levi (also levy, remote\_getaway): Moderator, Arab-South American PoC recently brought to the moderator team to help solve the longstanding lack of racial diversity in Quilt.
+* gdude: Moderator and Community Manager, white European who has worked in Quilt since its inception.
+* The Starchildren (also Hope, Akarys, Starchild): Community Manager and Administrative Board member, biracial European with a longstanding history with Quilt
+* Bubblie (also bubs): Community Team member, Indian-American PoC.
+* MrMangoHands (also mango): Community Manager and Administrative Board member, white US American, inactive for a few months and who was about to leave the staff team, holding a role similar to Keyholder in CaffeineMC.
+
+# Timeline
+
+* **February 2nd:** First report of Lex's transphobic Twitter likes.
+* **February 25th:** Curle discusses with Lex to "tone down the Twitter weirdness."
+* **April 1st:** Second report of Lex's transphobic Twitter likes.
+* **April 5th:** Curle tells QCC that she will be taking the lead on Forge.
+* **April 7th:** Curle shows the first draft of their statements, and after some discussion tells Levi to "take his victim complex to another thread."
+* **April 12th:** The beginning of Larry's demotion, marked by three events in quick succession:
+ * Larry espouses a racist viewpoint and argues against Levi in a ModMail thread, immediately after dismissing reports against someone who harbored ableist and Islamophobic views. Kashike then intercepts the argument and sides with Larry, his personal friend.
+ * A discussion is started in the `#admins` channel about starting a demotion against Larry, Kashike also joins this conversation.
+ * A suggestion of minimum activity requirement for Moderators, Community Managers and Admins is brought up again (previously shelved as no consensus was found). Larry somehow learns about messages from the `#admins` channel where the suggestion is discussed, which he is not supposed to be able to see, and uses it to push against the new policy.
+* **April 13th:** A demotion against Larry is started due to inactivity.
+* **April 15th:** After 8 days of silence from Forge, the process to remove Forge from the Collab program is started.
+* **April 17th:** Forge releases their statements. Noticing that Forge never addressed any feedback, the RFC that details the conditions of the voting process within QCC is simplified to make voting period end when the decision cannot be overturned, and the vote for Forge's removal passes. Forge is then removed from the program.
+* **April 18th:** Forge member looking to apply at Quilt retracts their application due to "concerning reports." zml additionally posts a statement in Toolchain then leaves.
+* **April 19th:** Larry posts a statement in both Community and Toolchain and leaves, somehow knowing about the demotion. Larry and zml reveal there is an active leaker who is conspiring with them.
+* **April 19th-20th:** Kashike kicks out all the Community Team and Administrative Board members and seizes control of the servers, before transferring them to MrMangoHands upon pressure. All CT and Admin Board positions are reinstated, and Kashike, Larry, and zml are all permanently banned from Quilt spaces due to their role in the hostile takeover.
+
+# Forge
+
+## First Lex Report
+
+On February 2nd, a thread was created on the QCC server titled "LexManos Twitter Activity", outlining how former Forge leader LexManos liked numerous transphobic tweets, by known bigoted accounts.[\[14\]](#ref-14). One Forge staffer answered that they wanted to wait for Curle to do anything. The thread had been bumped up on the 5th, 9th (with a ping), 12th, and 14th before getting another reply from the same staffer claiming that "Lex isn't a transphobe."[\[15\]](#ref-15)[\[16\]](#ref-16).
+
+Curle finally responded on the 25th of February, saying she spoke to Lex, who will "tone down the Twitter weirdness." When prompted back with the idea that keeping his transphobia quiet wasn't what was asked, Curle answered combatively stating it was "drunken nights" behaviour, and the likes were to "elicit a reaction"[\[17\]](#ref-17). No further action was taken by Forge.
+
+## Second Lex Report
+
+On April 1st, the thread was re-opened and many more transphobic and alt-right likes were found on Lex's public Twitter.[\[18\]](#ref-18)[\[19\]](#ref-19) Two server members, one from Quilt and one from another community, threatened to go public to make sure this behaviour was properly addressed[\[20\]](#ref-20).
+
+On the 3rd, Lex removed his likes from the tweets, which was followed by the Forge staffer mentioned previously saying Curle was pressured to leave the Forge project by her employers, who noticed Lex's problematic liked tweets, which is what finally drove her to act[\[21\]](#ref-21). Curle additionally tone-policed a member of the Quilt staff for "insulting" Lex by calling him a "man baby"[\[22\]](#ref-22).
+
+_It must be noted that Lex has openly stated that he "stands by everything \[he has\] ever 'liked' on social media."_[\[23\]](#ref-23)
+
+On the 5th, Curle revealed that she would be taking the lead on the Forge project. This change is welcomed by all present members, including the two members threatening to go public, telling Curle they would wait for the official statements from Forge, to avoid stressing out Forge members[\[24\]](#ref-24).
+
+## Feedback on the Forge Statements
+
+On the 7th, Curle posted a draft of the two statements made by Forge with the following foreword: [\[25\]](#ref-25)
+
+> This is from Lex (specifically, from a huge wall of text dump), but I've redone the phrasing extensively because as discussed... he has a significant issue with wording and getting his intentions across.
+
+The statements themselves didn't contain any disclosure of that information at the time.[\[26\]](#ref-26)
+
+Considering the misleading aspect of hiding the fact Lex's statement had been edited, a few members raised concerns about the idea of not knowing what the original statement contained.[\[27\]](#ref-27) It was found later that the statement was initially written in the third person and that some sentences were randomly added, reinforcing the idea that Lex never wrote the statement himself or even any first draft.[\[28\]](#ref-28) Concerns were also brought up with the "sorry we got caught" aspect of the statement[\[29\]](#ref-29).
+
+Levi was the first to raise those concerns, and as a member of the racial minorities targeted by Lex's likes, he expressed his desire to see the unmodified statement.[\[30\]](#ref-30) Curle responded that this attitude lacked "professionalism" (For more explanation about the racism behind this statement, please see the "[Professionalism and Racism](#professionalism-and-racism) section) and was "getting inflammatory".[\[31\]](#ref-31)
+
+Levi and another Quilt staff member left the conversation. After this, Bubblie, another person of colour in Quilt's Community Team, spoke about the recurrent issue of white people leaving conversations when people of colour mention racial issues, as well as constant issues with getting tone policed. Levi agreed, which caused Curle to send the following message: [\[32\]](#ref-32)
+
+> Why are you playing the race card all of a sudden? Take your victim complex to another thread please.
+
+We don't believe we need to explain how this is blatantly racist, but for the sake of explanations: People of colour are usually left to resolve issues they did not bring up or started, and this was simply a note taken on how the conversation had ended, nothing more than a passing comment. It was never pinned against Curle, but her immediate reaction to seeing people of colour complain about effort-in-labor bias was to say they had a "victim complex", thus posing their exhaustion as fake or an exaggeration.
+
+## DM hopping
+
+After walking out of the conversation without offering either an apology or an explanation for her comment, Curle went into Levi's DMs to offer an apology, and saying it should be “discussed directly”.[\[75\]](#ref-75)
+
+Levi invited Curle to say their piece, but mentioned that he did not want to engage in a discussion as there was nothing to debate about. Curle said she respected that decision, but then went on to lie on the “LexManos Twitter Activity” thread, saying her message had been “rejected”.[\[77\]](#ref-77)
+
+Curle then proceeded to complain to gdude, a white man, in DMs about being “highly concerned” with the behaviours Bubblie and Levi exhibited, claiming nobody was “willing to listen”, and that she believed if she expressed her concerns on them, she'd be labelled “a white supremacist”.[\[76\]](#ref-76)
+
+gdude repeatedly mentioned how Curle's venting and demands for clarification made him uncomfortable, and that he was not going to be speaking for people of colour. Curle, disregarding this, continued sending long paragraphs calling Levi “argumentative”, “inappropriate”, that his interpretation of her message as racist was “a conscious choice”, and ultimately putting the blame on him by saying he was “probing for that” to happen.
+
+Curle then claimed the moderation team was “reprehensible” for calling out her racist comment, but not calling Levi out on his tone. She states, again, that Bubblie and Levi are “unprofessional, directly accusatory and argumentative”, and that moderators have a conflict of interest for letting it happen.
+
+As this was happening, the “LexManos Twitter Activity” thread took a civil disobedience stance given the behaviour exhibited by Curle was heavily dismissive, stating that if she was not going to answer, continue eluding everyone's feedback and criticism, and lying about what her DMs stated, then the thread had no purpose, and they could go as off-topic as they wanted. This was agreed to by most participants of the thread.
+
+Curle, noticing this, goes on to complain in gdude's DMs once again, trying to pose the people of colour in the thread making reclaiming jokes as a bad thing, and calling the behaviour “wrong” and “disgusting”. We must highlight again that Curle is a white woman, and she has no say in or right to call out people of colour on how they approach reclamation.[\[76\]](#ref-76)
+
+She complains that no one reached out to her when she was “making a racist outburst, seemingly out of character”, again notes that Bubblie and Levi were being “aggressive”, “insensitive”, “unapologetic”, and are “unsuitable for the collab program”, then passively calls them “immature, insensitive, or unsuitable for reasonable conversation”. She states that her racism is just her “concerns and thoughts” being “twisted”, and “mental gymnastics”, and Bubblie and Levi are “explicitly searching for reasons to be hurt or insulted”.
+
+Curle then went on to face gdude with a questionnaire that goes as follows:
+
+* “Is levy's behaviour acceptable, in your opinion?”— The answer was just yes
+* Questioning why the thread was “not moderated”.— “it's civil disobedience”
+* Implying the moderation team has some sort of conflict of interest when it comes to “moderating levy and bubble's behaviour”— The answer is no.
+* Questioning why no one reached out to her after her racist statement.— “there is no context that would make that statement OK”. Curle pushes this topic, saying “it can be completely out of line and still have reasons, intents, history, and emotion behind it”.
+* Asks why was “bad faith” not shot down, and implies the moderation team is scared of moderating Bubblie and Levi.— “nobody is unbiased”.
+
+She claims bubblie and Levi get "preferential privilege", and that gdude is "isolating minority groups" by listening to them on racial topics. She goes on to ask him to "treat everybody equally" and "not give people preferential treatment because of the circumstances of their birth"
+
+Curle requests to be educated by gdude, again, a white man, on the topic of racism. gdude states he is not comfortable with this, and offers Curle asking Levi directly.
+
+Curle says she needs time away, and this is the last time she is seen.
+
+## Removal from the Program
+
+Between the 7th of April, the day of Curle's last message in the QCC, to the 15th, no Forge member attempted to address any of the concerns raised by anyone from any other community.
+
+Given that Forge was evidently not willing to cooperate and collaborate within the QCC program, a call for Forge's removal from the program was started on the 15th and scheduled to end on the 24th, under the following clause for possible removal of communities from the program: [\[33\]](#ref-33)
+
+> Substantiated concerns regarding a community's staff teams perpetuating harmful behaviour — such as paedophilia, physical violence, or ableism, racism, transphobia or other bigotry.
+
+While we were aware of the stress Curle was under to write a statement and assist Lex in writing his own statement, such heavy concerns and disregard to address it in a space this sensitive was unacceptable, and it clearly seems that no further attempts were made to seek critical feedback, despite our own concerns.
+
+The statements[\[34\]](#ref-34)[\[35\]](#ref-35) were released on the 17th of April. Noticing how our concerns were mainly brushed off, we looked into the RFCs to determine if there was a way to remove Forge earlier. Critically, a removal vote cannot be vetoed, meaning that once enough votes are cast, the results cannot change. Out of all three voting communities, one already voted positive, and only one more positive vote was needed to seal the results. Quilt's voting period was scheduled to end on April 22nd, which would push the vote to a pass.
+
+Given the RFC never mentioned anything about what happens when the vote results are sealed but the voting period has yet to end, we added a clause to better define that[\[36\]](#ref-36). Keep in mind that clause cannot change a vote result — it can only make the vote effects act earlier. Given how minor the RFC was, and the sufficient community team approval (including one from an uninvolved Administrative Board member), the RFC was merged. Shortly after, the third community involved gave a vote of agreement, leading to the prompt removal of Forge from the Quilt Community Collab program.[\[37\]](#ref-37)[\[38\]](#ref-38)
+
+We would like to mention that across 3 different organizations, 26 people voted in favor of the removal, 1 explicitly abstained and no one voted against it. This vote was not contentious by any metrics, even outside of Quilt. The vote ended before Quilt even cast its vote; the other two communities had already voted toward removal.[\[39\]](#ref-39)
+
+## Our take on Forge
+
+Curle's denial of the implicit bigotry she continues to perpetuate has led us to believe that Forge, under her leadership, cannot continue to pursue the goals Quilt and all our affiliated communities in the QCC program strive to achieve, most notably of safety and equity for all.
+
+As such, we have cut ties with Forge, and we recommend our vulnerable users to stay away from Forge-run spaces — racial bigotry can never be actively addressed and eliminated in a space if said space's leader denies their racist beliefs.
+
+# Larry
+
+While this section seems unrelated to the previous events, there is in fact a deeper connection and we would heavily encourage you to read on.
+
+## The ModMail
+
+On the 11th, a community member opened a ModMail thread to report off-server behaviour containing islamophobia, 9/11 jokes, autism mockery, and other issues. Moderators internally discussed an intent to ban, but no one ended up actioning the ban or responding at the time.[\[40\]](#ref-40)
+
+The following day, Larry unilaterally decided to not ban and replied as such to the reporter, notably without any discussion with the rest of the moderation team.[\[41\]](#ref-41) Levi responded internally that this wasn't the correct course of action, as the content was obviously Islamophobic. Larry continued to defend his action saying it was off-server behaviour and "just a kid", and therefore not worth actioning, which goes against our principle of defensive moderation against any potential bad actors who can endanger our community[\[42\]](#ref-42). Two other moderators agreed with levi while Larry continued to push back, despite going completely against the said principle.[\[43\]](#ref-43)[\[44\]](#ref-44)
+
+In the process, Larry made some other deeply concerning statements, such as calling Levi's experience with bigotry "epistemic privilege",[\[45\]](#ref-45) tone policing him, claiming he was arguing in bad faith,[\[46\]](#ref-46) insisting on using the word "privileged" despite Levi's request not to and went as far as comparing Levi to colonisers[\[47\]](#ref-47).
+
+## Kashike's intervention
+
+Even though the Keyholder is allowed to "oversee the community team in their actions and processes, and provide opinions and feedback if they wish", according to RFC 7, they must factor in any conflicts of interest that may arise before voicing their opinion. Yet, Kashike entered the conversation to defend his friend in a direct demonstration of favouritism and conflict of interest: [\[48\]](#ref-48)
+
+> Forgive my rough words here, but this entire conversation is fucked up on multiple levels.
+> What I do know for a fact is that some of the comments levy was making towards larry in here earlier were not warranted.
+> I will not stand by and be quiet when things like this happen.
+
+Kashike continued to tone police Levi to defend the racist points on his friends, which is both a conflict of interest and generally unacceptable. Similar to Curle, Kashike then moved to gdude's DMs to tone police Levi even more and go as far as claiming he should apologise. Kashike asked gdude to send a message in the `#managers` channel saying that he got contacted by someone for the discussion, failing to disclose that this person is Larry, one of the involved parties[\[49\]](#ref-49)[\[50\]](#ref-50). Kashike then continued to push for the admins to ask Levi to apologise to his friend as he got contacted by this same friend who was "concerned": [\[51\]](#ref-51)
+
+> I usually don't say much in conversations, but for the one in question I was contacted privately due to what was going on
+
+Once again, Kashike made it seem like he got contacted by another staff member, and failed to disclose his conflict of interest and that Larry was the person who contacted him.
+
+## Low activity requirement guidelines
+
+Considering how out of touch with the community Larry was, the Starchildren decided to action an item that have been on their to-do list for twelve days at the time: talk about introducing a low activity requirement for Moderators, Community Managers and Administrative Board members[\[52\]](#ref-52). Later in the day, they mentioned in `#managers` that they were going to talk to Larry about his future at Quilt if no one was opposed to the policy. Kashike answered with:
+
+> ... how does that make sense to do at all?
+
+They clarified that while the guidelines weren't made especially to remove Larry, they could also be used as such[\[53\]](#ref-53). Somehow at the same moment, Larry learned about that message in `#managers`, a channel he could not have read[\[54\]](#ref-54), while gdude got a complaint in DMs from Kashike at the same time[\[55\]](#ref-55). Larry accused the Starchildren of coming after them, after which the Starchildren clarified that while Larry's behaviour prompted them to fast forward the policy work, they were not looking to get them out but rather talk, as otherwise, a demotion would have already been in progress. Larry then revealed he abused a misconfiguration of PluralKit, an accessibility tool, to read the private channel[\[54\]](#ref-54). When asked who this misconfiguration was reported to, Larry answered Kashike, who did absolutely nothing to try to fix it or warn the Managers, the ones responsible for fixing this sort of issue. _The Keyholder isn't supposed to do anything_[\[56\]](#ref-56).
+
+In parallel, the Starchildren clarified the same thing in the `#managers` channel. Kashike responded with the following message: [\[53\]](#ref-53)
+
+> I'm going to go do something relaxing for a while - getting involved in things, when I usually don't, has made me a bit stressed out. Feel free to ping/message me if necessary, though. Hugs to anyone who wants one.
+
+Kashike didn't send any other message before taking over the servers.
+
+## Larry's Demotion
+
+Due to Larry's concerning behaviour with the PluralKit leaks, the Starchildren decided to move directly to a demotion against him on the 14th. [\[57\]](#ref-57)
+
+> Larry hasn't been inactive at all in Quilt those past few months. In total, Larry has about 500 messages on both servers combined. From November 2022 to April 2023, Larry has respectively sent the following number of messages: 32, 2, 7, 18, 3, 8. Considering Larry has been inactive since Quilt's inception, I don't consider him legitimate to hold the moderation powers given to him.
+>
+> This has recently been characterised by a few events, most notably the non-profit discussions where he made non-sensical, totally out of touch comments, and the \[name redacted\] thread where he immediately attacked levy in bad faith, accompanied with some pretty racist takes.
+
+No disagreement was voiced during the 6 days this vote went on for. It didn't have a chance to go through however, as he left the server on the 20th, after sending a paragraph you may read below in "[Larry (part 2)](#larry-part-2)".
+
+# zml
+
+On the 18th of April, zml sent the following message in the internal `#dev-office` channel in the Toolchain Discord server, which only the Quilt Developers, along with the Community Team and the Administrative Board, can view, and then left all Quilt-affiliated spaces:
+
+> hey gang, with some of the recent events i'm rather dissatisfied with the way quilt has been going, and i'm afraid I don't have strong hopes for a future for this project. I've discussed some of these things with others, but putting it out there, some of the thoughts i've had recently:
+>
+> \- The division between the community team's side of the project and the development teams has created fragmented planning and memberships, where the community has developed fairly divergently from the way the development sides work, and there is friction where some community team members believe that they are in some way able to overrule developers, rather than being equals in one project.
+>
+> \- Your moderation strategies feel super reactionary -- between only bring up policy when it's convenient to obstruct the work of others, and your swift removal of Forge from the community collab server (and all quilt spaces following) as soon as they failed to meet your expectations on their beliefs. We all say dumb things, are raised with 'bad' beliefs, and are here to learn and grow -- try to support that rather than punishing.
+>
+> \- A lot of the development team is burnt out, and the isolation of the toolchain discord makes it difficult to attract new contributors from ideal candidates who might be intimidated by joining an entirely separate guild. it's a bit of a vicious cycle at this point, but I hope you can break out (be kind to yourselves, devs)
+>
+> \- Levy, I would like to think there are good points in a lot of what you say, but every time someone crosses you whether it's one of your colleagues here in staff or other community members, it feels like you lash out in a way that helps you unload, but isn't very productive in building up relationships with other staff and the management of other communities
+>
+> \- Hope and the other Starchildren, your overly legalistic beliefs about this project's management and infrastructure goals out of line with other far larger organizations in the community have burdened everyone else on staff. Please stop.
+>
+> \- g, I think what you've created in quilt community is an interesting perspective on building a community and has succeeded more than i would have expected, but it doesn't seem to have meshed super well with the development work that is essential to keeping the project relevant, and i'd think would have trouble scaling to cast the broad tent initially imagined for Quilt. It really feels like you are trying to do some level of catching like, pre-crime that is a bad road to be on.
+>
+> \- For all of you, please take time and try to have your own conversations with people involved in situations, try to avoid just hopping on the bandwagon for votes (and maybe don't short-circuit votes where nothing about the situation at hand will change).
+>
+> with that, i wish you all well on your projects and hope that despite my expectations Quilt can turn things around -- feel free to reach out to me if you wish to talk further (tho as always my availability is a touch limited, responses may be delayed). with that i'm out :)
+
+The first and third points are decent arguments about the split between the development and community aspects of the project, which is something that we were actively working on and has only been delayed by those events.
+
+The second and sixth points are simply a fundamental misinterpretations of what moderation is for, catching problems before they happen. We don't have to wait for someone to hurt our sensitive users before acting.
+
+The fourth point about levi is simply tone policing.
+
+The fifth point is simply nonsensical, the Starchildren handle legal at Quilt and will therefore adopt a legal viewpoint. Their real life job is also infrastructure work, they should have the qualifications (and the authority, as the Infrastructure Lead) to set the project's goals.
+
+The seventh point probably refers to Forge, despite the vote being called by two communities other than Quilt. As outlined previously, the short-circuit clause couldn't have changed the result of the vote.
+
+Considering we know she was "conspiring"[\[69\]](#ref-69) with Kashike and Larry, we can only assume this message has been written in bad faith.
+
+# Larry (part 2)
+
+Larry left all servers late on the 19th, leaving the following message in both the Toolchain and Community servers:
+
+> Hey @everyone,
+>
+> Just want to say first of all, I appreciate everyone's efforts to make Quilt safe and productive. With that, I'm resigning as a moderator.
+>
+> I hope you take the time to read what I'm going to say, instead of dismissing it as a "whole load of nothing". Despite my lack of chatting time in the Quilt servers, I've spent the last 2 years lurking every important thread and channel, watching and learning.
+>
+> 1\. I suppose this is a good spot to express my displeasure at being voted out on the basis of lies by Hope. I know about the vote, but more importantly I know about the reasons provided for the vote. I did _not_ "immediately attack levy in bad faith." It's a shame that here, where Hope was biased, I didn't get a chance to defend myself at all. To be clear, levy immediately attacked me, and I know that everyone knows it was him who reacted (at best) suboptimally. I cannot emphasize how degrading it is to have someone who claims to be racially sensitive along with an entire staff team try to treat me differently because of my race (regardless of what that race is) or claim that I'm a bigot. I'm not - I literally just called out persistent bullshit. Gdude, your siding with levy on that issue displays a huge amount of unwarranted bias. There's a difference between respectability politics and treating others as lesser, and levy consistently treated me as a lesser, which you just reinforced. I think you're consistently letting your biases blind you to situations that would otherwise be unacceptable, even to you. At least, I hope so, because otherwise you just don't see (or worse, do see and don't care) how bad some of the stuff that you allow is.
+>
+> 2\. Hope, I'm sorry that my arguments against your registering Quilt solely under your name as a legal entity in France made you upset. They should not be used against me - just because you disagree with me, doesn't make all of my comments out-of-touch or baseless. If people can't disagree with you without getting 'marked' as an enemy and then voted out because of that disagreement, you're fostering hostility within the staff team. Perhaps this is a warning to everyone else; don't get on Hope's bad side or disagree or you'll be voted out!
+>
+> 3\. Levy, your racial aggrievedness is not an excuse to be a jerk. That's what you do when anyone gets on your bad side - you're a jerk, and it's not okay. Please don't take this as an attack, but there are infinitely less destructive (or, imagine, constructive!) ways to handle people that you think are uneducated. Assuming they're either racist or an idiot is the wrong assumption to start off with. Just going after them and their character doesn't even help _you_ with anything other than perhaps feeling or looking more like a victim of society. And sure, you (maybe me too!) are a victim of society. Making that your grounds for attacking others is illegitimate. I know this will probably be dismissed, but I want nothing more than to see you grow out of the looking-for-blood attitude you go into conversations with. It'd be a benefit for everyone.
+>
+> 4\. zml was here when Quilt started. zml actually helped to create Quilt, and y'all not knowing her is a shame. Assuming she's racist, leaving because she doesn't support racial diversity efforts, is really stupid. looks to me that she left because, like me, she can't believe some of the things that are allowed to go on. There's a huge difference between pushing for racial diversity and treating levy's word as infallible, and attacking the same people that levy attacks just because levy attacks them.
+>
+> 5\. To everyone else, thank you again for your dedication to being good people and making a good community. I appreciate it. Be careful not to buy into what others say just because they're good - form your own views and openly disagree when you see something unjust or plain stupid. That's how communities grow. Also, the leaks indicate a lack of trust in the system and its leaders. Work on that, y'all?
+
+Besides the pettiness of the `@everyone` pings and leaving before the vote goes through, let's break down those points one by one:
+
+1. As you could previously see, the demotion was about inactivity, a fact by all metrics shown previously. If Larry actually waited, according to the process he would have been offered to submit a counter-argument, which is a direct way of defending yourself[\[58\]](#ref-58). The double standard is impressive when it comes to the accusation of bias, considering his undisclosed friendship with Kashike[\[10\]](#ref-10). The fact that the rest of the Community Team agreed with gdude that levi's behavior was acceptable shows there is no actual conflict of interest.
+2. Again, Larry's demotion started because of his inactivity[\[52\]](#ref-52). The argument of the non-profit was brought up as Larry claimed there was no need for a legal entity, showing a clear lack of knowledge of months of previous struggles due to not having one. Other disagreements with the proposal weren't factored into the demotion. This argument also disregards the democratic aspect of Quilt; no one individual is able to decide who can leave and who can stay[\[57\]](#ref-57)[\[58\]](#ref-58).
+3. This point just comes off as extremely tone-policing and condescending. Saying that an actual victim of racism is trying to make himself look like a victim is sickening.
+4. As you could see in the previous section, calling out zml for racism was and still is accurate.
+5. There isn't much to say about this point, other than the group of three racists working together is hardly a demonstration of any failure.
+
+Overall this post is crippled with tone-policing paternalist points and false truths and clearly demonstrates the racism and bad faith that characterized his previous interactions.
+
+# The Hostile Takeover
+
+## Kashike takes control of the server
+
+A few hours after Larry left, Kashike used a self-bot to kick all the staff members and bots[\[59\]](#ref-59) from the servers and deleted all webhooks[\[60\]](#ref-60). He posted the same message in all news channels: [\[61\]](#ref-61)
+
+> This project has become controlled by a community moderation team that focuses their energy on finding ways to attack others, which is too dark an irony for my tastes considering this project's origin. In recent times, this moderation team has gone on a quest to personally attack community members and in the past has even doxxed individual's IRL information to justify bans.
+>
+> Per RFC 7, which grants me independent oversight powers to prevent exactly this sort of situation, I am freezing this discord server while we figure out what to do next, and I make this offer to the development team:
+>
+> \* If you wish to continue working on the projects without the previous moderation staff, we can consider rebranding the project while focusing on releasing a quality product, and can use the Toolchain discord to facilitate that, so the teams remain together.
+>
+> \* If you wish to stay with the moderation team that has stated they outrank you, you are entitled to do that.
+>
+> I'm not going to pressure anyone on this decision, and I am sorry that it has come to this.
+
+We will break down the first paragraph in a bit, but we first want to emphasise that Kashike had absolutely **no** authority in doing this. The existence of the Keyholder was made especially to avoid a hostile takeover, which Kashike undoubtedly knew, considering his involvement in Quilt's inception. Quoting the same RFC 7 Kashike mentions: [\[2\]](#ref-2)
+
+> A keyholder is a democratically elected member of the community that otherwise has no direct involvement or stake in the management of the community. By electing an otherwise unrelated party to be a keyholder, it's hoped that the Quilt community spaces can avoid the issue of a community leader gone rogue - it should prevent an abuse of power from giving someone total control over any community space, at least as far as is possible.
+
+While it is true the RFC says "they're also welcome to oversee the community team in their actions and processes, and provide opinions and feedback if they wish", this isn't a free pass to override all our democratic processes.
+
+Kashike also tries with this message to jeopardize the project and claim it for his own. He did not attempt to contact anyone whatsoever before doing so.
+
+## The Developers' Reaction
+
+After posting his announcement, Kashike pinged all the developers asking for questions or comments. Three developers immediately pushed back and mentioned that he also kicked developers by kicking the moderation team. Kashike responded that they can rejoin at any time, although he never actually gave back the roles necessary to view the channel, to which the developer answered that he "could have discussed before kicking them"[\[62\]](#ref-62). Two others developers then proceeded to derail the conversation by talking about water, and Kashike was promptly ignored until the server got restored[\[63\]](#ref-63).
+
+## The Community's Reaction
+
+It is hard to grasp the reaction of a large community over multiple hours, so we encourage you to go read the [conversations below this message](https://discord.com/channels/817576132726620200/833939581798711306/1098438405194522737) on the community server for the full context. Outside of a few people who wanted to hear more from Kashike, a very large number of people condemned Kashike's behaviour and wanted to see the server returned to its rightful owners, the Community Team.
+
+We will note that one death threat made by a community member was immediately called out by the rest of the chat and the moderation team, and the person who made it was subsequently banned by Kashike with support from gdude and MrMangoHands[\[64\]](#ref-64).
+
+## The Recovery Server
+
+A temporary server was made by the Community Team to gather staff and some community members. Since people left between when the servers got restored and this statement being written, we don't have the exact count, but we know the server had at least 3 admins, 14 staffers and 20 community members[\[65\]](#ref-65), all in disagreement with Kashike's actions.
+
+## The Group DM
+
+Kashike asked gdude to create a group DM with himself and all the other admins, except for the Starchildren, who he explicitly requested be excluded. Inside the DMs, Kashike repeated that he didn't want the Starchildren and Levi inside the group DM, despite the former being a part of the Administrative Board and the latter not even being on said board[\[66\]](#ref-66). He later claimed that he was discussing with the entire admin board[\[67\]](#ref-67), failing to disclose he didn't include the only coloured administrator, another example of Kashike's racist prejudices.
+
+gdude opened by asking why Kashike sees "leaking or leaving a vulnerable community without moderators as any kind of solution." He promptly ignored the major safety concern raised by gdude to talk about his grievances with the Community Team.[\[68\]](#ref-68)
+
+While we won't talk about everything that happened in those DMs (they span more than 25 desktop screens) for the sake of keeping this statement digestible, we want to talk about a few of the accusations being made.
+
+Kashike attempted to call out zml and Larry's messages as being unfairly dismissed, which makes sense considering they were "conspiring together."[\[69\]](#ref-69).
+
+## The "Doxxing" Accusations
+
+This is the only accusation Kashike made public, without any authorization from anyone in the team despite claiming so: back in December 22, 2021, a year and a half ago, gdude investigated reports from a member of the Quilt Community Collab about another member who was accused of having sexually harassed them. Due to the complexity of the situation and gdude's memory impairment, he made an internal thread to track his "research" into the accusations. Gdude had, actually, received court documents from the victim, but had been asked to not say so outright to protect the victim. As such, the thread was largely an attempt to _create_ a paper trail that could reasonably lead to the victim-provided documents[\[71\]](#ref-71).
+
+This thread was private to the moderation team and was never going to be public: this wasn't a doxx, everything stayed completely internal. However, Kashike had the following to say: [\[72\]](#ref-72)
+
+> I shared that thread with external community members and leaders, and all of them said the same thing (roughly): it is completely unacceptable to do something like that, and is not something that should be permitted in any community
+
+Taking an export of an internal thread and sharing it with third parties without any authorization from the victim is, on the other hand, doxxing, perpetrated by Kashike. He also waited more than a year and a half to kick the Community Team and discuss that thread, which he could have done anytime prior, especially considering he participated in that thread himself[\[73\]](#ref-73). We can only imagine this is a pretext to cover his defense of his friend being removed from the staff.
+
+It is also a breach of the European General Data Protection Regulations (GDPR), as the accuser's and accusee's personal data was being shared widely without any legal basis.
+
+## Recovering the Servers
+
+After waking up, the Starchildren, the legal handlers of Quilt, requested to be added to the group DM, which Kashike complied with. (note: this happened in Kashike's personal server which we can't access anymore, sorry we cannot provide any screenshots)
+
+Once the Starchildren were added, Kashike stated the following: [\[70\]](#ref-70)
+
+> The discussion in here have been good so far - all I ask is that anyone in here leave any swearing, threats, etc behind. People know me to be professional, and I don't want things to end badly here at all.
+
+This is quite ironic, as he himself has done the most unprofessional act possible that is this hostile takeover, not to mention how tone-deaf it was to say that to a group of hurt individuals.
+
+After the Starchildren had pointed out the legal issues, the lack of authority Kashike needed to justify his actions, the optics of kicking everyone out and seeking a new moderation team, and the total disapproval from the developers and the community, Kashike finally backed out and gave ownership of the servers to MrMangoHands.[\[74\]](#ref-74)
+
+Mango then gave the Community Manager role back to the other active Managers and proceeded to go to bed. They continued recovering the servers by reassigning the staff roles, adding back the bots and repairing all the other damages done by Kashike.
+
+To this day, Mango still acts as a temporary Keyholder while we find another solution (see "[Alternatives for the Keyholder System](#alternatives-for-the-keyholder-system)" section). In light of the leaks, conspiring[\[69\]](#ref-69) and hostile takeovers, Kashike, Larry and zml have been indefinitely banned from all Quilt spaces.
+
+## Our take on Kashike
+
+This day, Kashike has shown that he is completely unable to act as an impartial Keyholder for any project and will not hesitate to abuse this role and take over the server to serve his own interests. He has also shown that he cannot be trusted with access to sensitive information, as he will happily leak information to third parties and damage the project.
+
+We would like to suggest to communities who still trust Kashike to reconsider their relationships with him in light of those events.
+
+# What's next?
+
+## The Rendering Collab
+
+Quilt was also involved in another collaborative project: a rendering API which was meant to be a successor to both the Fabric Renderer API and FREX. The project originated as a proposal from Quilt to adopt FREX and integrate it as part of the Quilt Standard Libraries, as the maintainer of FREX, Grondag, no longer had enough time to work on it. Work was already put in FREX to allow it to be used on Forge and Fabric, which led to the question: do we keep that?
+
+Given the existence of Quilt Community Collab and the relatively healthy relationship between Quilt and Forge at the time, we contacted several communities to propose to work on a common rendering API: Render Wagon. The project had made theoretical progress and serves as a general direction for us to follow.
+
+Following what happened with Forge in Quilt Community Collab, and Forge's rendering technical representative leaving the project due to personal reasons, we no longer see any point in keeping this collaboration alive. Without a Forge representative, any work done with Forge would be pointless and morally questionable given past events.
+
+Quilt will likely absorb Render Wagon once more, likely as part of Quilt Standard Libraries, though details have not yet been determined.
+
+## Alternatives for the Keyholder System
+
+As these events have shown, having an impartial Keyholder seems impossible, and thus [we have created a proposal for a replacement](https://akarys.notion.site/Quilt-Keyholders-07704fd11bbd494bb89f7fed8fd69543). If you'd like to voice your opinion, you are more than welcome to [in the corresponding meta thread](https://discord.com/channels/817576132726620200/1098701370313420962) on the community server.
+
+## The Future of Quilt
+
+What does this effectively change for Quilt? Not much, really. All we learned through those events is that the Keyholder system is inherently broken and needs replacing. While zml, Larry and Kashike might have probably provided some interesting feedback, they are drowned in a sea of internalized and externalized racism making most, if not all, of their points null and void.
+
+Additionally, through this incident, the importance of diversity in community management has been made clearer than ever: it revealed to us the direct harm of the lack of racial diversity that Quilt, together with some parts of the wider community, face — we had been unknowingly harbouring racists for years, and instead of learning from minority voices, they were willing to take drastic measures such as planning and attempting a coup, all to defend their malignant beliefs that have only recently been challenged. (See the "[Importance of Diversity in Community Management](#importance-of-diversity-in-community-management)" section for more information on the topic)
+
+If you have some feedback for us that isn't about tone policing minorities, you are more than welcome to reach out to a Community Manager or a member of the Administrative Board. We would like to remind you that no action will be taken against someone providing feedback in good faith. You can even send us an email at [feedback@quiltmc.org](mailto:feedback@quiltmc.org) with a throwaway account if you'd like to provide anonymous feedback.
+
+# Additional explanations
+
+## Importance of Diversity in Community Management
+
+Bigotry in a community can manifest itself in several ways — either visibly and prominently as slurs, insults, harmful stereotypes, threats of violence, etc., or more subtly in the form of co-opting, dogwhistling, gaslighting, unequal representation, or identity erasure.
+
+While the former can usually be readily handled by a homogeneous moderation team, the latter can slip past moderation by appearing to be inconspicuous or insignificant to the white, cisgender, male, heterosexual majority of the anglophone Minecraft community.
+
+It is therefore imperative for people who have minority safety in mind to associate themselves with actual minorities, and let them partake in the moderation and management of their community. It is easier for a trans person to identify transphobic dogwhistles than cis people, in the same vein that a person of colour can more readily detect racist sentiments, rhetoric and stereotypes than white people.
+
+In other words, a community's leadership must be diverse, to properly recognize as many kinds of bigotry as possible, and protect as many different minority groups as possible.
+
+While LGBTQ+ groups are generally better represented these days in the communities we associate with, we would like to call for other communities to join us in our effort to push for diversity in other frontiers — most notably in racial and ethnic diversity. The events that transpired over the past two months have shown us that racism and white privilege are still very much alive and well in parts of the wider community, and our efforts must continue.
+
+## Professionalism and Racism
+
+It is often difficult for a person of colour to safeguard themself from \[micro/macroaggressions\], especially when they are one of the few racialized people in their working environment - and yet, they must in order to not become the “problem” or “angry” one in the work environment — unfortunately common stereotypes for people of colour.
+
+Protecting oneself against everyday microaggressions in a system that already establishes whiteness as the precedent in professional spaces can feel like a lose-lose situation.
+
+While many workplaces purport values of diversity and inclusion, these measures tend to be shallow. Addressing the emotional needs of workers and mitigating workplace hostilities can be a time costly endeavour, and can deter from the productivity of the workplace.
+
+We then see that it is in the best interests of a company to instead neutralize the situation, but this often means protecting the aggressor as opposed to the individual or group on the receiving end of a derogatory act or comment.
+
+So, if not asked formally by their employer, POC tend to understand and are conditioned to push down their emotions and feelings in the interest of a cohesive work environment.
+
+White professional spaces can thus be an isolating environment for POC.
+
+# A note about the GDPR
+
+All evidence in this thread may contain personal data that we collected on the basis of a legitimate interest ([Art. 6(1)(f)](https://gdpr.eu/article-6-how-to-process-personal-data-legally/)). We believe that shedding light on these events serves the public interest. Given the names and personal data needed to make this piece informative in certain sections, we have done our best to balance the value of the public interest and safeguards provided by the GDPR. If you have any questions or would like to exercise your rights, feel free to reach out at [privacy@quiltmc.org](mailto:privacy@quiltmc.org).
+
+# References
+
+
+
Discussion of the Keyholder role on Initiative - Screenshot
Curle saying levi refusing any clearing up - Screenshot
+
diff --git a/src/pages/fr/blog/2023-06-03-qm-needs-you.md b/src/pages/fr/blog/2023-06-03-qm-needs-you.md
new file mode 100644
index 000000000..9b5bfb799
--- /dev/null
+++ b/src/pages/fr/blog/2023-06-03-qm-needs-you.md
@@ -0,0 +1,36 @@
+---
+title: "Quilt Mappings needs you!"
+date: 2023-06-03 12:00:00 -00:00
+authors:
+ - ix0rai
+layout: /src/layouts/Post.astro
+---
+
+Hello quilters!\
+An important announcement from the Quilt Mappings team today (you can tell, because I’ve pulled out proper punctuation for the first time in my Quilt career). I’ll cut straight to the point and say it: Quilt Mappings is in need of contributions. The team and I have been working hard to keep up with Minecraft lately, but with a backlog of missing mappings since before I joined and Mojang always working to improve the game, we can’t hold up our completion by ourselves.
+
+
+
+#### What's holding the team back?
+
+The Quilt Mappings team is one of the largest in Quilt, but we’re still struggling to keep up. Why? There are a few reasons. Most of the team is simply busy and doesn’t have the time to submit new mappings, and those of us that do have time have other exciting projects to work on! We’re building an entirely new mappings toolchain, always matching to the latest snapshots, and delivering huge improvements to Enigma, the program that we use to create mappings. That’s not to say we’re not working on mappings all the time, though, and we’re always here to deliver quick reviews on pull requests!
+
+#### Why even bother?
+
+Quilt Mappings (or QM for short) is different from the other two sets of maintained mappings on the market: Mojmap and Yarn. We check our names against both sets constantly to make sure that we’re delivering the most accurate ones possible. Mojang names are often unintuitive, and aren’t built for modders: they’re made for the developers working on the game itself. Contrary to Mojmap, Yarn aims to deliver names that are easy to understand for modders, but since their names are not checked against Mojang’s intentions, they can sometimes be confusing and contradictory to the intended usage of the code. Both sets are excellent on their own, and QM is made to be a hybrid of the two, shipping clear, concise, and accurate names inspired by both. We’ve also implemented extensive checking for typos, Britishisms and convention violations to make sure no problematic mappings are published. Despite their drawbacks, Yarn and Mojang have 99% and 100% completion of class names respectively, and we can’t truly call ourselves the best with our measly 98.
+
+## How can I help?
+
+The biggest way you can help with QM is by contributing new mappings to the large swaths of the game that are missing names. All you need to help out is knowledge of Java! We have a couple cute documents already written up on how to contribute: check out our [CONTRIBUTING.md](https://github.com/QuiltMC/quilt-mappings/blob/HEAD/CONTRIBUTING.md) to find out everything you need to know before mapping! Making new mappings isn’t the only way to help, and if you want to improve our existing names, [our issue tracker](https://github.com/QuiltMC/quilt-mappings/issues) is a great place to find suggestions of names to change. However, be warned that if you change names made by me you run the risk of incurring my wrath (affectionate). Opening Enigma will immediately give you an idea of what needs doing in terms of new mappings, thanks to our handy little status icons next to each class. If a class has a check mark, you can move on, but anything with a yellow dot or red x needs your help! This adorable graph, generated by the Mapping Stats feature in Enigma, can help show you where to start. As always, we're happy to help you out with anything: using Enigma, what to name methods, where to map, etc! You can always talk to us on [our Discord](https://discord.quiltmc.org).
+
+
+
+If mapping the game is less your thing, we have plenty of other projects for you to help out with. We can also use the help of those experienced with Java, networking, Swing, Gradle, and even translation.
+Contributors have a few great options:
+1. Working on our new toolchain, which we’re calling Quilt Mapping Tools. You can help with designing the toolchain, writing Java code, designing the new mapping format, or even preparing other parts of Quilt to use QMT. The best way to find out what needs doing here is talking to our team leader, OroArmor, on [our Discord](https://discord.quiltmc.org)! You can also check the [QMT issue tracker](https://github.com/QuiltMC/quilt-mapping-tools/issues) to get a rough idea of the work that’s still in progress.
+2. Helping out with our deobfuscator, Enigma! Improving Enigma helps us make mappings faster and with fewer mistakes. To help out with Enigma, you can look at *its* [issue tracker](https://github.com/QuiltMC/enigma/issues), or try to break it to help us find more bugs. In particular, we're looking for help with solving a pesky ui issue detailed [here](https://github.com/QuiltMC/enigma/issues/108). Enigma is quite a complicated program, and you can always talk to me (rai), or Martrixx on [our Discord](https://discord.quiltmc.org) if you’d like some help understanding it. Enigma is separated into four parts: a backend, a command line interface, a server, and a swing GUI, which means there’s something for every type of Java experience! If the language you speak isn’t English *or* Java, Enigma also has internationalisation support! You can add languages in the [lang](https://github.com/QuiltMC/enigma/tree/master/enigma/src/main/resources/lang) folder, or complete translation for existing languages! Compare against the `en_us` file to find missing translations.
+
+3. Tinkering with our existing tooling! Our new set of tooling is nowhere near completion, and the stuff we use right now still needs maintenance and improvements. You can check [issues marked as “toolchain”](https://github.com/QuiltMC/quilt-mappings/issues?q=is%3Aissue+is%3Aopen+label%3A%22t%3A+toolchain%22) in our main repository to see what needs work right now.
+
+Thank you for reading, and we'll see you on the creature trail!
+\- rai
diff --git a/src/pages/fr/blog/2023-06-26-mau-beacon.md b/src/pages/fr/blog/2023-06-26-mau-beacon.md
new file mode 100644
index 000000000..57c64ddb0
--- /dev/null
+++ b/src/pages/fr/blog/2023-06-26-mau-beacon.md
@@ -0,0 +1,65 @@
+---
+title: "Evil Modding Project Adds Telemetry"
+date: 2023-06-26 12:00:00 -00:00
+authors:
+ - ix0rai
+layout: /src/layouts/Post.astro
+---
+
+If you've been keeping tabs on our RFC, or Request For Comment, [repository](https://github.com/QuiltMC/rfcs), you may have noticed that we've
+just merged a proposal for Quilt Loader to keep tabs on how many people are using it each month. All considered, it's unfortunate that it was RFC 81,
+not RFC 1984.
+
+
+
+## Why are we doing this?
+
+Excellent question, dear user. Over the last couple years of Quilt, we've been running [a website](https://quiltmc.org/),
+[a repository of compiled binaries called a Maven](https://maven.quiltmc.org/), and other miscellaneous bits that we need hosting for.
+One of the best ways for projects like us to pay for our infrastructure is by getting a sponsorship: a company agrees to pay some
+of our costs, for the low low price of an icon on the website or something similar. Since they're a company, before agreeing to take
+on the financial burden of an entire project, they first want to make sure that people will actually see that icon: that's where Monthly
+Active Users, or MAU, come in. MAU is a pretty universal statistic that shows how popular something is: my personal website has one MAU,
+which is just me coming back every once in a while when I add something interesting, while a big service like Github has millions of MAU
+from people coming back all the time to view and commit code. Every unique person who visits that month bumps the MAU number by one.
+Our potential sponsor gets to see that and go "ah, there are a pile of people playing on Quilt, that means a bunch of folks will see our
+little ad and check us out!".
+
+Another huge benefit of having an MAU statistic is that Quilt developers like me get to see just how many people are using our passion
+project, which is great motivation for us to keep improving it! I'm sure it'll always be fun to see how many of you are running around inside a Quilt-powered version of the silly block game.
+
+## *How* are we doing this?
+
+As neatly laid out [in the RFC](https://github.com/QuiltMC/rfcs/blob/main/specification/0081-active-user-beacon.md#explanations),
+the process is very simple.
+When you load up your game, Quilt Loader will check for a file that's shared by all your instances of Minecraft,
+that contains the last date that it told our infrastructure you're a user.
+If that month is the current month and you haven't opted out, Loader will move on to updating the stats. After running the opt-out and date checks, this process is entirely separate to loading your game, and won't slow anything down.
+
+
+
+When Loader has assessed that you're not yet considered an active user for this month, it sends a simple request with no data;
+no body or headers, to an endpoint at https://quiltmc.org. The server updates the counter without storing any identifying data.
+Then, Loader updates its persistent file with the current month, and continues on its merry way.
+
+### Will this steal my data, the family cat, and possibly my wife as well?
+
+The biggest consideration when designing this feature was privacy: we want to get the numbers, and absolutely nothing else.
+This means that while your IP address will be sent to our website once a month, we discard all information except the +1 to
+our counter as per [the restrictions in the RFC](https://github.com/QuiltMC/rfcs/blob/main/specification/0081-active-user-beacon.md#beacon-server-restrictions).
+The server accepting the signal is [fully open source](https://github.com/QuiltMC/beacon.quiltmc.org)
+and will remain that way so anyone can see what we're doing with what you send us. Additionally, since Quilt Loader is open source as well, you can see all the code sending the signal in [the MAU beacon pull request](https://github.com/QuiltMC/quilt-loader/pull/326).
+
+
+
+## I don't like that, how can I say no?
+
+There are two simple ways to opt out of being counted.
+1. When running Quilt Loader, add a property, `-Dloader.disable_beacon=true`, to your Java Arguments. In the official Minecraft
+launcher, you can do this by going to `installations -> edit -> more options -> jvm arguments` and appending that to the end.
+If you're using another launcher, check its documentation or poke around to find the same thing. Loader also has a collection of
+other useful properties, nicely documented in [its wiki](https://github.com/QuiltMC/quilt-loader/wiki/System-Properties).
+2. Set the `QUILT_LOADER_DISABLE_BEACON` environment variable to `true`. An environment variable is a value that is visible to all programs,
+so using this method will opt you out on *all* your installations.
+
+Though it's easy to disable, it would be lovely if you left it on for us. Who doesn't love a number getting bigger?
diff --git a/src/pages/fr/blog/2023-07-09-quiltflower-is-now-vineflower.md b/src/pages/fr/blog/2023-07-09-quiltflower-is-now-vineflower.md
new file mode 100644
index 000000000..e97683908
--- /dev/null
+++ b/src/pages/fr/blog/2023-07-09-quiltflower-is-now-vineflower.md
@@ -0,0 +1,17 @@
+---
+title: "Quiltflower is now Vineflower"
+date: 2023-07-09 14:55:00 -00:00
+authors:
+ - Southpaw1496
+layout: /src/layouts/Post.astro
+---
+The Quiltflower decompiler is an integral part of Quilt's toolchain, and has been quietly developed by jaskarth and the rest of the Decompilers team since our earliest beginnings. Yesterday, the team decided to separate from Quilt and continue development under the [Vineflower](https://github.com/Vineflower) organisation.
+
+Despite the separation and the change in name, we expect that very little will change for Quilt developers: We will continue to use Quiltflower — now Vineflower — in our toolchain as we always have.
+
+## Why did this happen?
+Although decompilation is a core part of Minecraft modding, decompilers aren't inherently related to Minecraft in the same way that Quilt Loader or QSL might be, and so the decompilers team hasn't really ever operated like the rest of Quilt's development teams. Because of this separation, they felt that it would be easier to develop Vineflower independently of the complexity that comes with having to coordinate the operations of an entire modding toolchain and its associated community.
+
+Although we will be sad to see the decompiler team go, we're very proud that they have managed (the geniuses that they are) to make Quiltflower into one of the best Java decompilers in the world, and bring it to a point where it is ready to leave our cozy nest, and blossom into its own amazing project.
+
+If you'd like to show the new Vineflower team some love, you might [send them a Star on GitHub](https://github.com/vineflower/vineflower).
\ No newline at end of file
diff --git a/src/pages/fr/blog/2023-07-12-quilt-telemetry-explained.md b/src/pages/fr/blog/2023-07-12-quilt-telemetry-explained.md
new file mode 100644
index 000000000..ca56bae5b
--- /dev/null
+++ b/src/pages/fr/blog/2023-07-12-quilt-telemetry-explained.md
@@ -0,0 +1,51 @@
+---
+title: "Quilt Loader Telemetry Explained"
+date: 2023-07-12 11:25:00 -00:00
+authors:
+ - Southpaw1496
+layout: /src/layouts/Post.astro
+---
+**Update 17/07/2023:** The beacon has been temporarily disabled following a report that it was errorneously storing IP addresses. Please see [this forum post](https://forum.quiltmc.org/t/important-monthly-active-user-beacon-update/1649) for more information.
+
+Quilt Loader 0.19.2 adds beacon functionality to count Quilt's Monthly Active Users, or MAUs. There has recently been some confusion about how this functionality works and why it was added, so this blog post is intended to provide a clear explanation of both of those things.
+
+
+
+## How the telemetry works
+Most telemetry is gathered with the intention of precisely learning how different demographics of people are using a product, perhaps with the intention of analysing behaviour to fine-tune an algorithm, interface, or marketing campaign. The word "telemetry" is associated with all sorts of sensitive data: your IP address, your location, the intimate details of how you're using an app, but we're not collecting anything like that. In Quilt's case, we only need to know how many people are using Quilt in the wild, so we optimised for sharing as little data as we possibly could while still accomplishing this goal.
+
+When Quilt Loader is launched, it first checks if the user has opted out of telemetry (more on this later), or if it has already added you to this month's active user count. If it neither of those apply, it sends an empty request to `beacon.quiltmc.org`, containing no data except the bare minimum that it needs to establish a connection. No identification, no information about how you're using Quilt Loader, no nothing. It then records the fact that it has made this request in a local file that is shared among all your Minecraft instances, so that it doesn't send any more requests that month. After receiving the request, the Beacon server increments the Monthly Active User counter, logs the request as a simple timestamp, then deletes all the connection data associated with the request that it just received.
+
+
+Image Credit: ixorai
+
+It's important to emphasise just how little data is being sent here. You're sending more data away if you:
+- Play Minecraft itself.
+- Use CurseForge, Modrinth, or any mods or launchers that integrate with them (such as Prism or ModMenu).
+- Connect to any website on the internet.
+
+If you want to dig into the exact workings of the system, you can look at [Quilt Loader PR #326](https://github.com/QuiltMC/quilt-loader/pull/326), [RFC 81](https://github.com/QuiltMC/rfcs/blob/main/specification/0081-active-user-beacon.md) which outlines the functionality of the active user beacon, and the [Beacon server itself](https://github.com/QuiltMC/beacon.quiltmc.org), which is fully open-source.
+
+## Why are we adding telemetry?
+Monthly Active Users is a statistic used all over the technology industry, often as a way to assess a platform's size or value. Although we've made sure that the telemetry we've added is as privacy-preserving as possible, it wouldn't be worth the disadvantages, however slight, if we didn't actually need it for some reason.
+
+The main reason we need a Monthly Active User count is that many companies and organisations are reluctant to work with us if they don't consider us large or consequential enough to be worth their time. Most notably, CurseForge asked us for a Monthly Active User count when we enquired about launcher support for Quilt. Additionally, although this hasn't happened yet, knowing our Monthly Active User count gives us a widely-accepted measure of size to use when applying for any sponsorships, grants, or other partnerships that we may need in the future.
+
+## But Why Couldn't You Just...
+We did consider some alternatives, however, everything we came up with was unsuitable for various reasons:
+- Measuring QSL downloads is inaccurate, because everyone downloads a new version of QSL whenever it updates.
+- Measuring Installer downloads ignores a large portion of users who use 3rd-party launchers, like Prism.
+- Measuring downloads of the Loader itself from Maven is technically infeasible because it is downloaded directly from a cloud storage bucket, and there's no point where you can reasonably insert a counter for download requests without spending lots of money.
+
+Additionally, all of those methods simply measure download count, which, while a useful statistic, is not as universally accepted as a Monthly Active User count.
+
+## How to disable the telemetry
+If, despite the precautions we've taken to measure telemetry in a privacy-preserving way, you'd still like to disable it, there are a couple of ways that you can do so.
+1. Add the Java argument `-Dloader.disable_beacon=true`. In the vanilla launcher, you can add Java arguments in Installations -> Edit -> More Options -> JVM Arguments. Note that this will only disable the telemetry for the Installation that you add the Java argument to.
+2. Set the environment variables `QUILT_LOADER_DISABLE_BEACON` or `CI` to `true`. How to do this varies in complexity based on your OS:
+ - In Windows, you can [add a new environment variable in Control Panel](https://www.architectryan.com/2018/08/31/how-to-change-environment-variables-on-windows-10/)
+ - In Linux, you can usually add the line `QUILT_LOADER_DISABLE_BEACON=true` to the `/etc/environment` file, but this can vary by distribution.
+ - In macOS, there seems to be no reliable way to set environment variables for the entire system, as opposed to just the zsh shell. We recommend using Java arguments instead.
+
+**Edit: 2023/07/12 12:50PM GMT:** Clarified that CurseForge takes Monthly Active Users as a consideration, not as a requirement. Also clarified that the Beacon server saves a timestamp, and fixed instructions about adding the beacon-disabling environment variable (thanks [Leo](https://60228.dev/@leo)!)
+**Edit: 2023/07/13 19:45 GMT:** The environment variable to disable telemetry is `QUILT_LOADER_DISABLE_BEACON`, not `QUILT_DISABLE_BEACON` (thanks esoterica!)
\ No newline at end of file
diff --git a/src/pages/fr/blog/[page].astro b/src/pages/fr/blog/[page].astro
new file mode 100644
index 000000000..f3bbfd2fd
--- /dev/null
+++ b/src/pages/fr/blog/[page].astro
@@ -0,0 +1,17 @@
+---
+import Base from "@layouts/Base.astro";
+//@ts-ignore
+import Paginator from "@setpieces/Paginator.astro";
+import { sortByDescending } from "@util/Util";
+
+export async function getStaticPaths({ paginate }) {
+ const allPosts = await Astro.glob("./*.md");
+ sortByDescending(allPosts, (post) => new Date(post.frontmatter.date));
+
+ return paginate(allPosts, { pageSize: 5 });
+}
+---
+
+
+
+
diff --git a/src/pages/fr/blog/index.astro b/src/pages/fr/blog/index.astro
new file mode 100644
index 000000000..1ffd24697
--- /dev/null
+++ b/src/pages/fr/blog/index.astro
@@ -0,0 +1,5 @@
+---
+import Redirect from "@layouts/Redirect.astro";
+---
+
+
diff --git a/src/pages/fr/community/code-of-conduct.mdx b/src/pages/fr/community/code-of-conduct.mdx
new file mode 100644
index 000000000..6e8c81928
--- /dev/null
+++ b/src/pages/fr/community/code-of-conduct.mdx
@@ -0,0 +1,81 @@
+---
+title: Code of Conduct
+description: Learn about Quilt's community spaces, and what we expect of our users.
+layout: /src/layouts/Page.astro
+---
+
+Like many communities, our policies are based on a Code of Conduct. Please make sure you read it before making use of
+our spaces, as it provides a set of behavioral guidelines that we expect everyone to adhere to.
+
+## Notes
+
+This Code of Conduct applies to anyone that makes use of a space managed by the Quilt team. **Not having read the Code of Conduct is not a valid excuse for breaking it,** and all members of the community will be held to this standard.
+
+While we try to go into detail with our examples, it's impossible to cover every possible situation in one document. In general, treat others how you wish to be treated -- if you wouldn't like to be treated in a particular way, don't treat others like that either!
+
+This Code of Conduct is the basis for [our rules](/en/community). We require that all community members read both this document, and the rules document.
+
+
+
+## Our Pledge
+
+We as community members, contributors, and team members pledge to make participation in our community a harassment-free experience for everyone, regardless of age, culture, ethnicity, gender identity & expression, nationality, physical or mental disabilities or differences (regardless of intensity), politics, race, religion, sex, sexual orientation, socio-economic status or subcultural affiliation.
+
+We pledge to act and interact in ways that contribute to an open, welcoming, diverse, inclusive, and healthy community, and we are committed to promoting these concepts.
+
+## Our Standards
+
+We expect the members of our community to participate in a positive, authentic and deliberate way. Consideration, respect and empathy are key when it comes to building and supporting a healthy community, and we request that our members exercise this through their actions.
+
+Please take into account that online communities bring people together from many different cultures and backgrounds. It's important to understand that sometimes the combination of cultural differences and online interaction can lead to misunderstandings.
+
+Examples of behavior that contributes to a positive environment for our community include:
+
+- Demonstrating empathy, patience and kindness toward other people
+- Being respectful of differing opinions, viewpoints, and experiences
+- Giving and gracefully accepting constructive feedback
+- Respecting others' personal choices, even when they don't line up with yours
+- Accepting responsibility and apologizing to those affected by our mistakes, and learning from the experience
+- Focusing on what is best not just for us as individuals, but for the overall community
+
+Examples of unacceptable behavior include:
+
+- The use of sexualized language or imagery, and sexual attention or advances of any kind
+- Trolling, insulting or derogatory comments
+- Personal or political attacks
+- Threats of violence, or violent acts towards others
+- Public or private harassment
+- Intentionally dead-naming or misgendering others
+- Publishing others' private information, such as a physical or email address, without their explicit permission ("doxxing")
+- Gatekeeping others' access to mental health or accessibility tools
+- Advocating for, or encouraging, any unacceptable forms of behavior
+- Other conduct which could reasonably be considered inappropriate
+
+## Enforcement Responsibilities
+
+Community team members are responsible for clarifying and enforcing our standards of acceptable behavior and will take appropriate and fair corrective action in response to any behavior that they deem inappropriate, threatening, offensive, or harmful.
+
+If a community member engages in behavior violating this Code of Conduct, the members of the community team may take any action they deem appropriate. Actions may range from a simple warning to the most drastic: permanent removal from the community, exclusion from any interaction, and loss of all rights in the community.
+
+## Scope
+
+This Code of Conduct applies within all community spaces (both online and offline), as well as when an individual is officially representing the community in public spaces. Examples of representing our community include using an official e-mail address, posting via an official social media account, or acting as an appointed representative at an online or offline event.
+
+This Code of Conduct applies to all projects, repositories and community spaces that are managed by Quilt, regardless of whether or not the use of this code is explicitly called out. We also reserve the right to retroactively enforce this Code of Conduct when community members violate it in spaces not managed by Quilt.
+
+## Reporting a Problem
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be reported to the Quilt community team directly on Discord, either via private message or the ModMail bot. If your report concerns a specific community team member or group of community team members, please send your report to a team member that is not part of the report, or a member of the administrative board.
+
+All complaints will be reviewed and investigated promptly and fairly, and all team members are obligated to respect the privacy and security of the reporter of any incident.
+
+## Changes & Feedback
+
+It is likely that this Code of Conduct will need additions, modifications and other improvements. Online culture changes, new views and sensitivities emerge which need to be taken into account. To that end, we reserve the right to update this Code of Conduct at any time, pending feedback from the community when possible.
+
+We always welcome feedback and suggestions. If you'd like to provide either, feel free to [open an issue on GitHub](https://github.com/QuiltMC/quiltmc.org/issues)!
+
+## Attribution
+
+This Code of Conduct is a heavily modified version of the [Contributor Covenant version 2.0](https://www.contributor-covenant.org/version/2/0/code_of_conduct.html), with inspiration and examples taken from the [JetBrains Open Source and Community Code of Conduct](https://confluence.jetbrains.com/display/ALL/JetBrains+Open+Source+and+Community+Code+of+Conduct), [Microsoft Open Source Code of Conduct](https://microsoft.github.io/codeofconduct) and
+[Open Source Design Code of Conduct](https://opensourcedesign.net/code-of-conduct).
diff --git a/src/pages/fr/community/index.mdx b/src/pages/fr/community/index.mdx
new file mode 100644
index 000000000..539e62dd5
--- /dev/null
+++ b/src/pages/fr/community/index.mdx
@@ -0,0 +1,27 @@
+---
+title: Community
+description: Learn about Quilt's community spaces, and what we expect of our users.
+layout: /src/layouts/Page.astro
+---
+
+import site from "@data/Site";
+
+You can find Quilt in the following places:
+
+- Our Discord server
+- Our forum
+- Our GitHub organization
+
+In all of these places you are expected to follow our [rules](/en/community/rules) and [Code of Conduct](/en/community/code-of-conduct).
+
+# Methodology
+
+Quilt's official community spaces exist to address issues in the wider modding community as much as the rest of the project does. While it's certainly true that no large project should be without official community spaces, we had several specific intentions in mind while creating it:
+
+- To build inclusivity and diversity into policy from the beginning, creating a safe community for minority groups as best we can
+- To create a plural-friendly space by including tools like [PluralKit](/en/community/pluralkit) from a very early stage
+- To get the community involved in community and policy decisions, allowing their voices to be heard and using their input to shape our spaces
+- To act with transparency where possible and reasonable without trying to hide our actions, and explaining moderation decisions when asked about them
+- To provide room for defensive moderation tools, and investigative moderation approaches -- allowing our staff to react to issues in the wider modding community, and solve problems before they're apparent to the userbase
+
+We think we've largely succeeded at this and our community has been excellent at correcting us when we make mistakes, holding us accountable, and helping us to understand issues that we otherwise have no direct experience with -- whether that's through lack of information, or just being privileged enough to never have encountered them directly. We always encourage our community members to contact us whenever they notice something untoward -- if you've been doing that, then thank you!
diff --git a/src/pages/fr/community/nsfw-policy.mdx b/src/pages/fr/community/nsfw-policy.mdx
new file mode 100644
index 000000000..d78f49aa6
--- /dev/null
+++ b/src/pages/fr/community/nsfw-policy.mdx
@@ -0,0 +1,208 @@
+---
+title: NSFW Policy
+description: Quilt's NSFW and Sexual Content policy - clarifying what subjects, media and content we do and don't allow.
+layout: /src/layouts/Page.astro
+---
+
+import Foldable from "@atoms/Foldable.astro";
+
+While it's true that Discord (and most other social media platforms) require their users to be at least 13 years of age, it's become clear that using common age-specific ratings for media (for example, PG-13) is not sufficient for our community. As the way people define NSFW content varies wildly depending on the individual and context, this document seeks to define what that term means for our community, and thus what content is unacceptable in our spaces.
+
+## Terminology
+
+We use the following terminology in the below document, which we've decided to explain here -- just in case you're not entirely familiar with them.
+
+### Body Horror
+
+"Body horror" can refer to one of a number of concepts:
+
+* AI-generated imagery that depicts people or animals with disfigured bodies and limbs, extra body parts, missing body parts, etc
+* Artwork and photography that depicts people or animals with disfigured bodies and limbs, where the primary intention of the imagery is to shock, horrify or scare the viewer
+ * Photos and depictions of people with physical disabilities or unusual birthmarks, missing limbs due to accidents, or any other physical differences to a typical able-bodied person **do not count as body horror** -- these people are not monsters, and deserve to be treated with the same respect and care that everyone else does
+
+### Content
+
+To keep things simple, we define "content" as anything a user could post, upload, link to or discuss. For example, we'd consider all the following to be "content":
+
+* A user's Discord, forum or GitHub profile, including their username, nickname, avatar, banner, "About Me" section, connections, or status
+* Textual content, including issue comments, forum posts and Discord messages
+* Mixed media, such as photos, audio, and images -- directly uploaded by the user, linked to from another site, posted in the form of a sticker or emoji (including as a reaction), and so on
+
+It's worth noting that this definition includes content not directly posted in our spaces, but made easily available to the users of our spaces by participating in them. We believe that this type of content can also be problematic in specific contexts, so we moderate it in addition to content directly posted by users.
+
+### Gender-Affirming Surgery
+
+"Gender-affirming surgery" refers to surgeries that may be undertaken by trans people in order to physically affirm their gender (and expression thereof), if they wish. This includes things like sexual reassignment surgery (SRS), facial feminization surgery (FFS), facial masculinization surgery (FMS), and so on.
+
+While it's true that cis people also occasionally undertake gender-affirming surgeries, this is considerably easier to for them to obtain when compared to trans people. If you're cis and are undertaking (or have undertaken) surgeries like this then your related discussions still come under this definition, but our policies largely focus on trans people, as they suffer from far more related discrimination -- medical, political, and otherwise.
+
+## NSFW? What's That?
+
+NSFW is short for "Not Safe For Work". This term, along with NSFL ("Not Safe For Life"), are often used online to denote content that you either wouldn't show to your boss, or wouldn't show to anyone -- acting as loose definitions for content that either belongs in specific spaces, or doesn't belong anywhere.
+
+Generally speaking:
+
+* **`NSFW` includes:** Suggestive content, porn, etc
+* **`NSFL` includes:** Animal abuse, gore (including any visible internal organs/tissue), vore, suicide, serious injuries, body horror, etc
+
+Additionally, SFW ("Safe For Work") and SFL ("Safe For Life") can be used as opposing designations for content that definitely doesn't come under the designations of NSFW or NSFL respectively.
+
+NSFL content is (and always will be) roundly banned at Quilt, aside from users seeking support from each other regarding how they feel about it, or for things that have happened to them. With NSFW content, though, the devil's in the details -- this term is loose by design, and they way it's applied differs greatly depending on the people, situation, and content in question.
+
+## Quilt's Definitions
+
+In order to make this easier to understand, we've split potentially NSFW content into several categories:
+
+* **Explicitly Allowed**: Content which we do not consider NSFW, and that we allow in any space
+* **Contextual**: Content which we may allow or disallow based on the discussion it's part of and context around it
+* **Restricted**: Content which is only allowed within the spaces we specifically designate for it
+* **Banned**: Content which is not allowed in all circumstances
+
+Some of our spaces may also have specific rules that apply to them. Where that's the case, we've listed them under the appropriate heading below.
+
+**Note:** It's always worth remembering that everyone has their own experiences and history. Additionally, note that _posting_ content and _discussing_ it isn't the same thing -- but if you're in doubt, you can always contact us via **@ModMail**.
+
+**Additionally:** We are not the ultimate arbiters of what should and should not be considered NSFW content on a global scale. We've listed some types of content below because a user had questions about it, because we want to ensure people understand how posting specific content impacts their safety, or because we wanted to be clear and avoid confusing users -- not because we consider it problematic, or we think other people shouldn't be allowed to peruse it (aside from a few specific examples in the banned category).
+
+
+Space-Specific Rules
+
+The following rules apply to specific Quilt community spaces. If we haven't listed a space here, you can assume that it follows the rest of this document. **Banned content remains banned regardless of space-specific rules.**
+
+* **Forums:** We only allow minimal contextual content outside dedicated topics and categories
+* **GitHub:** We do not allow any restricted or contextual content
+
+The specific definitions for each type of content mentioned here can be found in the following sections.
+
+
+
+
+Explicitly Allowed Content
+
+We allow the following content in our spaces.
+
+### Anywhere
+
+* Hormone replacement therapy and related discussions, including conversations about DIY hormone replacement therapy
+
+We believe that hormone replacement therapy should be available for anyone that needs it -- many countries are happy to provide access to this for cis people but unfairly discriminate against trans people, even though this approach contravenes modern medical recommendations and human rights work.
+
+Quilt has always been explicitly supportive of trans people, and some members of its Community Team consider themselves human rights activists. However, it's worth noting that testosterone is a controlled substance in the USA (the location of many platforms we use), and we may need to ask you to stop discussing ways to obtain it directly in our spaces.
+
+### In your Discord bio and connections
+
+Your Discord bio is the section displayed under "About Me" on your profile -- **not** your status, banner, or avatar.
+
+* Linked accounts containing potentially NSFW content, as long as they are correctly age gated or tagged for sensitive content as required by the platform
+* If your bio is otherwise SFW, a link to your (potentially NSFW) site or Discord server, as long as it's properly age-gated, without excessively explicit details in text
+
+While it would be completely inappropriate to engage in it within our spaces, we believe that sex work is work just like any other. We will not tolerate discriminatory behaviour towards sex workers in our spaces, but we will moderate sexual content in accordance with our policies regardless of whether the user in question is a sex worker.
+
+
+
+
+Contextual Content
+
+We allow or disallow the following content based on the surrounding context.
+
+### Anywhere
+
+* Non-sexual, consensual expressions of affection, including hugging/cuddling, parental/guardian-like affection such as sitting on laps, and so on
+
+Remember that **consent must be explicit** -- it's best not to make assumptions and to ask people if they're OK with an approach, instead of assuming they'll be OK with it and potentially hurting them.
+
+As long as this is **consensual and appropriate**, we're unlikely to try to moderate this outside of situations involving poor timing or lack of tact, where that's likely to hurt someone -- for example, you shouldn't try to hug someone when they're talking about how they've been negatively affected by people hugging them without consent.
+
+### With a spoiler and content warning
+
+* Mildly suggestive artwork or artwork depicting injuries, as long as the purpose of the artwork isn't simply to shock or upset other users
+* Artwork or photos depicting the intimate parts of a relationship
+
+While we don't have an interest in banning depictions of couples kissing (for example), we understand that this can be a trigger for some people, so we ask that it's posted with a content warning and a spoiler.
+
+
+
+
+Restricted content
+
+We only allow the following content in spaces designated for it.
+
+### In spaces designated for artwork and artistic discussions
+#### With a spoiler and content warning
+
+* Anatomy practise and historic artistic nudity (for example, the Venus statues)
+* Artwork that could reasonably be considered horror or horror-related (except for gore or body horror)
+
+It's difficult to improve your approach to drawing people in general without putting in some anatomy practice. However, this does not have to be extremely detailed work -- we advise that you use your best judgement, but we'll still remove content that includes depictions of intimate parts of the body that are too detailed.
+
+### In spaces designated for serious or sensitive topics
+#### With a spoiler and content warning, and without imagery
+
+* Discussions relating to sexual abuse (or other related trauma), from the perspective of activism, venting, discussing news, seeking support, and supporting survivors and the families of victims
+
+While we aren't therapists (or trained in how to help with these situations), it's hard to overstate how helpful it can be to receive support from your peer group, or just to talk about your trauma. We feel it's important for us to provide spaces where this can happen -- but we'd like to remind you that therapy is helpful for many people going through all sorts of things, and you should still seek it out if you need it.
+
+### In spaces designated for trans or LGBT+ people, or for serious or sensitive topics
+#### Without intimate imagery, aside from medical diagrams with a spoiler and content warning
+
+* [Sexual health](https://www.who.int/health-topics/sexual-health) and body care
+* Detailed information about gender-affirming surgery and what happens during it
+
+As a trans-positive space, it wouldn't make sense for us to disallow these discussions. It's still worth noting that even cis people may need to talk about sexual health and body care, though, so we don't limit this to trans-related discussions.
+
+### In spaces designated for trans or LGBT+ people, or for fashion or selfies
+
+* Photos of yourself that are not sexual in nature but depict suggestive or semi-intimate wear, or clothing that isn't suggestive but is commonly sexualized on the internet, with considerations made for your safety -- for example:
+ * Clothing such as hosiery, swimwear, crop tops, bras, tall heels or short shorts/skirts
+ * Body parts such as your chest, thighs, feet, or navel area
+
+This restriction is intended to protect users that wish to post photos of themselves, rather than entirely removing content from the view of other users -- it gives us a much smaller potential surface area to moderate, and makes it easier to pick out people that are just around to creep on people's photos.
+
+Regardless, please use your best judgement when posting content that may impact your safety. We'll always recommend you avoid posting your face or the area you live or work in, including scenery visible through windows.
+
+**Note:** It's not appropriate for threads or forum topics to be created to collate this type of content -- but it's OK to create (for example) an "outfit of the day" thread, as long as it isn't exclusively meant for this type of content, and allows for on-topic posts that don't match this designation.
+
+
+
+
+Banned Content
+
+We do not allow the following content under any circumstances, aside from the exceptions detailed previously.
+
+### Implied or explicit nudity
+
+* Implied or explicit nudity involving drawn characters, real people or AI generated images, including photos depicting the results of gender-affirming surgery or imagery where someone appears to be nude -- even when their intimate body parts are not visible due to positioning or framing
+* Implied or explicit nudity involving drawn characters, where the intention of the depiction is to be suggestive, sexual, shocking, or otherwise not incidental or intended for practice
+
+### Suggestive or sexual attention
+
+* Suggestive comments about (or reactions to) other users that haven't consented to it, especially if they've stated they're uncomfortable with it or aren't old enough -- regardless of how explicit the comments are
+* Sexual comments about other users, regardless of context or whether they consent to it, including implications about other people or groups of people
+* Any suggestive or intimate depictions involving people other than the poster, without their consent or knowledge -- including creep-shots or images reasonably assumed to be private, regardless of how well-known the person is
+
+### Suggestive or sexual content
+
+* Content (including imagery, audio and other multimedia) intended to be suggestive or arousing, or to seek a sexual response from another user
+* Explicit sexual content and behaviour, including role-play and innuendo intended to imply sexual intent
+* Depictions of movements intended to be sexual or seductive, including twerking (even if it's [a Crewmate from Among Us](https://among-us.fandom.com/wiki/Crewmate)), regardless of the reason it's being posted
+
+### Other content
+
+* Depictions of anything that can reasonably be considered NSFL -- animal abuse, gore, serious injuries, body horror, suicide, and so on
+
+
+
+## Moderation Policy
+
+First and foremost, we'd like to point out that we're not trying to be the fun police. Our community is host to a diverse range of people with many backgrounds, and some of them may suffer from panic attacks or other strong reactions to NSFW content. We believe that these people have a place in our community, and we'd like to make it as welcoming for them as we can.
+
+We're aware of the different levels of tolerance people have for drawn art versus photography and depictions of real people, and we understand the need to take content _and_ context into account when moderating this type of media. We'll do our best to avoid under-moderating while still allowing an acceptable degree of freedom.
+
+Additionally, it's worth pointing out that NSFW content can present a safety issue when posted around minors. Our team is intimately familiar with the correlation between people posting NSFW content around minors and how those people can be a danger to those minors, and we will not tolerate any behaviour that impacts the safety of our users.
+
+While we moderate NSFW content on a case-by-case basis in accordance with our broader moderation policy, we'd like to point out that the Community Team may include minors and people that have strong reactions to NSFW content. For this reason, **we do not allow minors to handle NSFW content**, and Community Team members that do not wish to handle NSFW content **are welcome to avoid doing so**, or ask another staff member to handle it on their behalf.
+
+It's important to us that everyone on our staff teams prioritizes individual safety and mental health above their work, but we'll still do our best to respond to reports and issues in a timely fashion.
+
+**Note:** There's a difference between sexual content and approaching another user sexually, or with sexual intent -- but the lines may be blurry in some situations. We consider approaching someone sexually to be much more serious than posting sexual content on its own, but it's also worth noting that sometimes the act of posting sexual content can itself be considered sexual attention towards someone. We always aim to prioritize safety, so it shouldn't be surprising if we are harsher than you may expect in situations like this!
+
diff --git a/src/pages/fr/community/pluralkit.mdx b/src/pages/fr/community/pluralkit.mdx
new file mode 100644
index 000000000..133301624
--- /dev/null
+++ b/src/pages/fr/community/pluralkit.mdx
@@ -0,0 +1,93 @@
+---
+title: PluralKit
+description: Learn about PluralKit, a tool we use to help plural systems to interact more comfortably on Discord.
+layout: /src/layouts/Page.astro
+
+redirect_from:
+ - /community/tupperbox
+---
+
+import Message from "@atoms/Message.astro";
+
+
+ **Note:** This document is specific to Discord. If you're not making use of
+ our community spaces on Discord, PluralKit won't be available.
+
+
+[PluralKit](https://pluralkit.me) is a Discord bot that exists to allow users to proxy their messages via Discord webhooks. This has many practical applications, especially given that Discord doesn't have any features that support the plural community, or any built-in mental health aids.
+
+PluralKit has all kinds of fun and interesting uses, but in Quilt community spaces it should only be used for [plurality](#plurality) or self-identity purposes, or as a mental health aid. We do not allow users to make use of PluralKit for role-playing.
+
+If you see users talking with the bot tag, they're talking through PluralKit. You can react to any message sent this way with the `question` emote (❓) for information on which Discord account the message belongs to.
+
+## General Usage
+
+The primary function of PluralKit is automatically proxying messages that people using it send, in order to make those messages appear to come from someone else. This is done by making use of Discord webhooks -- which has the unfortunate side effect of Discord stating that the messages were sent by a bot. Rest assured that this isn't the case -- while the messages were proxied by PluralKit, they were written by a real member of the community!
+
+Even if you aren't making use of PluralKit yourself, you can still leave reactions on messages that PluralKit has proxied. The following reactions allow you to interact directly with the system that sent the message, or to look up information about it:
+
+- ❓ (`question`) -- Get a private message with information about the Discord account that sent the message, such as username, nickname, pronouns, system/member descriptions and roles.
+- 🔔 (`bell`) -- Mention the Discord account that sent the proxied message, to make sure the system using it sees your reply. We advise using this sparingly, as it gets annoying and spammy quickly.
+
+## Moving from Tupperbox
+
+If you already have a system set up on Tupperbox, you can easily import that system to PluralKit. Simply follow these steps:
+
+1. Send a private message to Tupperbox: `tul!export`
+2. Copy the link that Tupperbox gives you, to use in the next step
+3. Send a private message to PluralKit: `pk;import `
+
+## Moderation Notes
+
+When working with PluralKit, please note that our moderation policy is one of system accountability, meaning that [plural systems](#plurality) are responsible for their members. Unfortunately, there's no practical way to moderate system members individually -- the community team is only able to target the Discord account you're using when acting as moderators.
+
+If you're part of a plural system, we suggest that you talk with the other members of your system and make sure they're aware of this.
+
+
+
+## Plurality?
+
+
+ **Note:** Pluralities are not the only valid reason to make use of a tool like
+ PluralKit, but it's by far the most common use for it in our community spaces
+ -- so we created this section to help explain the concept. Any gatekeeping of
+ these types of tools will not be tolerated in Quilt community spaces, but
+ you're always welcome to contact a member of the community team directly if
+ you have any concerns.
+
+
+Plurality is the concept of multiple people sharing a single body, inhabiting the same brain. Many people's first (or only) experience with this is from people with Dissociative Identity Disorder (DID), but there are many other situations that can cause something like this to happen -- and in many cases, **the existence of a plurality is not problematic or negative**. As [More Than One](https://morethanone.info) states:
+
+> Plurality (or multiplicity) is the existence of multiple self-aware entities inside one physical brain.
+>
+> You could think of a plural collective as a group of lifelong roommates, but with a body instead of an apartment.
+
+In general, a group of plural entities sharing one body tends to be known as a **plural system**.
+
+When interacting with plural people, remember to treat each individual member of a plural system with respect. Don't pathologise their identity (for example, by asking to meet the "real" person or suggesting that they need to be "cured"), and remember that many plural people consider their identity more a matter of philosophy than of medicine. Additionally, treat each system member as separate people, with their own memories, experiences and personality -- If they ask you to treat them in a specific way, listen to them and follow their lead as best you can.
+
+It's also worth noting that plurality is a whole world and plural systems often greatly differ from each other, sometimes identifying or manifesting themselves in completely different ways. All plural systems are valid, regardless of how their members identify or interact, how they were formed, or how they think about themselves.
+
+For more information on plurality, feel free to browse the following resources...
+
+### Ex Uno Plures
+
+
+ **Note:** This site belongs to a specific plural system, and much of what's
+ written there is related to their personal experiences of plurality.
+ Additionally, some articles there were written quite some time ago, and may
+ contain vulgar language and outdated terminology -- including terms that exist
+ outside the plural community. Nonetheless, it remains a popular and useful
+ resource for people approaching plurality and plural systems from the outside.
+
+
+- [Fictive Identities](https://www.exunoplures.org/main/fictive-identities) by Noël Dawkins
+- [Plurality for Skeptics](https://www.exunoplures.org/main/articles/skeptics) by Em Flynn
+- [Rules of Engagement: Plural Etiquette](https://www.exunoplures.org/main/articles/rules) by Em Flynn, Hess Sakal and Kerry Dawkins
+
+### Other Resources
+
+- [Cerberus Plural](https://cerberusplural.com), the plural news and media watchdog
+- [More Than One](https://morethanone.info), a quick, easy-to-digest overview of plurality -- including information on etiquette and myths
+- [r/plural Plurality FAQ](https://www.reddit.com/r/plural/wiki/faqs)
+- [Resource Links from Plurality Resource](https://pluralityresource.org/affiliates)
diff --git a/src/pages/fr/community/rules.mdx b/src/pages/fr/community/rules.mdx
new file mode 100644
index 000000000..d94154be9
--- /dev/null
+++ b/src/pages/fr/community/rules.mdx
@@ -0,0 +1,128 @@
+---
+title: Rules
+description: Quilt's core rules, which build upon the Code of Conduct to provide a set of concrete guidelines for behaviour.
+layout: /src/layouts/Page.astro
+---
+
+We expect everyone that makes use of any Quilt community spaces to adhere to the following rules. If you have any questions or suggestions, please feel free to contact a member of the community team or ask your question in the `#discord-meta` channel.
+
+**Remember:** Ignorance of our rules is not an excuse for breaking them. You are responsible for educating yourself on how every community you join expects you to behave, and "I didn't know that was in the rules" will never be a valid excuse.
+
+#### 1) Follow our Code of Conduct and NSFW content policy
+
+Make sure you read and follow [our Code of Conduct](/en/community/code-of-conduct), which outlines what we expect from you and is the basis for these rules. It's important that you read and understand the Code of Conduct, and the rules on this page -- feel free to contact a community team member if you need any clarification.
+
+Additionally, be sure to read and follow [our NSFW and Sexual Content policy](/en/community/nsfw-policy), which explains what types of content, media and related behaviour we do and don't allow.
+
+That said, remember that there will sometimes be situations that are difficult to fit into the Code of Conduct at a glance. In these cases, please contact a member of the community team for clarification.
+
+#### 2) Follow Discord's Rules
+
+In all community spaces, everyone must also follow the Discord [Community Guidelines](https://discord.com/guidelines) and [Terms of Service](https://discord.com/terms).
+
+These aren't just good to follow as a general rule of thumb -- this is also a requirement when operating a large community on Discord, especially if that community is aiming to be partnered or verified.
+
+#### 3) Try to speak English
+
+The world is a big place, and many people will have a different native language. The common language in our community is English, but we understand that not everyone speaks English at the same level.
+
+If you're not a native English speaker, please try to speak English to the best of your ability. Don't worry if you need to use a translation tool, or if your English isn't great -- we won't make fun of you, and we'll help you figure out the right words if you get stuck.
+
+#### 4) Listen to & respect all community team members
+
+The community team is here to support the community, keep it running smoothly, and ensure that it remains safe and friendly. In order to allow us to do our jobs, we need you to cooperate with us.
+
+Essentially, please take requests from community team members seriously and listen when a team member asks you to do something. If you have a problem with what a team member is asking you to do, we advise that you step away from the situation and send a private message to another team member.
+
+#### 5) Keep all projects legal, legitimate & appropriate
+
+While anyone may make use of the Quilt toolchain in accordance with the licenses applied to each project, all projects developed or promoted **in all Quilt community spaces** must meet the following criteria:
+
+- Projects must not be malicious -- which includes (but is not limited to) malware, mods that include backdoors, mods that modify Quilt in an attempt to hide themselves from servers they connect to, or mods that harass specific people or groups of people (for example, by automatically kicking them from servers with the mod installed)
+- Projects must not be sexualized, hateful or otherwise inappropriate in nature, and this also applies to all code and project assets posted for any purpose
+- Projects must not break laws, including copyright laws -- this includes piracy tools (including mods that use projects like `youtube-dl` for in-game music streaming) and hacked clients, as well as projects that fail to adhere to the licenses of other projects to the best of their ability
+- Projects must not break the Terms of Service or EULA of any organization, including (but not limited to) Mojang, Microsoft, Discord (including their ban on exploits and hacks) and any other community platforms we use
+- Projects must not hide their functionality and should be upfront with what they do -- however, projects with unfinished documentation or benign "Easter eggs" do not violate this rule
+- Projects must not make use of exploits in order to provide their functionality -- this is required by the [Discord Terms of Service](https://discord.com/terms) (among others), and is widely considered to be a problematic thing to do
+
+#### 6) Don't spam, and don't advertise outside the showcase channels
+
+We provide a number of channels for showcasing and informing users about your Quilt-related projects. Outside of these channels, we will not tolerate advertising or any other form of spam. In particular, posting large numbers of images or lines of text together can be particularly disruptive, and we'd prefer you make use of a pastebin site or image uploading site when sharing a lot of text or images.
+
+We may remove links to other Discord servers, communities and projects at our discretion if we feel like they've been posted inappropriately, rather than to start or contribute to a discussion.
+
+#### 7) Follow the given channel topic, and don't derail a discussion
+
+Most of our channels are strictly on-topic, and we expect our users to take note of a channel's topic and stick to it. We understand that conversations may span multiple topics and move onto something else, but we may ask you to move if a conversation leaves the scope of a channel's topic.
+
+Additionally, when entering a channel with an active discussion, please be mindful of that discussion and do not try to derail it (by talking over it, for example). We have multiple general (off-topic) channels you can use if a channel is busy.
+
+#### 8) When requesting help, specify your mappings (and other useful, relevant info)
+
+If you're working on a mod and asking for help in one of our many help channels, **make sure you specify what mappings you're using**. We recommend creating a thread, and putting the mappings in the thread name -- you can use these abbreviations to ensure everyone's on the same page:
+
+- `MCP` -- MCP/Forge mappings
+- `MM` -- Mojang Mappings
+- `QM` -- Quilt Mappings (The default for Quilt)
+- `YM` -- Yarn Mappings (The default for Fabric)
+
+An example thread title could be `YM | Entity pathing` or `[MM] Negative Enchants`. That said, we understand that quick questions may be more suited to direct discussion in the channels -- in those cases, **make sure you're clear about which mappings you're using**. You can also make use of the `:mcp:`, `:mm:`, `:qm:` and `:ym:` (or `:yarn:`) emoji if you'd like to.
+
+Ultimately, it's _your_ responsibility to ensure that it's as easy as possible to help you with your questions. The less work it takes for someone to understand your problem, the more likely you are to get a quick response! To that end, we also recommend you specify other useful information with your question -- such as **the version of Minecraft you're working with**, **error logs** and **relevant code snippets**.
+
+#### 9) Don't import drama or controversy from other communities
+
+We aim to be a safe place for everyone -- regardless of their background, identity, or other defining trait. In order to do this, it's important that people are allowed to interact without having to worry about controversies from the wider modding community that they may be seeking refuge from.
+
+Additionally, we expect a certain level of professionalism from our members. For both of these reasons, discussion of drama or controversies from other communities is banned -- including the numerous controversies that have unfolded within other spaces in the wider modding community.
+
+If you'd like to discuss these controversies with other users, start a DM group or join a community that's designed to handle that discussion.
+
+
+
+### Non-message mediums
+
+Do not change your avatar, nickname, username or custom/rich status to try to evade an infraction, or to attack or harass any user or group. If you'd like to appeal an infraction, please send a private message to any community team member.
+
+#### Nicknames
+
+All nicknames must adhere to the rules above. Additionally, they should not be hard to read or too noisy. Nicknames may be considered difficult to read or noisy if they contain emojis, Zalgo or other difficult-to-read styling, or Unicode control characters. "Empty" nicknames are also considered difficult to read.
+
+We also reserve the right to change or reset nicknames that are designed to place you higher in the member list in community spaces that have one, which is known as "hoisting".
+
+#### Avatars
+
+All avatars must adhere to the rules above. Additionally, avatars depicting weapons (e.g. knives, firearms), objectionable or Not Safe For Work (NSFW) content are disallowed, as well as fully-transparent avatars or avatars that appear to be fully-transparent by matching the platform's background color. This also applies to PluralKit member avatars.
+
+#### Custom/Rich Statuses
+
+All user statuses must adhere to the rules above. In particular, we don't want to see objectionable or NSFW emoji, the advertising of sketchy or NSFW websites, or hateful sentiment.
+
+### Reporting
+
+To report rule-breaking behavior on Discord, mention the **@Moderators** role directly in the channel, and a community team member will be along as soon as they can be. You can also send a private message to the **@ModMail** bot, which will open a thread that any currently available community team member can respond to.
+
+Alternatively, you can send a private message directly to any community team member, or otherwise contact the community team using the relevant contact methods for the given community space.
+
+If your report concerns a community team member, please send a private message directly to a different member of the community team or a member of the administrative board. All private reports will be treated with confidentiality.
+
+### Enforcement
+
+Our community team members have multiple tools at their disposal when dealing with those who violate the rules, including the following:
+
+- Verbally/textually warning or correcting users
+- Forcibly changing a user's nickname
+- Temporarily muting users
+- Temporarily or permanently removing users from the community (kicking, tempbanning, banning)
+
+Each situation is unique, and will be assessed on a case-by-case basis. All actions taken in response to rule-breaking behavior is done at the discretion of the community team member in question -- however, we will take feedback from the community if its members are not happy with how things were resolved.
+
+Appeals for community bans on Discord are handled via the **@ModMail** bot, and banned users are automatically sent an invite to a special server that exists for them to be able to send a private message to **@ModMail**. We advise that anyone appealing an infraction approaches their appeal with civility and respect, addressing the infraction reason and, if they agree with the infraction, considering the severity of what they did and what they may be able to do to rectify it.
+
+Appeals made for lesser infractions may result in a more significant infraction if the person appealing fails to approach their appeal with respect, or attempts to abuse the community team members or appeals process.
+
+#### Moderation Guidelines
+
+Moderation is a complicated subject at best, and it requires a lot of nuances and difficult decision-making. While it's impossible to enumerate every possible situation (and some situations will not suit our documentation), we've done our best to explain how we come to a decision, and what we expect from our community team.
+
+For more information on this, feel free to read [our moderation guidelines](/en/staff/moderation). If you have any feedback on this document, feel free to contact us!
diff --git a/src/pages/fr/dev/index.mdx b/src/pages/fr/dev/index.mdx
new file mode 100644
index 000000000..56e5c4179
--- /dev/null
+++ b/src/pages/fr/dev/index.mdx
@@ -0,0 +1,17 @@
+---
+title: Development
+layout: /src/layouts/Page.astro
+draft: true
+---
+
+import site from "@data/Site";
+
+# Develop Mods for Quilt
+
+If you'd like to learn how to get started developing Quilt mods, check out our [wiki](https://modder.wiki.quiltmc.org).
+
+You can find a list of available versions [here](/dev/versions).
+
+# Contribute to Quilt
+
+We welcome contributions to Quilt. You can find us on GitHub.
diff --git a/src/pages/fr/dev/versions.mdx b/src/pages/fr/dev/versions.mdx
new file mode 100644
index 000000000..fd693cb8d
--- /dev/null
+++ b/src/pages/fr/dev/versions.mdx
@@ -0,0 +1,65 @@
+---
+title: Gradle Snippets
+layout: /src/layouts/Page.astro
+draft: true
+# TODO add the javascript part of this page back
+---
+
+
diff --git a/src/pages/fr/help-wanted.mdx b/src/pages/fr/help-wanted.mdx
new file mode 100644
index 000000000..e9a9bbb9c
--- /dev/null
+++ b/src/pages/fr/help-wanted.mdx
@@ -0,0 +1,76 @@
+---
+layout: /src/layouts/Default.astro
+title: Help Wanted
+description: Ways you can help Quilt improve.
+---
+
+import Message from "@atoms/Message.astro";
+import PageTitle from "@atoms/PageTitle.astro";
+
+
+
+The Quilt Project is extremely community-oriented, and that means that it needs your help to succeed. This page is a
+list of opportunities to contribute - from contributing code to joining the Community team.
+
+## Development
+
+Development teams serve as the primary maintainers of the tools that make up Quilt, from build tools to mappings, libraries, and loaders.
+Development teams are responsible for triage, merging PRs, and helping the community maintain their respective projects.
+
+While teams provide a democratic leadership of each project, you **do not have to be on a team to contribute.** Team members come from experienced contributors who are interested in taking additional responsibility.
+
+If you want to help out with development, some projects that could use help are listed below.
+
+### Chasm
+
+The Chasm team is responsible for building and maintaining the [Chasm project](https://github.com/QuiltMC/chasm). Chasm
+is a bytecode transformer project, designed to handle collisions between transformers in as compatible a way as
+possible.
+
+This is a fairly technical project, but it's also one of our most interesting ones! If you're interested in helping out
+with the Chasm project, please sent a message in `#chasm` on the
+[Discord Server](https://discord.quiltmc.org/).
+
+### Mappings Triage
+
+The Mappings team is responsible for Quilt Mappings and its backbone projects, such as Hashed Mojmap. This team is
+always looking for more reviewers, who inspect Pull Requests to Quilt Mappings and ensure that they're high quality and meet the project's requirements.
+
+Experienced reviewers can join the Mappings Triage team, which give the final approval on Quilt Mappings PRs.
+
+If you'd like to learn more, please send a message in `#mappings` on
+the [Discord Server](https://discord.quiltmc.org/).
+
+### QSL
+
+QSL is always looking for PR authors and reviewers, who help QSL expand in scope to be a high quality and fully featured modding API. Reviewers inspect API structure, javadoc, implementation, etc for clarity and quality, ensuring QSL is both easy to use and easy to maintain. Experienced reviewers can join the QSL Triage team, which is responsible for giving the final approval on QSL PRs.
+
+If you'd like to write a QSL module or start reviewing PRs, please send a message in `#quilt-standard-libraries` on
+the [Discord Server](https://discord.quiltmc.org/)
+
+### Quilted Fabric API
+
+Quilted Fabric API is a re-implementation of Fabric API using QSL. We are looking for help maintaining this project!
+As a maintainer, you would share the responsibility for merging changes from upstream Fabric API, ensuring that it doesn't conflict with QSL,
+and re-implementing Fabric API features in QSL once they become available.
+
+If you're interested in taking up this role, please send a message in `#quilt-standard-libraries` on the
+[Discord Server](https://discord.quiltmc.org/)
+
+## Community Team
+
+The Community Team is responsible for taking care of our community, helping it grow, and keeping it safe, welcoming and
+running smoothly. Joining it is a great way to contribute if you're not a developer, or just not interested in
+developing modding technologies.
+
+### Moderators
+
+Moderators are the backbone of our community, ensuring that everyone is safe, that rules are enforced, and that
+discussions are conducted in a productive manner. While the current team can handle the amount of activity that our
+communities receive, the team needs to be expanded to deal with the increasing interest and community activity over
+time, and as development progresses.
+
+If you'd like to apply to be a Moderator, please join the [Community Discord Server](https://discord.quiltmc.org) and
+DM ModMail to send in your application. It is recommended that you read our
+[Rules](https://quiltmc.org/community/rules) and [Code of Conduct](https://quiltmc.org/community/code-of-conduct)
+before applying.
diff --git a/src/pages/fr/index.mdx b/src/pages/fr/index.mdx
new file mode 100644
index 000000000..ff184b489
--- /dev/null
+++ b/src/pages/fr/index.mdx
@@ -0,0 +1,45 @@
+import Home from "/src/layouts/Home.astro";
+import site from "@data/Site";
+
+
+
+ # Le projet Quilt
+
+ Le projet Quilt est une chaîne d'outils de modding open-source et communautaire conçue principalement pour Minecraft. En se concentrant sur la vitesse, la facilité d'utilisation et la modularité, Quilt vise à fournir une chaîne d'outils de modding moderne et élégante avec un écosystème ouvert.
+
+ Quilt est un projet qui est né d'un besoin de changement dans l'écosystème de modding de Minecraft. Nos équipes comptent de nombreux membres expérimentés de la communauté des moddeurs, ce qui nous permet d'éviter les erreurs du passé, qu'elles concernent la gestion de la communauté, la diversité et l'inclusion, la gouvernance du projet ou même la transparence. Pour plus d'informations sur la manière dont nous espérons y parvenir, [veuillez consulter nos pages "à propos"](/fr/about).
+
+
+
+ **Quilt est actuellement en version bêta.** Là est le danger -- il peut y avoir des problèmes, mais nous les corrigerons aussi vite que possible !
+
+ Si vous souhaitez nous aider à tester Quilt, n'hésitez pas à l'[installer](/fr/install), à l'essayer et à nous faire part de vos retours !
+
+
+
+ Quilt est axé sur la communauté et ne pourrait exister sans ses utilisateurs et ses contributeurs. Nous nous soucions de notre communauté, que vous soyez un membre de nos espaces communautaires, un contributeur occasionnel à l'un de nos projets ou simplement un utilisateur : Quilt existe pour vos besoins et non en dépit de ces derniers.
+
+
+ La modularité de Quilt n'existe pas seulement pour aider à organiser son code - elle s'étend aussi à ses utilisateurs et aux moddeurs. Si vous êtes un moddeur, nos outils de construction garderont la trace des bibliothèques Quilt que votre mod utilise. Si vous êtes un utilisateur, Quilt peut télécharger automatiquement les bibliothèques Quilt nécessaires pour faire fonctionner vos mods.
+
+
+ Quilt possède les fonctionnalités et les outils supplémentaires dont vos mods ont besoin pour réussir. Grace à une riche bibliothèque de modules qui vous aident à écrire des mods plus compatibles avec moins d'effort, à l'un des décompilateurs les plus précis fournis par toute chaîne d'outils de modding Minecraft, vous pouvez être sûr que **votre mod est entre de bonnes mains**.
+
+
+ # Rejoignez la communauté
+
+ N'hésitez pas à nous rejoindre sur l'un de nos espaces communautaires officiels en cliquant sur les boutons ci-dessous. Veuillez noter que **tous les utilisateurs de nos espaces communautaires (et de développement) doivent respecter [notre code de conduite](/fr/community/code-of-conduct) et [nos règles](/fr/community/rules).** Nous vous recommandons de les lire et de vous familiariser avec elles avant de nous rejoindre ou d'interagir avec nous.
+
+
+
+ # Participez
+
+ Il existe de nombreuses façons de nous aider, même si vous n'êtes pas un développeur. Une liste des projets ayant le plus besoin d'aide est disponible sur notre [page concernant l'aide pour les projets de Quilt] (/fr/help-wanted).
+
+ If you want to contribute, the best thing to do is join us on GitHub and the Discord Server. There's plenty of things to do, so we can always use more help!
+
+
+
+ # Derniers articles
+
+
diff --git a/src/pages/fr/install/atlauncher.md b/src/pages/fr/install/atlauncher.md
new file mode 100644
index 000000000..7f682a234
--- /dev/null
+++ b/src/pages/fr/install/atlauncher.md
@@ -0,0 +1,33 @@
+---
+title: "Install: ATLauncher"
+permalink: /install/atlauncher/
+
+layout: /src/layouts/InstallPage.astro
+platformKey: platform-atlauncher
+website: https://atlauncher.com
+---
+
+ATLauncher is a simple, easy-to-use launcher, built around the concept of building game instances from "packs". To set up your own Quilt instance, simply follow these steps:
+
+1. Download and install ATLauncher from [their website](https://atlauncher.com)
+2. Open ATLauncher and click on the **Vanilla Packs** tab on the right side
+3. Fill out the **Instance Name** and **Instance Description** boxes as required
+4. Pick the version of Minecraft you'd like to use for your instance
+5. Pick **Quilt** from the list of loaders below the Minecraft versions section
+6. Select the Quilt Loader version you'd like to use
+7. Click **Create Instance** to create your instance
+
+That's all there is to it! You can find your new instance in the **Instances** tab on the right side of the window.
+
+# Installing Mods
+
+To install mods to your ATLauncher instance, simply follow these steps:
+
+1. Click on the **Instances** tab on the right side
+2. Find the instance you'd like to add mods to, and click on **Add Mods**
+3. Find a Fabric or Quilt mod from CurseForge or Modrinth, and click the **Add** button
+4. Ensure you have also added the **Quilted Fabric API/Quilt Standard Libraries** bundle, which you can find [on CurseForge](https://www.curseforge.com/minecraft/mc-mods/qsl) or [on Modrinth](https://modrinth.com/mod/qsl)
+
+If you can't find the mod you'd like to install using the built-in search, you can click on **Open Folder** and copy any mod files you'd like to use into the `mods/` folder.
+
+Start up your game, and the mods should be available immediately. If you run into any issues, please take a look at the [troubleshooting page](/en/usage/troubleshooting), or [join us on Discord](https://discord.quiltmc.org) to ask for support!
diff --git a/src/pages/fr/install/bakaxl.mdx b/src/pages/fr/install/bakaxl.mdx
new file mode 100644
index 000000000..524a5c806
--- /dev/null
+++ b/src/pages/fr/install/bakaxl.mdx
@@ -0,0 +1,42 @@
+---
+title: "Install: BakaXL"
+permalink: /install/bakaxl/
+
+layout: /src/layouts/InstallPage.astro
+platformKey: platform-bakaxl
+website: https://www.bakaxl.com
+---
+
+import Message from "@atoms/Message.astro";
+
+
+ Please note that BakaXL is a launcher primarily designed for the Chinese market - they have done their best to localize the launcher, but if you don't speak Chinese then you may have a hard time reading some of its text.
+
+ If you'd like to contribute to BakaXL's translations, you can do so [on GitHub](https://github.com/BakaXL-Launcher/BakaXL).
+
+
+BakaXL is a launcher designed for Chinese users, with a broad focus on usability and a modern theme. In order to set up and use a Quilt "core", follow these steps:
+
+1. Download and install BakaXL from [their website](https://www.bakaxl.com)
+2. Open BakaXL and agree to install updates (using the button to the bottom-right of the dialog), if any are available
+3. Follow the instructions to set up the launcher and log into your Minecraft profile
+4. Click on the tile that looks like a pentagon to add a new core
+5. Select "Automatically install core", and select the Minecraft version you'd like to use
+6. Click on "Quilt", and select the Quilt loader version you'd like to use
+7. Click on "Install Now"
+8. Click on the "9" icon in the upper left corner to return home
+
+That's all there is to it! You can find your new instance in the **cores** section, by clicking on the circular icon on the bottom-right of the main window.
+
+# Installing Mods
+
+To install mods to your BakaXL core, simply follow these steps:
+
+1. Click on the circular icon on the bottom-right of the main window
+2. Select the core you'd like to add mods to
+3. Click on "Advanced Core Management"
+4. Select "Mods", and click on the second option below "Mods Folder", which will open the `mods` folder in your file explorer
+4. Download the mods you'd like to install, and copy or move them into the folder that just opened
+5. Ensure you have also added the **Quilted Fabric API/Quilt Standard Libraries** bundle, which you can find [on CurseForge](https://www.curseforge.com/minecraft/mc-mods/qsl) or [on Modrinth](https://modrinth.com/mod/qsl)
+
+Start up your game, and the mods should be available immediately. If you run into any issues, please take a look at the [troubleshooting page](/en/usage/troubleshooting), or [join us on Discord](https://discord.quiltmc.org) to ask for support!
diff --git a/src/pages/fr/install/client.mdx b/src/pages/fr/install/client.mdx
new file mode 100644
index 000000000..c8c32cd42
--- /dev/null
+++ b/src/pages/fr/install/client.mdx
@@ -0,0 +1,79 @@
+---
+title: "Installer: Client"
+permalink: /install/client
+
+layout: /src/layouts/InstallPage.astro
+platformKey: platform-client
+website: "https://www.minecraft.net/en-us/download"
+
+hasDownloads: true
+---
+
+import InstallerVersion from "@parts/install/InstallerVersion.astro";
+import MavenInstallerButton from "@atoms/MavenInstallerButton.astro";
+
+Avant de commencer, vous devez vous assurer que vous avez téléchargé une copie du programme d'installation de Quilt.
+
+Le programme d'installation **Universel** fonctionnera sur n'importe quel ordinateur avec Java correctement installé -- mais si vous êtes sous Windows, et que vous préférez simplement utiliser l'installation Java qui vient avec Minecraft, alors vous pouvez utiliser le programme d'installation **Windows**.
+
+Si vous ne savez pas quoi choisir, installez simplement Java (https://java.com/en/download) et utilisez le programme d'installation **Universel**.
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+Une fois que vous avez téléchargé une copie du programme d'installation de Quilt, suivez ces étapes :
+
+1. Si vous ne l'avez pas encore fait, téléchargez une copie du launcher de Minecraft [depuis le site web de Minecraft] (https://www.minecraft.net/fr-fr/download), et installez-le
+2. Si le launcher de Minecraft est ouvert, fermez-le avant de continuer
+3. Trouvez le programme d'installation de Quilt que vous avez téléchargé et exécutez-le
+4. Assurez-vous que vous avez sélectionné l'onglet **Client**
+5. Sélectionnez la version de Minecraft pour laquelle vous souhaitez installer Quilt
+6. Sélectionnez la version du _loader_ de Quilt que vous souhaitez utiliser
+7. Cliquez sur le bouton **Install**
+
+Si vous avez laissé la case **Generate profile**, vous remarquerez qu'une nouvelle installation de Quilt a été créée pour vous. Sinon, vous pouvez cliquer sur l'onglet **Configurations** en haut et en créer une nouvelle, en choisissant la nouvelle installation de Quilt dans le menu déroulant **Version**.
+
+C'est tout ce qu'il y a à faire, installez quelques mods, lancez votre nouvelle installation et amusez-vous bien !
+
+# Installer des mods
+
+Installer des mods est un processus assez simple :
+
+1. Téléchargez les mods que vous souhaitez installer
+2. Ouvrez le Minecraft Launcher et cliquez sur l'onglet **Configurations**
+3. Passez le curseur de votre souris sur l'installation de Quilt à laquelle vous souhaitez ajouter des mods
+4. Cliquez sur le bouton qui ressemble à une icône de dossier
+5. Dans le dossier qui s'ouvre, créez un dossier nommé `mods` s'il n'en existe pas déjà un
+6. Copiez vos fichiers de mods dans le dossier `mods/`
+7. Assurez-vous que vous avez également ajouté la librairie **Quilted Fabric API/Quilt Standard Libraries**, que vous pouvez trouver [sur CurseForge](https://www.curseforge.com/minecraft/mc-mods/qsl) ou [sur Modrinth](https://modrinth.com/mod/qsl)
+
+Lancez votre installation, et les mods devraient être disponibles immédiatement. Si vous rencontrez des problèmes, jetez un coup d'œil à la [page de dépannage](/fr/usage/troubleshooting), ou [rejoignez-nous sur Discord](https://discord.quiltmc.org) pour demander de l'aide!
diff --git a/src/pages/fr/install/curseforge.mdx b/src/pages/fr/install/curseforge.mdx
new file mode 100644
index 000000000..98ccaf76a
--- /dev/null
+++ b/src/pages/fr/install/curseforge.mdx
@@ -0,0 +1,37 @@
+---
+title: "Install: CurseForge"
+permalink: /install/curseforge/
+
+layout: /src/layouts/InstallPage.astro
+platformKey: platform-curseforge
+website: https://download.curseforge.com
+---
+
+import Message from "@atoms/Message.astro";
+
+### Status: Partially Implemented
+
+CurseForge does not currently support Quilt in their launcher, but they've stated they're planning on it. They do, however, support Quilt on the CurseForge website.
+
+Thanks to Claycorp, RedBlue and Yamza for their help, as well as to everyone that supported our [CurseForge Ideas suggestion](https://curseforge-ideas.overwolf.com/ideas/CF-I-2662). We couldn't have gotten this far without you!
+
+# Manual Installation
+
+It is not currently possible to manually install Quilt into a CurseForge instance. Please show your support on the suggestion linked above if you'd like to see CurseForge adding Quilt to their services!
+
+## Workarounds
+
+
+ Please note that the following solutions are maintained by third party developers. We cannot guarantee their efficacy over time -- and, while we believe them to be entirely safe, we can't take responsibility for any issues caused by them.
+
+ **Please remember to back up your worlds if you attempt to use the following solutions on an existing launcher profile!**
+
+
+If you can't wait for the CurseForge launcher to support Quilt, then [kb1000](https://www.curseforge.com/members/kb1000) maintains one possible solution:
+
+1. Create a Forge profile
+2. Add [JumpQuilt](https://www.curseforge.com/minecraft/mc-mods/jumpquilt), which will hijack the Forge loading process to load Quilt instead
+3. Add your mods as usual
+4. Ensure you have also added the **Quilted Fabric API/Quilt Standard Libraries** bundle, which you can find [on CurseForge](https://www.curseforge.com/minecraft/mc-mods/qsl)
+
+We're aware that this isn't an ideal solution for a number of reasons, especially given how mod browsing works in the CurseForge launcher. Please show your support on the suggestion linked above if you'd like to see a better solution!
diff --git a/src/pages/fr/install/gdlauncher.mdx b/src/pages/fr/install/gdlauncher.mdx
new file mode 100644
index 000000000..577b54deb
--- /dev/null
+++ b/src/pages/fr/install/gdlauncher.mdx
@@ -0,0 +1,31 @@
+---
+title: "Install: GDLauncher"
+permalink: /install/gdlauncher/
+
+layout: /src/layouts/InstallPage.astro
+platformKey: platform-gdlauncher
+website: https://gdevs.io
+---
+
+import Message from "@atoms/Message.astro";
+
+### Status: Work In Progress
+
+GDLauncher does not currently support Quilt, but a member of the community has [submitted a Pull Request](https://github.com/gorilla-devs/GDLauncher/pull/1400) that adds Quilt support. If you're interested in seeing Quilt support in GDLauncher, feel free to take a look at that PR.
+
+# Workarounds
+
+
+ Please note that the following solutions are maintained by third party developers. We cannot guarantee their efficacy over time -- and, while we believe them to be entirely safe, we can't take responsibility for any issues caused by them.
+
+ **Please remember to back up your worlds if you attempt to use the following solutions on an existing launcher profile!**
+
+
+If you can't wait for GDLauncher to support Quilt, then [kb1000](https://www.curseforge.com/members/kb1000) maintains one possible solution:
+
+1. Create a Forge profile
+2. Add [JumpQuilt](https://www.curseforge.com/minecraft/mc-mods/jumpquilt), which will hijack the Forge loading process to load Quilt instead
+3. Add your mods as usual
+4. Ensure you have also added the **Quilted Fabric API/Quilt Standard Libraries** bundle, which you can find [on CurseForge](https://www.curseforge.com/minecraft/mc-mods/qsl)
+
+We're aware that this isn't an ideal solution for a number of reasons. Please show your support on the Pull Request linked above if you'd like to see a better solution!
diff --git a/src/pages/fr/install/index.mdx b/src/pages/fr/install/index.mdx
new file mode 100644
index 000000000..81c24fd2d
--- /dev/null
+++ b/src/pages/fr/install/index.mdx
@@ -0,0 +1,22 @@
+import Install from "/src/layouts/Install.astro";
+import Message from "@atoms/Message.astro";
+
+
+
+ Installation directe
+
+
+
+
Launchers
+
+ **Veuillez noter que:** la présence d'un lanceur tiers sur cette page ne signifie pas que le projet Quilt l'approuve. Nous pensons simplement que le choix de l'utilisateur est important !
+
+
+
+ # En attente de support
+
+
+ Les lanceurs de cette liste ne supportent pas Quilt actuellement -- mais quelqu'un leur a demandé de le faire, ou ils y travaillent déjà. Vous pouvez cliquer dessus pour en savoir plus sur leur fonctionnement -- ou pour connaître les solutions de contournement permettant d'installer Quilt en les utilisant, lorsque cela est possible.
+
+
+
diff --git a/src/pages/fr/install/multimc.md b/src/pages/fr/install/multimc.md
new file mode 100644
index 000000000..82eeea0d5
--- /dev/null
+++ b/src/pages/fr/install/multimc.md
@@ -0,0 +1,32 @@
+---
+title: "Install: MultiMC"
+permalink: /install/multimc/
+
+layout: /src/layouts/InstallPage.astro
+platformKey: platform-multimc
+website: https://multimc.org
+---
+
+MultiMC is a launcher with advanced features to allow power users to manage separate instances of Minecraft. To set up a Quilt instance with MultiMC, follow these steps:
+
+1. Download and install MultiMC from [their website](https://multimc.org)
+2. Open MultiMC, follow the setup steps and click on the **Add Instance** button at the top of the window
+3. Fill out the **Name** and **Group** boxes as required
+4. Select **Vanilla** from the list on the left, and pick the version of Minecraft you'd like to use for your instance
+5. Click **OK** to create a new vanilla instance
+6. Right-click on the instance and select **Edit Instance**, or click on it once and select **Edit Instance** from the menu on the right of the window
+7. Select **Version** from the list on the left, and click the **Install Quilt** button in the menu on the right side of the window
+8. Select the Quilt Loader version you'd like to use and click **OK**
+9. Set up the rest of your instance as normal
+
+That's all there is to it! Once you've followed these steps, your instance should be ready to go -- just add your mods and get playing.
+
+# Installing Mods
+
+To install mods to your MultiMC instance, simply follow these steps:
+
+1. Right-click on the instance you'd like to install mods to and select **Edit Instance**, or click on it once and select **Edit Instance** from the menu on the right of the window
+2. Select **Mods** from the list on the left, and drag-and-drop the mod files you've downloaded into the mod list
+3. Ensure you have the **Quilted Fabric API/Quilt Standard Libraries** bundle installed, which you can find [on CurseForge](https://www.curseforge.com/minecraft/mc-mods/qsl) or [on Modrinth](https://modrinth.com/mod/qsl)
+
+Start up your game, and the mods should be available immediately. If you run into any issues, please take a look at the [troubleshooting page](/en/usage/troubleshooting), or [join us on Discord](https://discord.quiltmc.org) to ask for support!
diff --git a/src/pages/fr/install/prismlauncher.md b/src/pages/fr/install/prismlauncher.md
new file mode 100644
index 000000000..f69748490
--- /dev/null
+++ b/src/pages/fr/install/prismlauncher.md
@@ -0,0 +1,35 @@
+---
+title: "Install: Prism Launcher"
+permalink: /install/prismlauncher/
+
+layout: /src/layouts/InstallPage.astro
+platformKey: platform-prismlauncher
+website: https://prismlauncher.org
+---
+
+Prism Launcher is designed to allow users to manage multiple installations of Minecraft at once easily, and provide the power tools an advanced user would need.
+
+To set up a Quilt instance, simply follow these steps:
+
+1. Download and install Prism Launcher from [their website](https://prismlauncher.org)
+2. Open Prism Launcher, follow the setup steps and click on the **Add Instance** button at the top of the window
+3. Fill out the **Name** box as required (you may also fill the **Group** box optionally)
+4. Select **Vanilla** from the list on the left, and pick the version of Minecraft you'd like to use for your instance
+5. Under the **Mod Loader**, select **Quilt** and then pick the Quilt Loader version you'd like to use.
+6. Click **OK** to create a new Quilt instance
+7. Set up the rest of your instance as normal
+
+That's all there is to it! Once you've followed these steps, your instance should be ready to go -- just add your mods and get playing.
+
+# Installing Mods
+
+To install mods to your Prism Launcher instance, simply follow these steps:
+
+1. Right-click on the instance you'd like to install mods to and select **Edit...**, or click on it once and select **Edit** from the menu on the right of the window
+2. Select **Mods** from the list on the left, and click on the **Download mods** button in the menu on the right side of the window
+3. Click on **Download Mods** on the right side of the window, and use the popup to search for and install the mods you'd like to use.
+4. Ensure you have the **Quilted Fabric API/Quilt Standard Libraries** bundle installed, which you can find [on CurseForge](https://www.curseforge.com/minecraft/mc-mods/qsl) or [on Modrinth](https://modrinth.com/mod/qsl)
+
+If you can't find the mod you'd like to install using the built-in search, you can simply drag-and-drop any mod files you've downloaded into the mod list, and Prism Launcher will ensure it's installed properly.
+
+Start up your game, and the mods should be available immediately. If you run into any issues, please take a look at the [troubleshooting page](/en/usage/troubleshooting), or [join us on Discord](https://discord.quiltmc.org) to ask for support!
diff --git a/src/pages/fr/install/server.mdx b/src/pages/fr/install/server.mdx
new file mode 100644
index 000000000..292e36b3f
--- /dev/null
+++ b/src/pages/fr/install/server.mdx
@@ -0,0 +1,74 @@
+---
+title: "Installer: Serveur"
+permalink: /install/server/
+
+layout: /src/layouts/InstallPage.astro
+platformKey: platform-server
+
+hasDownloads: true
+---
+
+import InstallerVersion from "@parts/install/InstallerVersion.astro";
+import MavenInstallerButton from "@atoms/MavenInstallerButton.astro";
+
+Avant de commencer, vous devez vous assurer que vous avez téléchargé une copie du programme d'installation de Quilt. Vous devez également vous assurer que vous avez [installé Java](https://java.com/fr/download).
+
+
+
+
+
+
+
+
+
+
+
+
+## Installation utilisant l'interface graphique
+
+Une fois que vous avez téléchargé une copie du programme d'installation de Quilt, suivez les étapes suivantes :
+
+1. Trouvez le programme d'installation de Quilt que vous avez téléchargé et exécutez-le
+2. Assurez-vous que l'onglet **Server** est sélectionné
+3. Sélectionnez la version de Minecraft pour laquelle vous souhaitez installer Quilt
+4. Sélectionnez la version du _loader_ de Quilt que vous souhaitez utiliser
+5. Sélectionnez l'emplacement où vous souhaitez installer le serveur
+6. Cochez la case **Download server jar**
+7. Cliquez sur le bouton **Install**.
+
+Ceci téléchargera une copie du serveur Minecraft à l'emplacement que vous avez spécifié, et installera Quilt, en fournissant un JAR de lancement pour démarrer le serveur. Une fois que cela est fait, créez un fichier `.bat` (pour Windows) ou `.sh` (pour Mac/Linux), avec le contenu suivant :
+
+```bash
+java -jar quilt-server-launch.jar nogui
+```
+
+C'est tout ce qu'il y a à faire - utilisez le fichier `.bat` ou `.sh` correspondant pour démarrer le serveur pour la première fois, puis arrêtez-le (avec `/stop` ou `ctrl+c`) et configurez-le comme vous le feriez normalement.
+
+## Installation utilisant la CLI
+
+Une fois que vous avez téléchargé une copie de l'installateur de Quilt, vous devez le lancer depuis votre terminal, en remplaçant `INSTALLER_VERSION` et `MINECRAFT_VERSION` si nécessaire :
+
+```bash
+java -jar quilt-installer-INSTALLER_VERSION.jar \
+ install server MINECRAFT_VERSION \
+ --download-server
+```
+
+Ceci téléchargera une copie du serveur Minecraft dans `server/` et y installera Quilt, en fournissant un JAR de lancement pour démarrer le serveur. Une fois que cela est fait, créez un fichier `.bat` (pour Windows) ou `.sh` (pour Mac/Linux), avec le contenu suivant :
+
+```bash
+java -jar quilt-server-launch.jar nogui
+```
+
+C'est tout ce qu'il y a à faire - utilisez le fichier `.bat` ou `.sh` correspondant pour démarrer le serveur pour la première fois, puis arrêtez-le (avec `/stop` ou `ctrl+c`) et configurez-le comme vous le feriez normalement.
+
+# Installer des mods
+
+Installer des mods est un processus assez simple :
+
+1. Téléchargez les mods que vous souhaitez installer
+2. Créez un dossier nommé `mods`, s'il n'en existe pas déjà un
+3. Copiez vos fichiers de mods dans le dossier `mods/`
+4. Assurez-vous que vous avez également ajouté la librairie **Quilted Fabric API/Quilt Standard Libraries**, que vous pouvez trouver [sur CurseForge](https://www.curseforge.com/minecraft/mc-mods/qsl) ou [sur Modrinth](https://modrinth.com/mod/qsl)
+
+Lancez votre installation, et les mods devraient être disponibles immédiatement. Si vous rencontrez des problèmes, jetez un coup d'œil à la [page de dépannage](/fr/usage/troubleshooting), ou [rejoignez-nous sur Discord](https://discord.quiltmc.org) pour demander de l'aide!
diff --git a/src/pages/fr/install/technic.mdx b/src/pages/fr/install/technic.mdx
new file mode 100644
index 000000000..af3b8632d
--- /dev/null
+++ b/src/pages/fr/install/technic.mdx
@@ -0,0 +1,53 @@
+---
+title: "Install: Technic Launcher"
+permalink: /install/technic/
+
+layout: /src/layouts/InstallPage.astro
+platformKey: platform-technic
+website: https://www.technicpack.net
+---
+
+import Message from "@atoms/Message.astro";
+import VersionJson from "@parts/install/VersionJson.astro";
+
+Technic Launcher is a simple launcher, designed to allow users to download, install and play modpacks that have been uploaded to [The Technic site](https://www.technicpack.net/modpacks), either directly or via [Technic Solder](https://solder.io).
+
+As this launcher is not designed to allow you to create custom instances, most users will pick it purely to play an existing modpack. If you want to create your own custom instance, you'll need to create a modpack by hand, following the instructions further down this page.
+
+## Installing a modpack
+
+For most players, this is all you'll need to do:
+
+- Download and install the Technic Launcher from [their website](https://www.technicpack.net)
+- Open Technic Launcher and log into your Microsoft or Minecraft account
+- Select **Modpacks** at the top of the window and install the Quilt-based pack you want to use
+- Select the pack on the left side of the window and click the **Install** button in the lower-right of the window
+- Once the pack has been installed, click the **Play** button in the lower-right of the window
+
+This will allow you to start playing a Quilt-based modpack that someone else has made.
+
+## Creating your own modpack
+
+If you're working on your own Technic modpack, you'll need to provide a `version.json` file. While you'll probably want to try to follow [their official guide](https://www.technicpack.net/article/building-your-own-modpack.7), at a very basic level you'll need to do the following:
+
+- Create a new folder for your modpack
+- Create two folders within -- `bin` and `mods`
+- In the `mods` folder, place the mods you'd like to add to your modpack
+- In the `bin` folder, place a `version.json` that you've downloaded below
+
+Once you've done this, you should be able to upload your modpack via [the Technic Dashboard](https://www.technicpack.net/dashboard). Once you've finished creating and uploading your modpack, you should be able to install it by following the instructions listed at the top of this page.
+
+### Download version.json
+
+
+
+**Note:** You may need to right-click the download button and select **Save Link As** or similar, depending on your browser.
+
+
diff --git a/src/pages/fr/legal/cozy-privacy-policy.mdx b/src/pages/fr/legal/cozy-privacy-policy.mdx
new file mode 100644
index 000000000..faf8e623a
--- /dev/null
+++ b/src/pages/fr/legal/cozy-privacy-policy.mdx
@@ -0,0 +1,110 @@
+---
+permalink: /legal/cozy-privacy-policy/
+title: Cozy Privacy Policy
+description: The privacy policy for the Cozy Discord bots.
+layout: /src/layouts/Page.astro
+---
+
+# Foreword
+
+The following document was created as required by the European Union General Data Protection Regulation (EU GDPR).
+You can find more information about that regulation on [gdpr.eu](https://gdpr.eu/).
+
+This document details what and why data is collected by QuiltMC through the Cozy Discord bots, except "Cozy (Stats)",
+how it is used and how to use your rights related to your data.
+
+QuiltMC ("Us", "We", "Our") is the data controller for the data collected through the Cozy Discord bots.
+
+# Data Collected
+
+## Applications
+
+When you submit an application to join the server, we save your User ID along with some metadata. Your answers aren't
+stored.
+
+We use this data to maintain a list of previous applications that have been submitted by each user, which allows us to
+look them up on Discord when we need to review them.
+
+## Filter Events
+
+When you trigger an automatic filter, we record your User ID and the location of the message that triggered it.
+The message content isn't saved.
+
+We use this data to conduct analytics.
+
+## Threads
+
+If you are designated as the owner of a thread by creating it, or having the current owner transfer it to you,
+your User ID is saved alongside the thread ID.
+
+We use this data to allow you to manage the threads you own.
+
+## Suggestions
+
+### Voting
+
+When you vote positively or negatively, we save your User ID alongside the suggestion and your vote.
+
+We use this data to make sure you can't vote more than once.
+
+### Creating a suggestion
+
+When you create a suggestion, we save your User ID, Username, Avatar Url, Message and whether it was proxied or not.
+
+We use this data to display and keep track of the suggestions. This data can be seen on the public analytics dashboard, without the User ID or Username.
+
+## User Flags
+
+We save three flags about you:
+- Has Used PluralKit: whether you have used PluralKit previously or not. We use that to log new usages of PluralKit for
+review by the moderators.
+- Auto Publish: whether your messages sent in a news channel should be automatically published.
+- Sync Nicknames: whether your nickname should be synced between Quilt guilds.
+
+# Data Retention
+
+Data is retained indefinitely. We do not delete any data unless you request it.
+
+# Data Governance
+
+Database access is limited to the minimum of QuiltMC benevolent workers required to operate the service. We do not share any data with third parties.
+We do not sell any data. Your data isn't shared with any contracted sub-processors.
+
+Data is stored in a country part of the European Economic Area (EEA). Data is encrypted at rest and in transit.
+
+# Access, rectification, erasure, restriction, portability, and objection
+
+Every user is entitled to the following:
+
+**The right to access** – You have the right to request Us for copies of your personal data.
+We may charge you a small fee for this service.
+
+**The right to rectification** – You have the right to request that We correct any information
+you believe is inaccurate. You also have the right to request Us to complete the information
+you believe is incomplete.
+
+**The right to erasure** – You have the right to request that We erase your personal data,
+under certain conditions.
+
+**The right to restrict processing** – You have the right to request that We restrict the
+processing of your personal data, under certain conditions.
+
+**The right to data portability** – You have the right to request that We transfer the data
+that we have collected to another organization, or directly to you, under certain conditions.
+
+**The right to object to processing** – You have the right to object to Our processing of
+your personal data, under certain conditions.
+
+If you would like to exercise those rights, contact us at [privacy@quiltmc.org](mailto:privacy@quiltmc.org).
+We may ask you to verify your identity before processing your request, using a service such as [Aperture](https://aperture.starchild.systems).
+We will respond to your request within 30 days as required by law.
+
+# Changes to the Privacy Policy
+
+We keep this privacy policy under regular review and places any updates on this web page.
+If we do this, we will post the changes on this page and update the "Edited" date at the top of this page.
+
+# Contact
+
+If you have any questions about this privacy policy, please contact us at
+[privacy@quiltmc.org](mailto:privacy@quiltmc.org).
diff --git a/src/pages/fr/legal/index.mdx b/src/pages/fr/legal/index.mdx
new file mode 100644
index 000000000..ecb46af3f
--- /dev/null
+++ b/src/pages/fr/legal/index.mdx
@@ -0,0 +1,19 @@
+---
+permalink: /legal/
+title: Juridique
+description: L'essentiel des aspects juridiques de Quilt.
+layout: /src/layouts/Page.astro
+---
+
+Cette section contient le document juridique de Quilt. Si vous avez des questions,
+veuillez nous contacter à [privacy@quiltmc.org](mailto:privacy@quiltmc.org)
+ou dans le salon `#discord-meta` sur Discord.
+
+# Politiques de confidentialité
+
+Vous trouverez les politiques de confidentialité sur la gauche de cette page ou en dessous :
+* [Politique de confidentialité de Cozy](/fr/legal/cozy-privacy-policy/)
+* [Membership Privacy Policy](/fr/legal/membership-privacy-policy/)
+* [Politique de confidentialité de ModMail](/fr/legal/modmail-privacy-policy/)
+* [Politique de confidentialité de Metricity](/fr/legal/metricity-privacy-policy/)
+* [Non-profit Bylaws](/fr/legal/bylaws/fr/) ([English translation](/fr/legal/bylaws/en/))
diff --git a/src/pages/fr/legal/metricity-privacy-policy.mdx b/src/pages/fr/legal/metricity-privacy-policy.mdx
new file mode 100644
index 000000000..4268b0c22
--- /dev/null
+++ b/src/pages/fr/legal/metricity-privacy-policy.mdx
@@ -0,0 +1,100 @@
+---
+permalink: /legal/metricity-privacy-policy/
+title: Metricity Privacy Policy
+description: The privacy policy for the Metricity Discord bot.
+layout: /src/layouts/Page.astro
+---
+
+# Foreword
+
+The following document was created as required by the European Union General Data Protection Regulation (EU GDPR).
+You can find more information about that regulation on [gdpr.eu](https://gdpr.eu/).
+
+This document details what and why data is collected by QuiltMC through the "Cozy (Stats)" Discord bot
+running [Metricity](https://git.pydis.com/metricity), how it is used and how to use your rights related to your data.
+
+QuiltMC ("Us", "We", "Our") is the data controller for the data collected through the Cozy Discord bots.
+
+# Data Collected
+
+## Messages
+
+We collect the following information about messages sent on the server:
+* Message ID
+* Author ID
+* Channel ID and Thread ID
+* Creation date
+* Whether the message is deleted or not
+
+The message content is **not** collected. Message data is kept after deletion from Discord, for erasure please see [Contact](#contact).
+
+## Users
+
+We collect the following information about users who are on one of our Guilds:
+* User ID
+* Username
+* Avatar image hash
+* Guild avatar image hash
+* Creation date
+* Join date
+* Public Discord flags
+* Whether the user is in the Guild
+* Whether the user is considered as "pending" by Discord
+
+User data is kept after leaving the Guild, for erasure please see [Contact](#contact).
+
+# Data usage
+
+The data is collected to provide statistics and identify bad actors.
+We do not make use of any automated decision making based on this data.
+
+No statistics containing private information will be provided publicly.
+We may use statistics containing private information internally.
+
+# Data Retention
+
+Data is retained indefinitely. We do not delete any data unless you request it.
+
+# Data Governance
+
+Database access is limited to the minimum of QuiltMC benevolent workers required to operate the service. We do not share any data with third parties.
+We do not sell any data. Your data isn't shared with any contracted sub-processors.
+
+Data is stored in a country part of the European Economic Area (EEA). Data is encrypted at rest and in transit.
+
+# Access, rectification, erasure, restriction, portability, and objection
+
+Every user is entitled to the following:
+
+**The right to access** – You have the right to request Us for copies of your personal data.
+We may charge you a small fee for this service.
+
+**The right to rectification** – You have the right to request that We correct any information
+you believe is inaccurate. You also have the right to request Us to complete the information
+you believe is incomplete.
+
+**The right to erasure** – You have the right to request that We erase your personal data,
+under certain conditions.
+
+**The right to restrict processing** – You have the right to request that We restrict the
+processing of your personal data, under certain conditions.
+
+**The right to data portability** – You have the right to request that We transfer the data
+that we have collected to another organization, or directly to you, under certain conditions.
+
+**The right to object to processing** – You have the right to object to Our processing of
+your personal data, under certain conditions.
+
+If you would like to exercise those rights, contact us at [privacy@quiltmc.org](mailto:privacy@quiltmc.org).
+We may ask you to verify your identity before processing your request, using a service such as [Aperture](https://aperture.starchild.systems).
+We will respond to your request within 30 days as required by law.
+
+# Changes to the Privacy Policy
+
+We keep this privacy policy under regular review and places any updates on this web page.
+If we do this, we will post the changes on this page and update the "Edited" date at the top of this page.
+
+# Contact
+
+If you have any questions about this privacy policy, please contact us at
+[privacy@quiltmc.org](mailto:privacy@quiltmc.org).
diff --git a/src/pages/fr/legal/modmail-privacy-policy.mdx b/src/pages/fr/legal/modmail-privacy-policy.mdx
new file mode 100644
index 000000000..d7f99edce
--- /dev/null
+++ b/src/pages/fr/legal/modmail-privacy-policy.mdx
@@ -0,0 +1,107 @@
+---
+permalink: /legal/modmail-privacy-policy/
+title: ModMail Privacy Policy
+description: The privacy policy for the ModMail Discord bot and web interface.
+layout: /src/layouts/Page.astro
+---
+
+# Foreword
+
+The following document was created as required by the European Union General Data Protection Regulation (EU GDPR).
+You can find more information about that regulation on [gdpr.eu](https://gdpr.eu/).
+
+Our ModMail+ instance is contracted to Starchild Systems.
+This document details what and why data is collected by Starchild Systems for QuiltMC,
+how it is used and how to use your rights related to your data.
+
+QuiltMC ("Us", "We", "Our") is the data controller for the data collected by Starchild Systems for QuiltMC.
+
+# Data Collected
+
+## Discord Bot
+
+We collect message content and attachments sent to the ModMail+ instance through Direct Message or by typing inside the thread channel.
+
+We also collect the following information about the sender:
+* Discord ID
+* Discord Username
+* Discord Discriminator
+* Discord Avatar URL
+
+We collect that data to preserve historical data and conduct moderation. The data is persisted across leaving the guild and is essential to the operation of the service.
+
+Attachments are stored inside a Content Delivery Network (CDN) owned by Starchild Systems to preserve data after the thread is closed.
+
+## Web Interface
+
+The web interface doesn't store any personal data.
+
+# Data Retention
+
+Data is retained indefinitely. We do not delete any data unless you request it.
+
+# Data Governance
+
+Database access is limited to the minimum of Starchild Systems employees required to operate the service. We do not share any data with third parties.
+We do not sell any data. Your data isn't shared with any contracted sub-processors other than Starchild Systems.
+
+Data is stored in a country part of the European Economic Area (EEA). Data is encrypted at rest and in transit.
+
+# Cookies
+
+Cookies are text files placed on your computer to collect standard Internet information.
+
+For further information, visit [allaboutcookies.org](https://allaboutcookies.org).
+
+## How do we use cookies?
+
+We use cookies inside the web interface to keep you signed in.
+
+## How to manage cookies?
+
+You can set your browser not to accept cookies, and the above website tells you how to remove cookies from your browser.
+However, in a few cases, some of our website features may not function as a result.
+
+# Access, rectification, erasure, restriction, portability, and objection
+
+Every user is entitled to the following:
+
+**The right to access** – You have the right to request Us for copies of your personal data.
+Starchild Systems may charge you a small fee on Our behalf for this service.
+
+**The right to rectification** – You have the right to request that We correct any information
+you believe is inaccurate. You also have the right to request Us to complete the information
+you believe is incomplete.
+
+**The right to erasure** – You have the right to request that We erase your personal data,
+under certain conditions.
+
+**The right to restrict processing** – You have the right to request that We restrict the
+processing of your personal data, under certain conditions.
+
+**The right to data portability** – You have the right to request that We transfer the data
+that we have collected to another organization, or directly to you, under certain conditions.
+
+**The right to object to processing** – You have the right to object to Our processing of
+your personal data, under certain conditions.
+
+If you would like to exercise those rights, contact us at [privacy@quiltmc.org](mailto:privacy@quiltmc.org)
+or by sending a message to the ModMail+ Discord Bot.
+We may ask you to verify your identity before processing your request, using a service such as [Aperture](https://aperture.starchild.systems).
+We will respond to your request within 30 days as required by law.
+
+# Analytics
+
+We use [Cloudflare Web Analytics](https://www.cloudflare.com/en-gb/web-analytics/) to
+collect anonymous usage statistics of the web interface.
+Cloudflare does not collect or process personal data for Us.
+
+# Changes to the Privacy Policy
+
+We keep this privacy policy under regular review and places any updates on this web page.
+If we do this, we will post the changes on this page and update the "Edited" date at the top of this page.
+
+# Contact
+
+If you have any questions about this privacy policy, please contact us at
+[privacy@quiltmc.org](mailto:privacy@quiltmc.org) or by sending a message to the ModMail+ Discord Bot.
diff --git a/src/pages/fr/mc-patchnotes.mdx b/src/pages/fr/mc-patchnotes.mdx
new file mode 100644
index 000000000..acfd56d7f
--- /dev/null
+++ b/src/pages/fr/mc-patchnotes.mdx
@@ -0,0 +1,28 @@
+import PatchNotes from "@layouts/PatchNotes.astro";
+
+
+
+ This page requires JavaScript to retrieve the Minecraft launcher's patch notes.
+ Please enable it and reload the page to continue.
+
+
+ Missing versions?
+
+
+ If a new version of Minecraft has just released, it may be not be shown here
+ immediately. This is because the patch notes are not always available right away,
+ and may even become available at different times in different regions.
+
+ It should never take more than an hour for a new set of patch notes to appear here.
+
+
+ Minecraft Patch-notes
+
+
+ Select the version you'd like to see patch notes for.
+
+
+
diff --git a/src/pages/fr/sponsors.mdx b/src/pages/fr/sponsors.mdx
new file mode 100644
index 000000000..19d2705a5
--- /dev/null
+++ b/src/pages/fr/sponsors.mdx
@@ -0,0 +1,115 @@
+---
+title: Sponsors
+description: A list of Quilt sponsors, as well as information about our sponsorship process in general
+layout: /src/layouts/Page.astro
+sidebar: false
+---
+
+import site from "@data/Site";
+import Button from "@atoms/Button.astro"
+import SponsorBlock from "@parts/sponsors/SponsorBlock.astro"
+
+This page contains a record of all Quilt sponsorships, past and present, as well as instructions on how to apply to sponsor Quilt.
+
+While Quilt is not (and hopefully never will be) a financially-driven project, sponsors help us to offset our costs, or provide tools or services that would otherwise be inaccessible to us. Additionally, in order to maintain transparency and to try to avoid problems (such as accepting a sponsorship and endorsing a problematic company), we have [a detailed process](https://github.com/QuiltMC/rfcs/blob/master/rfc/0061-sponsorships.md) that we follow when evaluating and accepting sponsorships.
+
+Sponsorships may be endorsed, or non-endorsed. If a sponsorship is currently endorsed, it means that they require an endorsement from us, such as a link on our homepage. Because of this, endorsed sponsors undergo a more thorough vetting process, including a review by the community [on the Quilt forum](https://forum.quiltmc.org/c/quilt/sponsorship/23). Non-endorsed sponsors do not require an endorsement.
+
+## Current Sponsors (Endorsed)
+
+The following sponsors are endorsed by Quilt.
+
+
+Capitol Hosting Solutions are a hosting provider based in Seattle and Australia, with offerings for gaming, dedicated, web, and Discord bot hosting. They provide us with servers to host much of our infrastructure, including the forum, collab wiki, Modmail, and Cozy.
+
+
+ Cloudflare is an Edge Services provider, with offerings including DNS management, static hosting, edge computing, network security and protection, and CDNs. We use Cloudflare to host our website, serve our Maven, and to protect the rest of our infrastructure from attacks.
+
+ Cloudflare provides us with a free Pro plan, which comes with some extra performance and security features, such as image optimisation and more firewall rules.
+
+
+---
+
+## Current Sponsors (Non-Endorsed)
+
+The following sponsors do not require an endorsement by Quilt.
+
+
+ 1Password is a software for managing passwords and other types of sensitive data. They provide us with a free 1Password Team account as part of their [1Password for Open Source Projects](https://github.com/1Password/1password-teams-open-source) program, which we use to safely share credentials and other sensitive data within various teams.
+
+
+
+ Sentry is an open-source error-tracking and performance monitoring service, which we use to monitor parts of our infrastructure for errors and issues. They provide us with a free Business plan on their cloud platform as part of their [Sentry for Open Source](https://sentry.io/for/open-source/) project.
+
+
+---
+
+## Past Sponsors (Endorsed)
+
+The following past sponsors were endorsed by Quilt while we were working with them.
+
+
+ Starchild Systems is an Infrastructure-as-a-Service and Software-as-a-Service company. They hosted the Quilt Forum, Collab Wiki and several of our Discord bots on their infrastructure at no cost to us.
+
+
+---
+
+## Past Sponsors (Non-Endorsed)
+
+The following past sponsors did not require an endorsement from Quilt while we were working with them.
+
+
+ Amazon Web Services (AWS) is a general-purpose cloud-computing company. In Quilt's early days, AWS hosted our Meta, Maven, and emails, and they provided us with credits to offset those costs through their [Promotional Credits for Open Source Projects](https://aws.amazon.com/blogs/opensource/aws-promotional-credits-open-source-projects/) program.
+
+
+
+---
+
+## Sponsoring Quilt
+
+For detailed information on our processes for accepting and handling sponsors, please see the [Sponsorships RFC](https://github.com/QuiltMC/rfcs/blob/master/rfc/0061-sponsorships.md).
+
+If you're an individual that just wishes to support us and help cover our costs, the best way to do so is by donating directly on our [OpenCollective page](https://opencollective.com/quiltmc).
+
+In addition to Endorsed and Non-Endorsed sponsors, there are two types of sponsorship: Financial and Non-Financial. Financial Sponsorships are those that provide direct financial contributions to Quilt through our [OpenCollective page](https://opencollective.com/quiltmc), and non-financial sponsorships are those that provide tools or services to us at a discount, or for free. When offering us a sponsorship, please include whether it is a financial or non-financial sponsorship, as well as if you would like to be endorsed or not.
+
+When deciding whether to accept a sponsorship, we look for sponsors that provide high-quality products at fair and competitive prices, market their products transparently and honestly, and do not discriminate against minorities, have a history of anti-consumer practices, or conduct business in a way that is unsustainable or especially harmful to the environment. For the full list of Sponsorship Guidelines, see the [Sponsorships RFC](https://github.com/QuiltMC/rfcs/blob/master/rfc/0061-sponsorships.md).
+
+A good sponsorship offer should include the following:
+
+* Information about you, the sponsor
+* What the sponsorship is (tools, services or money)
+* Any additional terms of the sponsorship (if applicable)
+* Links to your website, social media etc -- we're more likely to accept your sponsorship if you have a website with lots of details about your offerings
+
+To offer us a sponsorship, please email the Outreach Team at outreach@quiltmc.org. We look forward to hearing from you!
diff --git a/src/pages/fr/staff/index.md b/src/pages/fr/staff/index.md
new file mode 100644
index 000000000..14b472e4a
--- /dev/null
+++ b/src/pages/fr/staff/index.md
@@ -0,0 +1,10 @@
+---
+permalink: /staff/
+title: Ressources du staff
+description: Des documents pour aider les membres de notre staff à faire leur travail.
+layout: /src/layouts/StaffDocument.astro
+---
+
+Cette section du site contient des documents d'orientation à l'intention du staff, répartis par équipes spécifiques auxquelles ils sont destinés. Ils constituent un ensemble de lignes directrices supplémentaires que les membres du staff peuvent utiliser pour guider leur travail, ce qui contribue à l'efficacité et à la cohérence.
+
+Ces documents sont rendus publics ici dans un souci de transparence. Bien sûr, nous sommes toujours heureux de recevoir des suggestions et des commentaires. N'hésitez pas à nous envoyer un message sur Discord et nous discuterons.
diff --git a/src/pages/fr/staff/moderation.md b/src/pages/fr/staff/moderation.md
new file mode 100644
index 000000000..b278de4c7
--- /dev/null
+++ b/src/pages/fr/staff/moderation.md
@@ -0,0 +1,7 @@
+---
+title: Équipe de modération
+description: Documents destinés à aider l'équipe de modération.
+layout: /src/layouts/StaffDocument.astro
+---
+
+Cette section comprend des documents destinés à guider et à soutenir l'équipe de modération de Quilt. Veuillez sélectionner un document dans le menu de gauche (ou caché derrière le bouton en haut si vous êtes sur un appareil mobile).
diff --git a/src/pages/fr/staff/moderation/moderation.mdx b/src/pages/fr/staff/moderation/moderation.mdx
new file mode 100644
index 000000000..a82ed011f
--- /dev/null
+++ b/src/pages/fr/staff/moderation/moderation.mdx
@@ -0,0 +1,107 @@
+---
+title: Moderation
+description: Quilt's standard moderation policy -- a guide for moderation staff.
+
+redirect_from:
+ - /community/moderation
+layout: /src/layouts/StaffDocument.astro
+---
+
+import Message from "@atoms/Message.astro";
+
+This document outlines a basic idea of what's expected of our community team members, and provides some advice for team members that may be in a pinch. For the sake of transparency, this is a public document -- if you have suggestions or feedback, please feel free to contact us (either directly or via `#discord-meta`).
+
+All of our community team members are involved with moderation -- if there are no community moderators around, you can contact a community manager instead.
+
+## Moderation as a Concept
+
+Moderation is, at its core, the front lines of community safety. Community team members are responsible for keeping the members of their community safe, by resolving disputes and removing problematic people from the community.
+
+There are many ways to approach moderation, and they're all effective in different ways. We prefer to take a proactive approach -- addressing issues as early as possible, and preventing problematic people ever from joining the community when we can. For this reason, we encourage our community team members to be active participants in the community as well, joining the other users in discussions and otherwise participating the same way everyone else does.
+
+## Qualities of a Community Team Member
+
+Every community team member has their own personality and thought process, but we do expect a number of things from every team member:
+
+- A relatively active presence in our community, with genuine participation
+- A wish to improve the community and support its members
+- A relatively cool approach to problem users, allowing the team member to deal with the issue rather than engaging problematic mentalities
+- An understanding of (or willingness to learn about) the unique challenges that minority communities are faced with, and a willingness to apply that knowledge practically and consistently to the moderation process
+- A non-judgemental approach to those in differing circumstances -- people with differing (non-harmful) viewpoints, religions, identities, etc
+
+We ask that all community team members pledge to put the needs of the community above their own personal viewpoints. That said, all team members are people and real life comes first -- team members are not expected to sacrifice their quality of life for the sake of the Quilt community.
+
+## Our Hierarchy
+
+
+
+**Note:** All community team members can act as moderators, regardless of their named role. That said, Community Moderators are the people you should contact first if there's a problem -- Community Managers should be contacted only when Community Moderators are unavailable, or when your concerns relate to a Community Moderator.
+
+
+
+While all community team members have equal influence, there are two primary roles:
+
+- **Community Moderators** are responsible for maintaining the safety and welfare of our community members, by enforcing the community policies, aiding in conflict resolution and dealing with problematic users and behaviours. If you have a problem, these are the people you should contact first.
+- **Community Managers** are responsible for the day-to-day administration tasks in our community spaces, by mobilising and supporting the community team, maintaining community spaces and automations, and keeping everything running smoothly. If you have concerns about how the community is run, these are the people you should contact first.
+
+For more information on how the community team is structured and what processes it follows, please read [RFC 7: Community Team](https://github.com/QuiltMC/rfcs/blob/master/rfc/0007-community-team.md).
+
+## Discord Moderation Tools
+
+We currently have a fairly lightweight set of tools for moderation, provided by [Zeppelin](https://zeppelin.gg). This bot provides a set of standard moderation commands, as well as some lightweight automations. Additionally, we make use of [CrossLink](https://panleyent.com/crosslink) to automatically vet and remove links and attachments that are known to be problematic or contain viruses, and a [ModMail bot](https://github.com/kyb3r/modmail) to allow users to contact the community team if they need anything.
+
+When issuing infractions, community team members **must** use Zeppelin's commands. The prefix is `!!`, and community team members can look at [the Zeppelin site](https://zeppelin.gg/docs/plugins/mod_actions/usage) for more information on how these commands work.
+
+There are some other useful commands too, such as `clean` and `search` -- team members should familiarize themselves with Zeppelin's full list of commands as soon as they can.
+
+We also ask that team members familiarize themselves with [Tupperbox](https://github.com/Runi-c/Tupperbox), as there are several people present in our community that make use of it.
+
+## Discord Infraction Policy
+
+When issuing infractions, community team members should bear the following points in mind:
+
+- If the offending behaviour happened in a public channel and was relatively recent, consider running the infraction command directly within the channel -- otherwise, unless they're pre-emptive bans to avoid known problem users, they should be run in the `#discord-meta` channel.
+- Consider the severity of the violation -- lower-tier offenses (such as rule 8 violations) are better met with a temporary mute (assuming the user doesn't listen), whereas more serious offenses such as hate speech and discrimination may be met with a quick ban, depending on the severity.
+- Consider the user's history in our community, and outside it -- do they have a record of previous infractions? Are they usually a prolific, positive member of the community or are they brand new? Are they infamous for causing trouble in other communities?
+- Consider the user's personal circumstances -- do they have any disabilities or social circumstances that may cloud their judgement or give them a less favourable view of the issue at hand? If they're just generally being disruptive, it's often helpful to read past the words they're using and try to understand the root of the point they're trying to make.
+
+## Handling Appeals
+
+All appeals are handled via the **@ModMail** bot. To submit an appeal, users send a private message to **@ModMail** -- this both allows for a timely response (when possible) and for oversight from the rest of the community team during the appeals process.
+
+Users that are banned from Discord community spaces are sent a private message by **@Zeppelin** that includes a link to a special Discord server, which allows banned users to send a private message to **@ModMail** -- since a shared server is required.
+
+The community team is human and mistakes can happen -- but regardless of whether someone submitting an appeal agrees with their infractions, they're expected to approach their appeal with civility and respect. Appeals should address the infraction reason (assuming the user is aware of it).
+
+**Please note:** While the appeals system exists to allow us to rectify mistakes (and as a way for infracted users to come back later and prove that they've grown, understand the issue and are willing to work towards fixing their reputation), the community team still reserves the right to deny appeals for any reason other than infractions made in clear violation of the moderation guidelines. The safety of the users in our community is of utmost importance, and appeals will not be successful if the person submitting an appeal is still considered to be a threat to the safety of our users -- both physical and psychological.
+
+Appeals made for lesser infractions may result in a more significant infraction if the person appealing fails to approach their appeal with respect, or attempts to abuse the community team members or appeals process.
+
+## Health & Safety
+
+All community team members are human, and we care for the health of everyone that contributes to a healthy atmosphere in our community. Team members should always keep the following points in mind:
+
+- **Prioritise your health over community moderation.** Get enough sleep, drink enough water, and take time off if you need it. Nothing is worth burning out over, and it's important that you look after yourself before taking care of the community -- real life always comes first.
+- **Remember that you're a volunteer.** All community team members are here on a voluntary basis, and we don't require a time commitment from any of them. It's up to each individual team member to decide how much time they can spend on the community.
+- **You do not have to handle every situation.** There are multiple community team members in our community, and some of us are more comfortable dealing with some situations than others may be. If you find that a situation is affecting you negatively, causing you to feel emotionally charged or affecting a psychological trigger, feel free to request that another team member handles the situation -- and step away.
+
+It's extremely important that you take care of yourself before you worry about the needs of the community. You cannot effectively moderate unless you're in the right frame of mind.
+
+## General Advice
+
+While every situation is unique and must be dealt with directly, the following tips may aid community team members when things get difficult, or to avoid problematic situations entirely. Remember to look after yourself, and try to approach these situations with a clear mind when possible. Additionally, it helps to remember that our community is Minecraft-related and, even though some community platforms have a minimum age of 13, it's likely that we do have members that are younger than this -- for this reason, it is a **top priority** to remove users that are at risk of endangering any minors.
+
+- **Read and understand the rules.** Read over them a few times, and try to understand the thought process behind them. Refer back to specific rules by number when you issue an infraction.
+- **Get to know the community.** Be present and genuine in discussions, and take part in the community. The users will need to get to know you both as a person and community team member, and this will help to build trust and encourage them to behave themselves. You'll also get to know the active community members, and learn how they communicate and behave.
+- **Do not tolerate discriminatory behaviour.** Everyone has a right to feel safe, and it's your job as a community team member to ensure that our community is a safe one. All hateful and discriminatory behaviour will alienate community members and make them feel unwelcome, and you should be quick to moderate it.
+- **Be ready to de-escalate heated situations.** Everyone has strong opinions, and disagreements will happen -- it's only natural. As a community team member, you should be ready to step in when discussions become too heated, problematic or unhealthy. Encourage users to try to understand each other's viewpoints, and focus on resolving the conflict. If this is not possible then be firm in asking the users to move on from the subject, but empathetic to the users that are getting emotional. Everyone is human, and infractions and channel locks should only be issued as a last resort in these situations.
+- **Be consistent with the rest of the community team.** Our policies are in place for a reason, and the community team needs to be internally consistent to help build trust with the users. Policy-related discourse is fine, but try to keep the timing, messaging and placement appropriate -- in the heat of the moment, it may be best to disagree in an internal channel at first, especially if you're unsure why an action was taken. That said, you're free to use the `#discord-meta` channel -- just like any other community member is.
+- **Be your best self.** We're all human, but community team members are expected to provide a good example of how to behave in our community spaces. Try your best to keep a level head, and consider stepping away from situations that negatively affect you on a personal level.
+- **Make use of your peers.** The rest of the community team is here to support you if you're unsure how to proceed with a situation. However, if you're unable to contact anyone, don't wait around for too long -- sometimes you will have to make a difficult call on your own, and there is often no ideal outcome for a situation.
+- **Consider the composition of the community.** Our community is home to a diverse range of people, spanning various racial, identity-related and sexuality-based groups. We have many members of the LGBT community, and a surprisingly high ratio of plural systems. Additionally, many of our users have been alienated from other spaces in the wider modding community. This should all factor into your decision-making, and you should think about it when evaluating the points people are making.
+
+## Closing Notes
+
+While this document does its best to act as an aid for the community team (and as an insight into how we operate), there's no way a single document can cover everything there is to know. Community team members are expected to learn on the job, and the world is constantly changing -- however, any explicit policies we come up with will be documented.
+
+At the end of the day, everyone in the community (whether they're community team members or not) is human, and we expect everyone to be treated that way. We can all work together to build a safe, friendly, inclusive environment for everyone, and we all have a responsibility to do that -- not just the community team members!
diff --git a/src/pages/fr/staff/outreach.md b/src/pages/fr/staff/outreach.md
new file mode 100644
index 000000000..77d722a41
--- /dev/null
+++ b/src/pages/fr/staff/outreach.md
@@ -0,0 +1,7 @@
+---
+title: Équipe de communication
+description: Documents destinés à aider l'équipe de communication.
+layout: /src/layouts/StaffDocument.astro
+---
+
+Cette section comprend des documents destinés à guider et à soutenir l'équipe de communication de Quilt. Veuillez sélectionner un document dans le menu de gauche (ou caché derrière le bouton en haut si vous êtes sur un appareil mobile).
diff --git a/src/pages/fr/staff/outreach/writing.mdx b/src/pages/fr/staff/outreach/writing.mdx
new file mode 100644
index 000000000..0aefce4ba
--- /dev/null
+++ b/src/pages/fr/staff/outreach/writing.mdx
@@ -0,0 +1,223 @@
+---
+title: Writing Guidelines
+description: Tips and best-practices for writing content on the site.
+authors:
+ - gdude2002
+ - pluie
+ - "[object Object]"
+layout: /src/layouts/StaffDocument.astro
+---
+
+import Message from "@atoms/Message.astro";
+
+import TabBar from "@atoms/tabs/TabBar.astro";
+import TabBarLink from "@atoms/tabs/TabBarLink.astro";
+import TabContent from "@atoms/tabs/TabContent.astro";
+import TabGroup from "@atoms/tabs/TabGroup.astro";
+
+
+
+**This document has completely changed.** As we have migrated from Jekyll to [Astro](https://astro.build), writing documents is now a vastly different process. Please contact [pluie](https://github.com/pluiedev) (`pluie#9105`) or [[object Object]](https://github.com/obj-obj) (`[object Object]#7105`) if you need any help writing new articles and these new guidelines aren't enough. Thanks for your patience!
+
+
+
+{/*
+
+
+
+
+
+
+
+ First tab content
+
+
+
+ Second tab content
+
+
+*/}
+
+Writing work can be tricky at times, and Quilt doesn't have a large group of professional writers on hand for advice. This document is intended to be a set of guidelines, tips, and tricks to use when writing documents, articles, blog posts, and other written content for the site.
+
+## Editors & Setup
+
+Using [Visual Studio Code](https://code.visualstudio.com) or [VSCodium](https://vscodium.com) is recommended. When opening the site with VSCode, you should see a popup in the bottom right asking if you want to install some recommended extensions. If you don't see it, you can also type `@recommended` into the extensions searchbar:
+
+
+
+To view the site while editing a page, you have to install [pnpm](https://pnpm.io/installation).
+TL;DR:
+
+###### Linux
+
+```sh
+curl -fsSL https://get.pnpm.io/install.sh | sh -
+```
+
+###### Windows
+
+```powershell
+iwr https://get.pnpm.io/install.ps1 -useb | iex
+```
+
+After installing, run `pnpm i` and then `pnpm dev`. You should now be able to view the site in your browser at `localhost:3000`. The site will also automatically update if you make any changes to it.
+
+## Spelling, Punctuation & Grammar
+
+This goes without saying, but proper spelling and grammar is fairly important. That said, nobody is perfect and there are tools out there that make everyone's lives easier. The use of one is highly recommended, even if you usually have excellent spelling and grammar -- everyone makes mistakes!
+
+- [LanguageTool](https://languagetool.org) remains one of the best tools available for this, even the free version. VSCode with [the LTeX extension](https://marketplace.visualstudio.com/items?itemName=valentjn.vscode-ltex) -- or IntelliJ IDEA -- is an easy way to use LanguageTool.
+- [Grammarly](https://www.grammarly.com) exists as an alternative, but LanguageTool's open-source approach tends to result in a more trustable tool.
+
+A somewhat formal tone in your writing is also recommended, but there's absolutely no need to completely avoid an informal approach. The site even supports emojis (Meta + .), if that's something you're into. 🥔
+
+It's also worth thinking a little about punctuation -- you can use `-` for a hyphen, with `--` and `---` existing for progressively longer dashes. If you're looking to join to words together (like-this), use a single hyphen. To break apart a sentence -- like this -- use two dashes.
+
+## Front Matter
+
+A front matter block must be placed at the top of every document or page that's written for the site. It takes the form of a block of YAML surrounded by triple dashes (`---`), and should contain _at least_ a `title` and `layout` property.
+
+```yaml
+---
+title: This is the title of the page or blog post.
+layout: /src/layouts/Page.astro
+---
+```
+
+Pages that don't contain a `layout` property in the front matter will be output as plain HTML (no sidebar, no styling, nothing). Below are some front matter properties:
+
+- `layout` -- Layouts are in the `/src/pages` directory. Most of the pages either use `/src/layouts/Page.astro` (for pages, such as About, Community, etc.) and `/src/layouts/Post.astro` (for blog posts). The Install section of the site uses a different set of layouts (`/src/layouts/Install.astro` for the main page and `/src/layouts/InstallPage.astro` for the launcher pages).
+
+- `draft` -- If you're working on something that needs to be committed but not visible to the public on the site, you can set this to `true`.
+
+More information on this can be found in [the Astro documentation](https://docs.astro.build/en/guides/markdown-content).
+
+### Author Information
+
+Author information can be specified using the `authors` property in the front matter:
+
+```yaml
+---
+authors:
+ - person-one
+ - person-two
+---
+```
+
+### Components
+
+To use any components that require importing, you'll need to be in a `.mdx` file instead of a `.md` file. There's no difference between the Markdown in these two filetypes, so you can just rename any existing Markdown file.
+
+#### Messages
+
+`Message` -- this allows you to create a Message, as shown below. Messages are essentially boxes that draw attention to a specific block of text.
+
+
+
+ ##### Example
+
+ ```astro
+ import Message from "@atoms/Message.astro";
+
+
+ This message has no title, but it has the "success" styling.
+
+
+
+ This message has a title, and the "danger" styling.
+
+ ```
+
+
+
+
+ ##### Result
+
+
+ This message has no title, but it has the "success" styling.
+
+
+
+ This message has a title, and the "danger" styling.
+
+
+
+
+
+
+#### Columns
+
+Columns aren't particularly complex. Columns on this site will collapse nicely for mobile users, with the leftmost column showing first. Here's an example to show how to use them:
+
+##### Example
+
+```astro
+
+
+
+ This is column 1.
+
+
+
+
+ This is column 2.
+
+
+
+```
+
+##### Result
+
+
+
+ This is column 1.
+
+
+ This is column 2.
+
+
+
+# Articles, Documents and Pages
+
+When working on non-blog content, it's worth keeping the following points in mind.
+
+## Front Matter (Pages)
+
+For non-blog content, the following front matter properties may be useful:
+
+- `description` -- This is the page's meta description that will be shown in search engines and on social media. If you skip this, then the site's default description will be used instead.
+
+# Blog Posts
+
+As writing blog posts is somewhat different from writing an article or document, you'll need to do the following things **in addition to the requirements for any other type of page**:
+
+- Include a date in the post's front matter.
+- Include author information in the post's front matter, [as detailed above](#author-information).
+- Define an excerpt in your post
+
+For more information on these concepts, please see the following sections.
+
+## Front Matter (Blog)
+
+For blog posts, you need to include a `date` field in the front matter, which should be in a standard ISO format (For example, `2022-05-07 4:30:00 -00:00`). This is required for all blog posts, as the site relies on it for post ordering and to display metadata.
+
+## Excerpts
+
+Excerpts are meant to be a summary of what's in a blog post. **Every blog post must have an excerpt** -- failing to provide one will make the entire post be used as the excerpt, which is definitely not what you want.
+
+Typically, excerpts are generated from the first couple of paragraphs in a post. Using the special HTML comment `` will mark all content above it as the excerpt.
+
+One approach would be to write a summary at the top of an article, mark it as the excerpt and add a horizontal rule to split it from the rest of the page content:
+
+```markdown
+A summary of the post goes here.
+
+
+
+---
+
+The actual post content starts here.
+```
+
+There are many ways to approach this, of course -- it's best left to the creative liberty of whoever's writing the post, so this is just a suggestion.
diff --git a/src/pages/fr/toberfests.mdx b/src/pages/fr/toberfests.mdx
new file mode 100644
index 000000000..7e3f8c1df
--- /dev/null
+++ b/src/pages/fr/toberfests.mdx
@@ -0,0 +1,117 @@
+---
+title: "'Toberfest Contribution Guidelines"
+description: Guide for contributing to Quilt for Hacktoberfest or Modtoberfest
+layout: /src/layouts/Page.astro
+sidebar: false
+---
+
+import site from "@data/Site";
+
+This October, Quilt is participating in two open-source contribution challenges: [Hacktoberfest](https://hacktoberfest.com) and [Modtoberfest](https://modtoberfest.com). If you want to contribute to Quilt as part of these challenges, thank you so much! We created this guide to help you make the best contributions you can, and maximise your chances of them being accepted.
+
+## Using Git and GitHub
+
+While the workings of Git and GitHub are second nature to most developers, this year Hacktoberfest is accepting low or non-code contributions to count toward your total, so this section exists to give a basic overview of how they work, in case they are new to you. This is not meant to be an advanced guide in any way, merely an overview of the basics, so if you are already familiar with commits, branches, pushes, and pull requests, feel free to skip this section.
+
+### Setting up a GitHub account
+
+GitHub is a service that hosts git repositories (that is, folders containing files tracked by git), so that people can easily download and work on them together. We'll get more into how git works later, but the first step is to go to https://github.com/signup and create an account. Once that is complete, click your avatar in the top-right, and click Settings. There are a lot of settings here that you can dig through if you want, but there's only a couple that need to be changed. Click "Email" in the sidebar and ensure that "Keep my email address private" and "Block command line pushes that expose my email" are both ticked. This is to ensure that you don't accidentally leak your email address, as all git commits must include an email address, but with these settings enabled, GitHub will by default give you a public address to associate your commits with, and stop you from accidentally uploading commits that use your personal email.
+
+### Forking a repository
+
+If you find a GitHub repository that you want to contribute to, the first step is to fork it. This will create a copy of the repository that you can control, so that you can safely make your changes without affecting the original repository, before submitting them to be added back to it using a Pull Request (more on that later). Forking a repository is easy, just go to the repository you want to work on, and click the "Fork" button in the top-right. In the next screen, leave everything as default, and click "Create fork". After GitHub thinks for a few seconds, you'll be brought to a copy of the repository that's controlled by you, and your fork will be ready to use.
+
+### Using github.dev to make your changes
+
+Installing and configuring git on your local machine can be a complex process, but if you're not making any complex changes (for example, if you're writing documentation or doing translation), it can be easier to use github.dev, which is a near-full featured version of the Visual Studio Code editor that runs in your browser. All the commits you make are sent directly to GitHub, so there's no need to run git locally. To use github.dev, all you have to do is visit your forked repository and press the `.` key on your keyboard, and you'll be taken to a VSCode instance running in the browser, with your repository opened and ready for editing. To keep following this guide, skip down to "Commits".
+
+### Installing git locally
+
+If you would prefer to work locally, there are several ways you can install git yourself, depending on your operating system:
+
+#### Windows
+
+You can download Git for Windows from https://git-scm.com/download/win
+
+### macOS
+
+Apple include git in their Xcode Command Line Tools, which you can download by opening the Terminal app and typing `xcode-select --install`. Note that this comes with a lot of other tools, which won't do any harm, but may take up space on your computer that you'd prefer they didn't. If you have [Homebrew](https://brew.sh), you can install it by running `brew install git` in the Terminal.
+
+### Linux
+
+If git was not included with your distro, you will almost certainly be able to install it using your package manager of choice.
+
+### Installing GitHub Desktop
+
+Git is designed to be used with the Terminal, but if you're not a developer, that can be intimidating, so instead we will use [GitHub Desktop](https://desktop.github.com) to set everything up for us. There are many text editors and IDEs that come with git features built-in, like Visual Studio Code, which powers github.dev, but we will use GitHub Desktop as it works with almost any text editor that you might want to use. Download it, install it, and use your GitHub name and email to set up git when it asks.
+
+In the screen that next appears, search for your forked repository and click "Clone"
+
+Make sure you're happy with the Local Path of the repository, and click Clone.
+
+
+### Commits
+
+Commits are the fundamental building blocks of git. Each one represents a snapshot in time, and the real power of git comes from the fact that the repository's entire history, from the first commit to the last, is stored within it. With the right knowledge, you can go back to any point in time and see what the repository looked like, and nothing is ever truly lost.
+
+Every time you make a change to the repository, you need to commit that change. Don't worry that you're making too many commits, as they'll all be "squashed" into a single commit when they're added to the main repository. When you make a commit, you need to write a commit summary, and, optionally, a commit description if you feel more detail is required. In GitHub Desktop, commits are on the left-hand side of the window, along with a list of all files that will change in the commit.
+
+Commit messages are conventionally written in present-tense, for example "Update the site information" rather than "Updated the site information". This is because commit messages are not seen as a record of what has been changed, but rather, how the commit changes the repository. While this might be hard to adapt to at first, it's a good habit to develop for when you're working with other people.
+
+It's a good idea to "push" or upload your commits up to GitHub every so often, for example, whenever you take a break from working. This ensures that if you ever lose or somehow damage your local copy of the repository, you still have a relatively up-to-date version that you can fetch from GitHub whenever you need to. In GitHub Desktop, you can click the Push to Origin button at the top of the window to push your changes.
+
+If you're using github.dev, the Commit menu is in the sidebar below the search magnifying glass. There's no need to push your changes, as they'll be automatically sent to GitHub.
+
+
+
+### Branches
+
+Another key concept of git is branches. At its core, a branch is a path of commits that have at some point been split of the main branch (which you could think of as a trunk) and continued on independently. This is useful in situations where you want to make changes, but don't want to put the files on the main branch at risk of damage, so you can create a branch to keep on working without affecting the main one. In the [quiltmc.org repository](https://github.com/quiltmc/quiltmc.org), for example, anything that is committed to the `stable` branch (which is the main one) is automatically published live on the main website, so we always make sure to develop and test new pages or features on other branches, before sending the changes to the main branch.
+
+When making changes to a fork that you intend to send back to the original repository, it is good etiquette to create a branch for yourself to work on, rather than committing to the main branch. To do this in GitHub Desktop, click the "Current Branch" button, click "New Branch", name it, and click "Create Branch". You will be automatically switched to the new branch.
+
+In github.dev, there's a small button in the bottom-left next to the green GitHub text. Click it, and click "Create New Branch" to create a new branch.
+
+
+
+### Pull Requests
+
+The last thing you need to know about Git and GitHub is the concept of Pull Requests. Pull requests are GitHub's system for sending changes between branches, or, more importantly, from a fork of a repository back to the original one. To create a Pull Request, visit your fork on GitHub, click current branch in the top left, and select the branch with your changes to switch to it.
+
+
+
+Then click "Contribute" and then click "Create Pull Request". More information about what you need to include in your Pull Requests can be found further down the page.
+
+And that is the basics of how to use git and GitHub. If you're interested in learning more about how git works, there is an excellent visual tutorial available at https://learngitbranching.js.org. If you get stuck, don't be afraid to ask for help on Discord.
+
+## Finding Something to Contribute
+
+The following Quilt projects are accepting **code** Pull Requests for Hacktoberfest and Modtoberfest:
+
+- [Chasm](https://github.com/quiltmc/chasm)
+- [Developer Wiki](https://github.com/quiltmc/developer-wiki)
+- [Enigma](https://github.com/quiltmc/enigma)
+- [Mappings Hasher](https://github.com/quiltmc/mappings-hasher)
+- [Quilt Loom](https://github.com/quiltmc/quilt-loom)
+- [quiltmc.org](https://github.com/quiltmc/quiltmc.org)
+- [Quilted Fabric API](https://github.com/quiltmc/quilted-fabric-api)
+- [Quiltflower](https://github.com/quiltmc/quiltflower)
+- [Quilt Mappings](https://github.com/quiltmc/quilt-mappings)
+- [Quilt Standard Libraries](https://github.com/quiltmc/quilt-standard-libraries)
+
+In addition, the following Quilt projects are accepting **low or non-code** Pull Requests for Hacktoberfest:
+
+- Developer Wiki (documentation)
+- quiltmc.org (Translation)
+
+After you decide on a repository to contribute to, a great place to start is by looking at the Issues tab for something you think you could help with, unless you already have something in mind. If you find something that you think you can do, please leave a comment stating your intent to work on it, and please clarify any details you're unsure of before starting work. Likewise, if you're attempting something that isn't being tracked in an issue, **please** confirm that it is something that would be beneficial to the project before you start, either by making an issue on GitHub or chatting to the developers on Discord; we'd hate for your work to go to waste! We will not accept contributions that are obviously low-effort or unhelpful, and PRs will be accepted at the sole discretion of the team responsible for the repository.
+
+Once you know what you're going to do, make sure to read the contribution guidelines for the repository, which are usually found either in the README or the CONTRIBUTING.md file. These guidelines will not only give you advice for developing the repository locally, but they often also contain information about the appropriate procedures for submitting contributions, as well as code conventions. Contributions that correctly follow procedures and conventions are likely to be reviewed and accepted far more quickly. Some repositories have other contribution-related files that aren't as obvious, like `ARCHITECTURE.md` in quiltmc.org, so it's always advisable to have a good look around before you begin.
+
+### Pull Requests
+
+After you've finished and tested your work, it's time to submit it as a Pull Request. **All** contributions must be submitted as Pull Requests to be tracked by Hacktoberfest and Modfest, including low and non-code ones.
+
+In your Pull Request title, write a short overview of your changes, with more detail in the description. Please make sure to include if you would like your contributions to count toward Hacktoberfest, Modtoberfest, or both. Remember, well-written Pull Requests make everyone's lives easier, and makes it more likely for your contribution to be reviewed and accepted in a timely fashion.
+
+In case you're unfamiliar with the Pull Request process, it generally goes like this: After you submit your Pull Request, members of the team responsible for the repository that you're sending the Pull Request to will look over your work and let you know of anything they want changed before it can be merged into the main repository. To make any changes to the files Pull Request, just commit them to the branch you used to create the Pull Request, and they'll automatically be added, as long as you remember to push them to GitHub as well.
diff --git a/src/pages/fr/usage/index.mdx b/src/pages/fr/usage/index.mdx
new file mode 100644
index 000000000..ca628c1e1
--- /dev/null
+++ b/src/pages/fr/usage/index.mdx
@@ -0,0 +1,26 @@
+---
+permalink: /usage/
+title: Vue d'ensemble de l'utilisation
+description: Apprenez à utiliser Quilt et à en tirer le meilleur parti.
+layout: /src/layouts/Page.astro
+---
+
+Cette section contient la documentation d'utilisation de Quilt. Elle contient actuellement une petite collection d'informations pour vous aider à tirer le meilleur parti de Quilt et à résoudre les problèmes que vous rencontrez.
+vous aider à tirer le meilleur parti de Quilt et à résoudre les problèmes que vous rencontrez -- nous allons l'enrichir au fil du temps,
+donc si vous avez un problème ou une question qui, selon vous, devrait être traité ici, n'hésitez pas à nous le faire savoir !
+
+## Liens pour les joueurs
+
+- [Installation de Quilt et des mods](/install)
+
+## Liens communautaires
+
+- Discord: [Quilt Project](https://discord.quiltmc.org) (For all topics, including Quilt project work)
+- Forum: [Forum officiel de Quilt](https://forum.quiltmc.org) (Pour tous les sujets)
+
+## Liens pour les développeurs
+
+- [Utilitaire d'importation de Quilt](https://lambdaurora.dev/tools/import_quilt.html) d'Aurora (Informations sur les versions, pour vos projets Gradle)
+- [Wiki de Quilt pour les développeurs](https://modder.wiki.quiltmc.org)
+- [Dépôt Maven de Quilt](https://maven.quiltmc.org)
+- [Modèle de mod Quilt](https://github.com/QuiltMC/quilt-template-mod)
diff --git a/src/pages/fr/usage/troubleshooting.mdx b/src/pages/fr/usage/troubleshooting.mdx
new file mode 100644
index 000000000..4733afba2
--- /dev/null
+++ b/src/pages/fr/usage/troubleshooting.mdx
@@ -0,0 +1,66 @@
+---
+permalink: /usage/troubleshooting
+title: Dépannage
+description: Comment dépanner Quilt en cas de problème ?
+layout: /src/layouts/Page.astro
+---
+
+import Message from "@atoms/Message.astro";
+
+
+
+## Why am I getting an "Incompatible mod set!" error?
+
+There are a few versions of this error, but they all ultimately mean the same thing: You're missing something another mod
+needs to work, or your mods are incompatible with each other.
+
+**Note:** We understand that these error pop-ups are ugly, difficult to read and extremely confusing. While we haven't
+had time to fix this in time for our first beta, we are planning on solving this problem and providing something that
+everyone can understand.
+
+### Missing dependency
+
+The following errors mean you're missing the [Quilt Standard Libraries](https://modrinth.com/mod/qsl) -- please download
+them and add them to your `mods` folder or launcher mod list.
+
+- Dependency for mod 'mod-id' on fabric versions ...
+- Dependency for mod 'mod-id' on quilt\_ ...
+
+Any other dependencies listed similarly are other mods, and you'll need to download them separately and add them to
+your `mods` folder or launcher mod list.
+
+### Incompatible mod versions
+
+If the error specifies that a mod exists but isn't valid for resolution, you have incompatible mod versions. You'll
+need to double-check that all your mods are up-to-date and, if they are, contact the developers behind the mods that
+are causing problems.
+
+### Jar-in-jar resolution error
+
+
+
+If the error you're getting looks something like this, then this is a problem with a mod you're using -- you should
+report it to that mod's developers. The mod you're looking for in this example has been circled in red above for
+clarity -- in this case, the mod would be QuickCarpet.
+
+
+
+
+## My game is crashing. Why is this happening?
+
+If your game is crashing, the most likely cause is a problem with a mod you have installed. It's always worth trying
+to figure out if this is the case, and you can attempt to do so by following these steps:
+
+1. First, take a look at your `latest.log` - you can find this in the `logs/` folder located within your Minecraft
+ profile, which will likely be in your `.minecraft/` by default.
+2. If you notice errors in your log referring to a specific mod, try removing it and see whether you can reproduce the
+ error.
+3. You could also try using a binary search to track down a misbehaving mod - move half of your mods to another folder,
+ and test the other half. If there's no issue in that half, switch to the other one. Continue to split your mods in
+ half and test each half until you've managed to isolate the problematic mod.
+
+If this doesn't help, or you have trouble reading the logs on your own, please feel free to drop into the
+`#quilt-basic-support` channel on [The Quilt Community Discord server](https://discord.quiltmc.org), and we'll try to
+help you out. **Please remember to provide your `latest.log` and any other relevant issue when requesting support!**
+
+
+
+
+
+ 
+
+ 
+
+ 
+
+ 
+
+ 
+
+ 
+
+To view the site while editing a page, you have to install [pnpm](https://pnpm.io/installation).
+TL;DR:
+
+###### Linux
+
+```sh
+curl -fsSL https://get.pnpm.io/install.sh | sh -
+```
+
+###### Windows
+
+```powershell
+iwr https://get.pnpm.io/install.ps1 -useb | iex
+```
+
+After installing, run `pnpm i` and then `pnpm dev`. You should now be able to view the site in your browser at `localhost:3000`. The site will also automatically update if you make any changes to it.
+
+## Spelling, Punctuation & Grammar
+
+This goes without saying, but proper spelling and grammar is fairly important. That said, nobody is perfect and there are tools out there that make everyone's lives easier. The use of one is highly recommended, even if you usually have excellent spelling and grammar -- everyone makes mistakes!
+
+- [LanguageTool](https://languagetool.org) remains one of the best tools available for this, even the free version. VSCode with [the LTeX extension](https://marketplace.visualstudio.com/items?itemName=valentjn.vscode-ltex) -- or IntelliJ IDEA -- is an easy way to use LanguageTool.
+- [Grammarly](https://www.grammarly.com) exists as an alternative, but LanguageTool's open-source approach tends to result in a more trustable tool.
+
+A somewhat formal tone in your writing is also recommended, but there's absolutely no need to completely avoid an informal approach. The site even supports emojis (Meta + .), if that's something you're into. 🥔
+
+It's also worth thinking a little about punctuation -- you can use `-` for a hyphen, with `--` and `---` existing for progressively longer dashes. If you're looking to join to words together (like-this), use a single hyphen. To break apart a sentence -- like this -- use two dashes.
+
+## Front Matter
+
+A front matter block must be placed at the top of every document or page that's written for the site. It takes the form of a block of YAML surrounded by triple dashes (`---`), and should contain _at least_ a `title` and `layout` property.
+
+```yaml
+---
+title: This is the title of the page or blog post.
+layout: /src/layouts/Page.astro
+---
+```
+
+Pages that don't contain a `layout` property in the front matter will be output as plain HTML (no sidebar, no styling, nothing). Below are some front matter properties:
+
+- `layout` -- Layouts are in the `/src/pages` directory. Most of the pages either use `/src/layouts/Page.astro` (for pages, such as About, Community, etc.) and `/src/layouts/Post.astro` (for blog posts). The Install section of the site uses a different set of layouts (`/src/layouts/Install.astro` for the main page and `/src/layouts/InstallPage.astro` for the launcher pages).
+
+- `draft` -- If you're working on something that needs to be committed but not visible to the public on the site, you can set this to `true`.
+
+More information on this can be found in [the Astro documentation](https://docs.astro.build/en/guides/markdown-content).
+
+### Author Information
+
+Author information can be specified using the `authors` property in the front matter:
+
+```yaml
+---
+authors:
+ - person-one
+ - person-two
+---
+```
+
+### Components
+
+To use any components that require importing, you'll need to be in a `.mdx` file instead of a `.md` file. There's no difference between the Markdown in these two filetypes, so you can just rename any existing Markdown file.
+
+#### Messages
+
+`Message` -- this allows you to create a Message, as shown below. Messages are essentially boxes that draw attention to a specific block of text.
+
+