Investing resources where it matters

Apr 27, 2026 - 4 min read

Biome Core Team, Biome Maintainers

Biome is a project solely driven by passionate volunteers that want to improve the web ecosystem with new ideas, teach the fundamentals of the different web technologies, and have fun coding.

Since the project started a few years ago, Biome has gone a long way with amazing milestones. Among them:

Won the Prettier Challenge in a matter of weeks.
Won the OS Awards in the Productivity Booster category.
Received a total of ~75k USD from individuals and companies and distributed ~40k USD to Core team members.
Created and shipped a TypeScript inference system that doesn’t require the TypeScript compiler, thanks to the collaboration with Vercel.
And, hopefully, saved a lot of CI time among our users!

The project evolves and grows thanks to the feedback and contributions of our community, which means your voice and opinions can shape the roadmap of the project.

Among the feedback received by the community, we saw a recurrent pattern: difficulty in grasping certain parts of our documentation.

The documentation swings

Shortly after Biome was launched, we started to cement some important concepts as part of our core values, like the rule pillars. Enforcing this framework made sure that lint rules were informative and actionable.

On the other hand, we shipped many other features that didn’t have an established value nor framework, and after a while their documentation fell short: unclear concepts, missing information, information too technical and lack of examples.

Two big, clear examples:

After the launch of GritQL plugins, we have received many reports of users that couldn’t find good examples, or at least a way to easily introduce users to the concept. All we did was to redirect the users to the GritQL website.
Monorepo was another feature that users asked for a while, and even though we tried to provide examples and explanation, some users struggle to understand the right behavior of the feature. Some other users rightfully flagged that some information is missing, leaving some holes in how the feature is supposed to work in some cases.
The documentation of the organizeImports, when shipped, was very technical and too focused on how the feature worked, and it wasn’t written for the end-user.

So while we delivered something of good quality from one hand, on the other hand, we couldn’t provide such quality on other parts of the project.

We want to invest in good documentation

As of today, I am very happy to announce that the Biome project enters into a collaboration with Sarah Rainsberger and Yan Thomas!

Sarah and Yan are the main reasons why Astro docs are so good, and why Astro has the highest satisfaction rate among the web frameworks. They are a rock star team and come with my highest recommendation.

Sarah has been working with Astro for over four years; she fostered a very welcoming community and taught a lot of people how to help others. She was also one of the MCs at ViteConf together with patak. She also spoke at ViteConf 2025, explaining how meaningful contributions often come from the docs.

Yan, like Sarah, has been working with Astro for at least three years. He’s the creator and maintainer of Lunaria, a set of tools to track and improve the localization of your website. Websites such as Biome, VitePress and Tauri use it. Every team would be lucky to have him, as he’s great at writing good docs, very user-centered and clear. I learnt a lot from his hawk-eyed reviews!

In this collaboration, Sarah and Yan will work together to improve many aspects of the documentation. Among them:

Improve the overall communication of the Biome documentation, make it more user-centric where necessary.
Bring their expertise and share it with the Biome community.
Create an internal framework (guidelines, tips, rules, etc.) for the Core team and contributors.

The whole team is very excited by the initiative, and I am sure that maintainers, contributors and end users will see the benefits very soon!