Skip to content

[Feature]: Improve Readme Formatting and Structure #194

@Dippp10-ally

Description

@Dippp10-ally

Area

Documentation

Problem to solve

New contributors currently lack a proper CONTRIBUTING guide, and setup instructions are scattered across different files or inferred from source code. This makes onboarding confusing and time-consuming, especially for first-time contributors who need clear guidance on how to run the project locally.

Proposed solution

Improve project documentation by:

  • Adding a CONTRIBUTING.md file with clear setup instructions.
  • Including environment variable requirements for frontend and backend.
  • Documenting run commands for both frontend and server.
  • Adding linting, formatting, and build steps for consistency.
  • Ensuring README aligns with actual scripts and project structure.
  • Clearly separating frontend and backend setup instructions.

Who benefits and how?

  • First-time contributors can set up the project quickly without needing to inspect source code.
  • Maintainers spend less time answering repetitive setup questions.
  • Overall onboarding experience becomes smoother and more structured.
  • Reduces setup errors caused by missing or unclear environment documentation.

Scope or acceptance criteria

  • README accurately reflects available scripts and commands.
  • CONTRIBUTING.md is added and linked in README.
  • Environment variables for frontend and backend are documented.
  • Setup steps are clearly separated for frontend and server.
  • Project can be set up by a new contributor using documentation alone

Related files, routes, or references

  • frontend/src/App.jsx
  • server/index.js
  • README.md

Before submitting

  • I checked for an existing issue that already covers this request.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions