Title: Add Table of Contents to README for easier navigation

[durdana3105]

🔍 Have You Searched Existing Issues?

• I have searched the existing issues to avoid duplicates

📝 What's wrong with the existing documentation?

Description:
The current README is very detailed and contains multiple sections, including Overview, Vision, Key Features, Technologies Used, Installation, Troubleshooting, Contribution Guidelines, License, and more. However, it lacks a Table of Contents, which makes it harder for users and contributors to quickly navigate to specific sections.

Proposed Solution:
Add a Table of Contents at the top of the README.
Make it clickable, linking to all major sections such as:

Overview
Vision
Why SaralSeva
Mission
Live Demo
Key Features (Citizen, Employee, Admin)
Technologies Used
Installation and Setup
Troubleshooting
Contribution Guidelines
Code of Conduct
License
Stargazers & Forkers

Benefit:
Improves readability and user experience.
Helps new contributors quickly find relevant information.

Label Suggestion: enhancement, documentation, GSSoC, wocs

Assign to me, i'll work on it

📎 Supporting Material

No response

🙌 Contributor Checklist

• I have reviewed the existing documentation
• I agree to follow this project's Code of Conduct
• I am a GSSOC'25 contributor
• I want to work on this issue

[github-actions]

Thank you for raising this issue!

We'll review it as soon as possible. We truly appreciate your contributions! ✨

Meanwhile make sure you've visited the README.md, CONTRIBUTING.md, and CODE_OF_CONDUCT.md before creating a PR for this. Also, please do NOT create a PR until this issue has been assigned to you. 😊

[Muhammad0407]

Hello, I am interested in working on this issue. It appears unassigned.
Could you please assign it to me so I can start working on it?

[durdana3105]

Hello, I am interested in working on this issue. It appears unassigned. Could you please assign it to me so I can start working on it?

I have raised this issue. if you want to get assigned can you please raise your own issue
thankyou.

[Muhammad0407]

*Subject:* Clarification Regarding PR #350 from a Different GitHub Account *Body:* Hello eccentricoder01, I wanted to inform you that the pull request #350 “Add Table of Contents to README for easier navigation” was submitted from my *secondary GitHub account(MuhammadLuqman0407)*. My primary account (Muhammad0407) is currently experiencing some authentication issues, which is why I used this other account temporarily. Please feel free to review and compare the changes. I apologize for any confusion caused and appreciate your understanding. Thank you for your time and consideration. Best regards, Muhammad Luqman

…

On Tue, Dec 2, 2025 at 8:51 PM Durdana Sultana ***@***.***> wrote: *durdana3105* left a comment (eccentriccoder01/SaralSeva#350) <#350 (comment)> Hello, I am interested in working on this issue. It appears unassigned. Could you please assign it to me so I can start working on it? I have raised this issue. if you want to get assigned can you please raise your own issue thankyou. — Reply to this email directly, view it on GitHub <#350 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/BYZ5Y6AU4AMM5HSB7UBKSCL37WYPTAVCNFSM6AAAAACMGJ74GKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTMMBSG4ZDONBXGM> . You are receiving this because you commented.Message ID: ***@***.***>

[eccentriccoder01]

@durdana3105 You already have one issue #349 raised regarding the README. Kindly do all your changes by linking that issue in a single pull request if it is assigned to you based on the sample asked from you. Thanks!

[Muhammad0407]

I fixed the issue and pull the request

…

On Thu, Dec 4, 2025, 11:54 PM Sagnik Chakraborty ***@***.***> wrote: *eccentriccoder01* left a comment (eccentriccoder01/SaralSeva#350) <#350 (comment)> @durdana3105 <https://github.com/durdana3105> You already have one issue #349 <#349> raised regarding the README. Kindly do all your changes by linking that issue in a single pull request if it is assigned to you based on the sample asked from you. Thanks! — Reply to this email directly, view it on GitHub <#350 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/BYZ5Y6DJDUMOOF4B5GZJXRL4AB7PLAVCNFSM6AAAAACMGJ74GKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTMMJTHA3TGNJVHE> . You are receiving this because you commented.Message ID: ***@***.***>