Contributions Page fixed

[Samruddhi0857]

🔖 PR Title:

Fixed contribution page path issue

---

📄 Description:

This PR fixes the incorrect navigation/path for the contribution page.
Also added that if github API fails get data from leaderboard.md

• Bug Fix ✅

---

🧑‍💻 What changes were made?

• Corrected the contribution page path in routing/navigation.
• Updated related links to ensure proper redirection.
• Verified that the contribution page is now accessible without errors.

---

💡 Tech Stack Used:

• HTML / CSS / JavaScript

no. of file changed : 7

[vercel]

@Samruddhi0857 is attempting to deploy a commit to the vaibhavbabele's projects Team on Vercel.

A member of the Team first needs to authorize it.

[github-actions]

👋 Hi @Samruddhi0857, thank you for opening this Pull Request!
🔧 Please ensure the following:

• ✅ Resolve any merge conflicts, if they exist.make sure you have updated your local repo to avoid conflicts. and solve in your local repo. do not solve in github editor.try to solve in your local repo in vs code or any other editor.
• 🧾 Clearly mention the issue number you are solving (e.g., Fixes #issue_number).
• 📎 Please update your PR description if anything is unclear or incorrect.
• 📷 Attach a screenshot or screen recording of your fix.
• 💬 Kindly share the PR link in the Discord server manually for better tracking.
• if follow the guidelines and fit to project then label according to pr otherwise close the pr.

Happy Contributing! 🚀

[Samruddhi0857]

@VAIBHAVBABELE do check!

[github-actions]

⚠️ Merge Conflict Detected!
Hi @Samruddhi0857, your pull request currently has a merge conflict with the base branch. Please resolve the conflict so your PR can be merged.
---
## How to Resolve a Merge Conflict (Step-by-Step)
1. Checkout your PR branch:
bash git checkout main

  2. **Fetch the latest changes from the main branch:**
     ```bash
     git fetch origin
     git pull origin main
     ```
  
  3. **Git will show conflict markers in files with conflicts. Open those files, and manually edit them to resolve the differences. Conflict sections look like:**
     ```
     <<<<<<< HEAD
     Your changes
     =======
     Changes from base branch
     >>>>>>> main
     ```
  
  4. **After resolving the conflicts, mark them as resolved:**
     ```bash
     git add <file(s)-you-resolved>
     ```
  
  5. **Commit the resolution:**
     ```bash
     git commit -m "Resolve merge conflict"
     ```
  
  6. **Push your updated branch:**
     ```bash
     git push origin main
     ```
  
  ---
  
  🔗 [GitHub Docs: Resolving merge conflicts](https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/addressing-merge-conflicts/about-merge-conflicts)
  
  If you need any help, please ask your mentors by replying here!
  
  ---
  
  *This is an automated message to help you resolve merge conflicts and get your PR ready for review. Thank you!*

[Samruddhi0857]

@VAIBHAVBABELE @neeraj1907 plz approve and run workflows, I have resolved the conflicts