what is docs fr?

This repository contains the source files for the documentation website at docs.futureagi.com, which explains how to use Future AGI's products. If you're a developer or user trying to figure out how to work with their tools, this is the repo where those help articles, guides, and reference pages live. The published site is what you'd normally read, but the repo holds the underlying content and code that generates it. The docs are built with Astro, a framework for creating fast websites, combined with MDX (a format that lets you write normal text alongside interactive React components) and Tailwind CSS for styling. Each documentation page is a file whose location on disk maps directly to its URL. There's a scaffold script that creates a new page and automatically adds it to the sidebar navigation. The project also includes a link-checking tool so contributors can catch broken internal links before publishing. When changes are merged to the main branch, the site deploys automatically. The main audience here is contributors, people who want to fix a typo, clarify a confusing section, add an example, or write an entirely new guide. Future AGI seems to be an AI evaluation platform, so the documentation likely covers topics like running evaluations on AI models, measuring performance, and related workflows. A product manager exploring the platform, a developer integrating it, or a technical writer helping improve the docs would all be in the right place. The README is thorough about the contribution process, with a clear workflow from forking through review to deployment, plus style guidelines and writing conventions. What stands out is the thought put into making contributions approachable. There's a style guide with concrete rules (use "you," lead with working examples before explanation, start headings at a specific level), a scaffold script that handles the plumbing of adding a page, and an automated link auditor. The branching model is straightforward: work happens on feature branches, merges go to dev for integration, and then flow to main for the live site.