Skip to content

docs: improve README formatting and readability#19

Open
prateek-shanbhag wants to merge 1 commit into
bsoc-bitbyte:mainfrom
prateek-shanbhag:docs/readme-formatting
Open

docs: improve README formatting and readability#19
prateek-shanbhag wants to merge 1 commit into
bsoc-bitbyte:mainfrom
prateek-shanbhag:docs/readme-formatting

Conversation

@prateek-shanbhag

@prateek-shanbhag prateek-shanbhag commented Jun 10, 2026

Copy link
Copy Markdown

What

In this PR readme documentation is updated so that it has better readability and is more welcoming for new open-source contributors.

Fixes #5

Type of change

  • Added 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.

Proof of work

image image image

Checklist

  • I claimed this issue before starting work
  • Branch name follows the convention (feature/, fix/, docs/)
  • Commits follow Conventional Commits format
  • CI is passing (lint, prettier, build)
  • I have self-reviewed my own code
  • Any non-obvious decisions are explained with a comment in the code

Copilot AI review requested due to automatic review settings June 10, 2026 13:00

Copilot AI left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Note

Copilot was unable to run its full agentic suite in this review.

Updates the project README to be more welcoming and structured, with clearer onboarding and section formatting.

Changes:

  • Added emoji-enhanced section headers and reorganized “Getting Started” into prerequisites/setup/launch steps
  • Reformatted the Tech Stack section and simplified “How it works” bullets
  • Simplified Contributing/Docs sections into shorter bullet lists

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

Comment thread README.md
Comment on lines +19 to +25
| | |
| ------------- | ------------------------------------------------------------------------------------ |
| **Frontend** | **React 18**, **Vite**, **TailwindCSS**, **TanStack Query**, **React Router v6** |
| **Backend** | **Node.js 20**, **Express**, **Prisma**, **PostgreSQL** |
| **Real-time** | **Server-Sent Events (SSE)** |
| **Auth** | **Google Identity Services** _(ID token flow — no client secret needed)_ |
| **Infra** | **Docker** (local), **Render** (backend), **Vercel** (frontend), **Neon** (database) |
Comment thread README.md
Comment on lines +9 to +11
1. **Post a ride** — Add info if have spare seats.
2. **Post an intent** — request for a ride.
3. **Match** — Splitt finds the intended rides automatically.
Comment thread README.md

Read [docs/CONTRIBUTING.md](docs/CONTRIBUTING.md) before opening a PR.
Open issues are tracked in [CLEANUP.md](CLEANUP.md) — pick one and claim it.
- Before opening any PR make sure to read **[docs/CONTRIBUTING.md](docs/CONTRIBUTING.md)**.
Comment thread README.md
Comment on lines +75 to +77
- Refer **[docs/SETUP.md](docs/SETUP.md)** — for Local setup, Google OAuth config, all dev commands
- Refer **[docs/DATA_SHAPES.md](docs/DATA_SHAPES.md)** — for Every API endpoint with request and response examples
- Refer **[docs/CONTRIBUTING.md](docs/CONTRIBUTING.md)** — for Branch naming, commit format, PR process
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[FEATURE] Polish and improve README readability

2 participants