📝[Docs](readme): improve README with flowchart and clarity enhancements

[Akshayaqueen]

Is there an existing issue for this?

• I have searched the existing issues

Issue Description

The current project documentation has several areas that can be improved for clarity and usability. Minor typos and inconsistent formatting reduce overall readability. The contribution process is text-heavy, making it difficult for new contributors to quickly understand the workflow. Additionally, the README lacks a clear project vision and direct navigation aids, such as a link to the documentation search page. The prerequisites and troubleshooting sections could also benefit from clearer guidance and structure.

These issues collectively affect the user experience, slow down onboarding for new contributors, and make the documentation appear less polished and professional.

Suggested Change

✅ Proposed Fix:
● Fix minor typos and formatting inconsistencies for better readability.
● Add a clear, concise flowchart illustrating the contribution workflow .
● Include a direct link to the project’s documentation search page with usage notes.
● Adding vision and enhancing the readme
● Suggest additional minor improvements to the prerequisites and troubleshooting sections.

Rationale

[ ] Fix minor typos and formatting inconsistencies to improve readability and maintain a consistent, polished appearance.
[ ]
[ ] Add a clear, concise flowchart illustrating the contribution workflow to visually guide new contributors and simplify the onboarding process.
[ ]
[ ] Include a direct link to the project’s documentation search page with usage notes to make navigation easier and reduce confusion for users.
[ ]
[ ] Add a vision section and enhance the README to communicate the project’s purpose and future direction, fostering better understanding and engagement.
[ ]
[ ] Suggest minor improvements to the prerequisites and troubleshooting sections to ensure smoother setup and minimize contributor errors or setup issues.

Urgency

High

Record

• I have read the Contributing Guidelines
• Are you a GSSOC'25 contributor
• I want to work on this issue

[github-actions]

Thanks for opening this issue! 🎉 We'll look into it as soon as possible, estimated time for response is 5–8 hrs.

Don't raise PR unless assigned to you.

In the meantime, please provide all necessary details and context to your issue — screenshots or videos of your changes help speed up the review and assignment. If you have questions, reach out to LinkedIn. Your contributions are highly appreciated!😊

Note: I maintain the repo issue every day twice at 8:00 AM IST and 9:00 PM IST. If your issue goes stale for more than one day, you can tag and comment on this same issue by tagging @sanjay-kv.

We are here to help you on this journey of open source. Consistent contributions are eligible for sponsorship 💰

🎁 check our list of amazing people we sponsored so far: GitHub Sponsorship. ✨

📚Resources which can help you know more about Github 👇🏻

1. End to End GitHub Beginner Playlist: GitHub Playlist.

2. Build your GitHub Profile: GitHub Profile Optimisation.

3. GitHub Handbook for dummies: GitHub Blog for Beginners.

[github-actions]

👤 Issue assigned to @Akshayaqueen.

[Akshayaqueen]

Hi @sanjay-kv , Can I request you to add Gssoc25 label

[sanjay-kv]

sure

[Adez017]

Any Updates on this @Akshayaqueen