Updated README.md

[ashmittt08]

Issue Title :

• Info about the related issue (Aim of the project) :
• Name:
• GitHub ID:
• Email ID:
• Identify yourself: (Mention in which program you are contributing. Eg. For a WoB 2024 participant, it's WoB Participant)

Closes: #issue_number that will be closed through this PR

---

Snippet Details 📃

• Snippet Name: <snippet_name>
• Category: (e.g., strings, numbers, files)
• Function Name: <function_name>

Summary of Changes

1. Added badges for version, build status, license, contributors, and issues to the top of the README.
2. Improved the "Table of Contents" by adding sub-sections and linking to specific sections.
3. Added a new "Quick Start" section for users to immediately see how to use the package.
   4)Updated the "Features" section with emojis for better readability and added clarity for each feature.
   5)Added a "Why Use PySnippets?" section to highlight the benefits of the package.
   6)Created a "Roadmap" section to outline upcoming features and future development plans.
4. Maintained clear code examples and explanations throughout the document.

Code Changes

• Documentation update

Example Usage

python

PySnippets - A Python Package for Reusable Code Snippets

---

Type of Change ☑️

What sort of change have you made:

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Code style update (formatting, local variables)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• This change requires a documentation update

---

How Has This Been Tested? ⚙️

1. Verified that all markdown links in the "Table of Contents" lead to the correct sections.
2. Checked that badges load correctly and display accurate information.
3. Reviewed the content for clarity and ensured it improves user navigation and understanding.

---

Checklist ☑️

• [x ] My code follows the guidelines of this project.
• [x ] I have performed a self-review of my own code.
• I have commented my code, particularly where it was hard to understand.
• [x ] I have made corresponding changes to the documentation.
• [ x] My changes generate no new warnings.
• I have added tests that prove my fix is effective or that my feature works.
• Any dependent changes have been merged and published in downstream modules.

[github-actions]

👋 Thank you for opening this pull request! We're excited to review your contribution. Please give us a moment, and we'll get back to you shortly!

Feel free to join our community on Discord to discuss more!

[UTSAVS26]

@ashmittt08 who told you to work on this issue? I am not merging it, as said I have assigned it to some other contributor check once before raising PR #8.

[ashmittt08]

it is showing no assignees

[UTSAVS26]

Check it again I have assigned the issue to Yash.

[UTSAVS26]

you have cleary assigned me this above

I don't assign it to you but approve the changes the changes you made.