Aller au contenu

Engagement

This page describes why we committed to open source, how we support culture through exhaustive genre cartography and community-owned data, and how we think about environmental impact for the public site you are browsing.

Open source

We chose open source so genre data, software, and project history stay inspectable, reusable, and community-owned. Proprietary silos make it hard to verify claims or build on each other’s work; public repositories and licenses let anyone audit, fork, and improve the ecosystem without asking permission from a single gatekeeper.

That choice also shapes how we collaborate: issues and roadmaps in the open, contributions reviewed on their merits, and documentation that lives next to the code. The BehindTheMusicTree organization on GitHub is the hub; Contribuer explains how to take part.

Culture

Discover culture through exhaustive genre cartography. We treat the map of genres as a living chart: the more complete and precise it is, the easier it becomes to explore how music travels, splits, and reconnects across places and eras. Breadth and depth in that cartography are how listeners and researchers actually find their way into real cultural context—not only a handful of familiar labels.

Keep it crowd-sourced so communities hold the power. The reference is built in the open: proposals, review, and debate happen where contributors can see them. That shifts agency toward the people who live the music—scenes, archivists, educators, and enthusiasts—instead of locking decisions inside a single proprietary product.

Represent every culture—established and emerging. When the map is community-owned and ambitious in scope, widely known traditions sit alongside emerging and local forms that rarely get a fair slot in closed catalogs. The goal is a cartography where each culture can show up with the nuance it deserves, including what is still taking shape today.

Contribuer outlines how to take part in that map; Projets links the tools that turn shared data into discovery in practice.

Environnement

We try to follow principles aligned with sustainable web design: lean delivery, efficient runtime, durable information architecture, and honest measurement—so the site stays fast, maintainable, and transparent about its footprint.

The Website Carbon calculator estimates emissions per page view (methodology aligns with common sustainable web design models). The badge below is the same component as in the site footer; on the live site it reflects this page.

Their API may be unavailable, so the badge may show Unavailable or No Result even when their website still has a report for this site—you can view this site’s report on Website Carbon.

Measuring CO2Website Carbon

Ce que nous faisons deja

  • Next.js (App Router) with server-first pages and optimized assets via next/image and next/font (subset fonts).
  • Tailwind CSS for lightweight styling instead of large unused style bundles.
  • Shared UI via organization packages so we avoid duplicating heavy frontends across every repo.
  • Website Carbon in the footer and in this Environment section: a public estimate of this page’s carbon impact (see Website Carbon).
  • Accessibility basics that also reduce friction: skip link to main content and a clear main landmark.
  • Deployment on Vercel with edge-friendly delivery for production traffic.

Pistes d'amelioration

  • Define and revisit performance budgets (e.g. Core Web Vitals and JavaScript weight on key routes) as the site grows.
  • Keep heavy dependencies scoped to the pages that need them (for example, rich code highlighting only on project pages that show snippets).
  • Periodically review images, embeds, and third-party scripts so each addition stays justified.
  • When we have verified data, document hosting and grid-carbon context (renewable share, region) alongside calculator estimates.
  • Continue favoring clear structure and copy over decorative weight—fewer bytes per meaningful visit.

Questions ou suggestions ? Contactez-nous.