[FEATURE] Polish and improve README readability

[BitForge95]

Brief summary

Improve the readability and formatting of the project README.md to make it more welcoming for new open-source contributors.

Motivation

The README is the first thing visitors see when they land on the repo. Making it easier to read and more visually clear helps new contributors quickly understand what Splitt is and how to get involved. A polished README is vital for our community!

Acceptance criteria

[ ] Add relevant emojis to the main section headings.

[ ] Break up any long, dense paragraphs into shorter 2-3 sentence blocks.

[ ] Ensure the "Tech Stack" and "Setup" sections use clear bullet points or bold text for readability.

[ ] Verify that all existing markdown syntax (links, code blocks) renders correctly without errors.

Proposed design

README.md

Out of scope

Taking or adding screenshots. Adding CI badges. Changing the actual core content, meaning, or structure significantly, this is about visual polish and formatting, not a total rewrite!

[vidhikasaxena]

Hi @BitForge95 I'd like to work on this issue. I'll improve the README's readability and formatting by adding emojis to headings, breaking up dense text, and polishing the Tech Stack and Setup sections while keeping the existing content and structure unchanged. Please assign it to me.

[Icsylab]

Hi @BitForge95 .
After going through the README, here's what I'm planning:

1. Add relevant emojis to section headings (How it works, Stack, Getting Started, etc.)
2. Break up the dense "How it works" paragraph into shorter, scannable chunks
3. Bold key terms in the Stack and Getting Started sections for faster skimming
4. Add bash syntax highlighting to the setup code block
5. Fix the inconsistent "Auto ride-sharing" vs "Auto ride sharing" casing
6. Verify all links and code blocks render correctly

Would love to work on this issue.

[prateek-shanbhag]

Hi @BitForge95,

I'd like to work on this issue if it's still available.

I've reviewed the acceptance criteria and my approach will be to:

• Add consistent, relevant emojis to the main section headings.
• Split long paragraphs into shorter, contributor-friendly sections without altering the content.
• Improve the Tech Stack and Setup sections using clear bullets and emphasis where appropriate.
• Verify all links, code blocks, and markdown render correctly across GitHub's markdown preview.
• Keep the changes strictly within the scope of readability and visual polish.

Kindly assign this to me.

[Pranavgitty]

Hi @BitForge95 ,

I'd like to work on this issue if it's still available.

I will be following the acceptance criteria you mentioned:

1. I will add consistent and appropriate emojis to the ReadME to make it non-monotonous for readers.
2. Verify that all the links and code blocks render on my machine before opening a pull request.
3. Reduce content heavy paragraphs to readable bullet points.
4. The headings like "Tech stack' and "Setup" are formatted such that the are clearly readable.

Also I found a few opportunities to improve its readability without changing any functionality. My plan is to:

1. Add a concise Quick Overview section for first-time readers(Something like a TL;DR).
2. Add a small Project Structure section to help new contributors navigate the codebase.
3. Improve the visual flow of the "How it works" section by convertinf it from bullet points to a flow chart diagram.
4. Add a short New Contributor/Troubleshooting section to reduce common setup confusion.

I'll keep the documentation concise and maintain the existing style while making it easier for both users and contributors to get started.

Kindly assign this to me so I can start working on this.

[AniketSingh16742]

Hi @BitForge95 I would like to work on this issue and improve the readme.md file. I'll make sure to fulfill all the above mentioned criteria, as I also have written many readme.md files for my personal projects with proper format and by using proper emojis to attract attention of contributors.
I would really like to contribute if you assign me this issue.

[prashant273000]

HI @BitForge95 I would like to work on this issue and improve the readability of the Readme.md file. Since the acceptance criteria is already clear I would make sure the Readme.md file is according to the acceptance criteria. Hoping that this issue gets assigned to me.
Thank you,
Prashant.

[BitForge95]

@prateek-shanbhag i am assigning you this issue as the people above you are already handling some issues and remaining contributors , as the first few issues are a bit general and easy , we will assigning them on fcfs , then later on will be checking the PR description and approach.