The finished dashboard in miniature, with a numbers audit
This is a small version of the dashboard, in one script, because the preview cannot run the Vite project (Topic 4.1): it keeps the KPIs, the rides line and the top stations, and adds an audit. The whole project, with React, live status, the map and the story, is in the files of Phases 4 to 17. Run the same kind of audit against your real dashboard before you publish.
Put every part of the Lumen dashboard together, check it against a checklist from Phase 0 to Phase 17, point it at your own cloud bucket by changing one line, build it for production and publish the result. Then see where to go next.
Change the code and press Run (Ctrl+Enter). Predict what will happen first, then break it on purpose and read what changes. Your edits are saved and match the lesson page.
Ready for more? This phase has 5 hands-on exercises with automatic checks.
Practice questions
Write the code in the editor, run it, then open the model answer to compare.
Write the three lines you would add to the README so that a new hire can change the data, run the tests and publish.
Add a post-build script to package.json named check that runs the tests and the build, and explain what it protects against.
Write a cors.json that allows GET only from https://dashboard.example.com, and explain when you would prefer it to *.
Explain it without notes
How do you move the dashboard's data to your own bucket, and what must be set on the bucket?
What does npm run build produce, and how do you check it before publishing?
Why must keys never be in frontend code, and what do you do for private data?
What would you build next, and why?
Preview
Console
Nothing logged yet.Expected console output
PASS total rides is 933,651
PASS quietest day is 2025-08-14 with 439
PASS busiest day is 2025-07-18 with 4,380
PASS station-month adds up to daily.csv
PASS 25 stations
PASS top station is Quay with 58,584
PASS no NaN in any attribute