Website / UI
This track works on the RideScore DC website: the map people use to explore street scores, and the route survey where riders tell us how a ride felt. You can improve what's there, fix rough edges, or build something new. Web developers, designers and mapping enthusiasts are all welcome.
These projects use the RideScore DC website repository and the develop branch. You can see the current site at dev.ridescoredc.com.
What it's built with
- Frontend: HTML and JavaScript with MapLibre GL JS, served by Vite during development.
- Backend: a PostGIS database, a Martin tile server for the map, a FastAPI API for the survey, and nginx.
Which setup do I need?
| If you're working on… | Use | Go to |
|---|---|---|
| Pages, map styling, the survey's look and flow, a landing page or tutorial | Front-End only. Runs on your machine, and uses our shared server for map data | Front-End Developer Guide |
| The API, database, storing new survey answers, or what data the map carries | Full Stack. Everything runs on your machine, using Docker | Full Stack Developer Guide |
Most projects only need Front-End. On Windows, start with the Windows WSL guide.
How to use these pages
- Setting up: Windows WSL → Front-End or Full Stack Developer Guide
- Understanding the site: Schematic → Website Repository Layout → The Data
- Doing the work: Mini-project Ideas → Making Website Changes, which covers submitting a pull request