[Chore]: Refactor standalone GitHub Pages leaderboard into modular assets

[udaycodespace]

Summary

Refactor the standalone GitHub Pages leaderboard by separating its HTML, CSS, and JavaScript into dedicated files to improve maintainability, readability, and future enhancements.

Area

Frontend

Details

What needs to be done?

• Extract all inline CSS from index.html into index/css/style.css.
• Extract all inline JavaScript into index/js/script.js.
• Create an index/images/ directory for leaderboard-specific assets (icons, banners, future images, etc.).
• Update index.html to reference the external stylesheet and script.
• Ensure the page continues to work correctly on GitHub Pages with no functional or visual regressions.

Details

The current index.html contains all HTML, CSS, and JavaScript in a single file, making it difficult to maintain and review.

Refactor the standalone leaderboard into a modular structure:

index.html
index/
├── css/
│   └── style.css
├── js/
│   └── script.js
└── images/

The leaderboard is independent of the React application under frontend/, so these assets should remain isolated from the application source code.

Acceptance Criteria

• index.html contains only the page structure.
• All styles are moved to index/css/style.css.
• All JavaScript is moved to index/js/script.js.
• index/images/ is created for leaderboard assets.
• All asset paths work correctly after refactoring.
• No UI, animation, or functionality changes.
• GitHub Pages deployment continues to work without errors.

Notes

• This is a refactoring/maintenance task only.
• No redesign or feature additions should be introduced.
• Preserve the existing UI, animations, responsiveness, and functionality.
• Keep the folder structure clean and scalable for future leaderboard enhancements.

[anshika-guleria]

Maybi work on it under ecsoc26

[anshika-guleria]

/assign

[github-actions]

@anshika-guleria, since this issue was opened by someone else, please comment with your approach along with /assign.

Example:
/assign I will reproduce the issue locally, trace the affected component flow, and submit a tested fix.

[udaycodespace]

/assign

I have already assigned to you! You can start working on it