Skip to content
WeDanceDocs
WeDance docs
AGPL-3.0

The dance community platform, built in the open

WeDance helps dancers find classes, socials and festivals city by city, the teachers, venues and organisers behind them, and who else is going. The whole app is open source under the GNU AGPL-3.0.

View on GitHub Run it locally Contribute
database tables
70database tables
tRPC procedures
270tRPC procedures
user stories mapped
180user stories mapped
documented components
14documented components

Counted from the code at build time.

Explore the docs

Design system

Tokens, components and patterns behind every WeDance screen, with live examples.

Open

Architecture

Generated from the code on every build, so it never drifts.

Governance

How the WeDance organisation decides: the org's living docs, on org.wedance.vip.

org.wedance.vip

Open metrics

Our real usage numbers on a public dashboard, and exactly what we track.

Open

Quick start

Bun, Node.js and Docker are all you need. The full guide sets up a local database so you never touch production.

bash
git clone https://github.com/razbakov/wedance-2026.git
cd wedance-2026
bun install
cp .env.example .env      # then point DATABASE_URL at a local Postgres
bun run dev               # http://localhost:3000

Read the full quick start →

How to contribute

Code, design, docs and bug reports are all welcome.

  1. 1

    Find or open an issue

    Bugs and ideas live in GitHub Issues. Say what you want to change before a big piece of work.

  2. 2

    Branch from main

    Fork the repo, create a branch, keep the change focused on one thing.

  3. 3

    Run the checks

    bun run test runs the unit tests, including the design-system guardrails.

  4. 4

    Open a pull request

    Against main, with what changed and why. Screenshots for anything visible.

The details — branch names, commit style, which tests to run — are in CONTRIBUTING.md. Everyone taking part follows the Code of Conduct.

Report a problem

Something broken or confusing, in the app or in these docs?

Open a GitHub issue

The report button sends a screenshot of this page along with your note — no account needed.