How krakinme/gla-leaderboard works
Project type and purpose
• The frontend lives under a frontend/ directory (HTML, JS, CSS), and there is a Node.js entry point (index.js) at the root with a package.json, so it’s likely a Node.js-based backend that serves both static assets and dynamic data for a leaderboard.
• The various data_*.json files and details_* directories suggest that the app reads from flat-file JSON and text sources to populate leaderboard entries.
File structure
Top-level directories and files:
• frontend/ – contains index.html, index.js, and styles.css.
• admin.html – a standalone admin UI page for uploading or viewing raw data.
• data_January.json, data_Second.json, data_September.json – JSON data sources for different time periods.
• details_January/, details_Second/, details_September/ – beneath each, plain text files (day.txt, mobno.txt, name.txt, roll.txt, sections.txt, urls.txt) hold granular data fields.
• index.js – Node.js server script.
• package.json – lists dependencies and scripts.
Architectural patterns:
• MVC-light: the Node.js script likely acts as the controller, file system + JSON serve as the model, and the HTML/JS frontends are the views.
• Static-file and dynamic-data hybrid: a single service (Express or HTTP server) handles both.
README for additional insights
• README only states project title and its purpose (“GLA-LeaderBoard for TBPPP”) without deep architectural notes, so we rely on the file tree for details.