[Documentation] Create a Comprehensive CONTRIBUTING.md Guide

[Aditya948351]

Description

As more open-source contributors join DevPath for GSSoC, they need a central guide on how to clone, run, and contribute to the repository.

Proposed Solution

1. Create a CONTRIBUTING.md file in the root directory.
2. Detail the exact steps: git clone, npm install, setting up .env.local, and npm run dev.
3. Add rules about branch naming conventions (e.g., feature/issue-name or fix/issue-name) and PR formatting.

Expected Outcome

A welcoming, easy-to-read guide that reduces the friction for new contributors.

[DivyaShreeS09]

Hi @Aditya948351,
I would like to work on this issue under GSSoC'26. I can create a detailed CONTRIBUTING.md covering project setup, environment configuration, branch naming conventions, and PR guidelines for new contributors.
Could you please assign this issue to me?

[nishupr]

Hey @Aditya948351 !

I'd love to take up this issue and create a comprehensive CONTRIBUTING.md for DevPath. I've already planned out the full structure and content - here's my approach:

Document Structure

CONTRIBUTING.md
├── Welcome & Introduction
├── Table of Contents
├── Code of Conduct
├── Getting Started
│   ├── Prerequisites
│   ├── Fork & Clone
│   ├── Install Dependencies (npm install)
│   ├── Environment Setup (.env.local)
│   └── Running the Dev Server (npm run dev)
├── Branch Naming Conventions
├── Making Changes
├── Commit Message Guidelines
├── Pull Request Process & Formatting
├── Reporting Bugs / Suggesting Features
└── GSSoC-specific Guidelines

Key Sections I'll Cover

• Prerequisites - Node.js version, Git, and any other tools needed
• Step-by-step setup - exact commands from git clone → npm install → .env.local configuration → npm run dev
• Branch naming conventions - e.g., feature/issue-name, fix/issue-name, docs/issue-name, chore/issue-name
• Commit message format - conventional commits style (e.g., feat:, fix:, docs:)
• PR formatting guidelines - title format, description template, linking issues, checklist before submitting
• GSSoC contributor notes - how to get assigned, one issue at a time policy, communication etiquette
• Welcoming tone - beginner-friendly language so first-time open source contributors feel comfortable

Files to be Added/Modified

CONTRIBUTING.md    ← new file in root directory

Could you please assign this issue to me?