Updated Cotributing.md

Author: Adii0906

CONTRIBUTING.md

@@ -1,59 +1,73 @@
 # Contributing to Vanilla Verse
 
-Thanks for your interest in contributing! This project is designed for first-time contributors.
+Welcome! This guide will help you make your first contribution. No experience needed—just follow the steps below.
 
-## Ways to contribute
-- Pick a project from the hub (`index.html`) and open its folder in `projects/vanilla-verse`.
-- Read the local `README.md` and `main.js` of projects for TODO markers.
-- Open an issue to ask questions or propose a change.
+## How to contribute (Step-by-step)
 
-## Development setup
-1. Use VS Code with the Live Server extension (recommended) or any static HTTP server.
-2. Open `index.html` and ensure links to projects work.
-3. Make small, focused changes.
+### 1. Fork the repository
+- Click the **Fork** button at the top right of the GitHub page. This creates your own copy of the project.
 
-## Commit and PR guidelines
-- Use meaningful commit messages.
-- Title PRs clearly (e.g., "Snake: Add keyboard controls" or "Todo: Persist to localStorage").
-- Link related issues, and check the "good first issue" label when appropriate.
-- Ensure HTML/JS syntax passes basic validation (no console errors on load).
+### 2. Clone your fork
+- On your forked repo, click **Code** and copy the URL.
+- Open your terminal and run:
+    ```bash
+    git clone https://github.com/your-username/vanilla-verse.git
+    cd vanilla-verse
+    ```
 
-### Issue → Assign → PR flow (enforced)
+### 3. Pick a project to work on
+- Open `index.html` and look at the projects listed.
+- Go to the folder in `projects/vanilla-verse` for the project you want.
 
-To keep work organized and make it simple for maintainers to triage contributions we follow this flow and enforce it via a repository check:
+### 4. Read the local files
+- Check the `README.md` and `main.js` in the project folder for TODOs or ideas.
+- If you have questions or want to suggest something, open an issue on GitHub.
 
-1. Create an issue describing the change you want to make. Use the provided issue templates when appropriate. Alternatively, get alloted in an existing issue. 
-2. A maintainer (or you, if given permission) assigns the issue to someone. The assignment signals ownership and helps avoid duplicate work.
-3. Open a pull request that references the assigned issue in the PR body (for example: `Closes #12`, `Fixes #12`, or include `#12` somewhere in the PR description).
+### 5. Make your changes
+- Use [VS Code](https://code.visualstudio.com/) with the Live Server extension (recommended) or any static HTTP server.
+- Edit the code. Make small, focused changes.
 
-Our CI includes a check that requires PRs to reference an existing issue that is already assigned. If you open a PR without a referenced assigned issue, the check will fail and a maintainer will ask you to link/assign the issue first.
+### 6. Commit your changes
+- Save your work and run:
+    ```bash
+    git add .
+    git commit -m "Describe your change here"
+    git push
+    ```
 
-Why this helps:
-- Prevents duplicated effort (two people solving the same item at once).
-- Makes it clear who owns the change and who to ask for review.
-- Keeps the issue tracker meaningful (issues move to closed automatically when referenced with `Closes #N`).
+### 7. Open a Pull Request (PR)
+- Go to your fork on GitHub. Click **Compare & pull request**.
+- In the PR description, reference the issue you worked on (e.g., `Closes #12`).
+- Title your PR clearly (e.g., "Snake: Add keyboard controls").
 
-Examples (PR body):
+### 8. Wait for review
+- A maintainer will review your PR and may suggest changes.
+- If needed, update your PR by pushing more commits.
 
-```
-Closes #12
+## Issue → Assign → PR flow
 
-Add keyboard controls to the Snake game. This PR implements arrow keys and prevents reverse-direction input.
-```
+To keep things organized:
+1. **Create an issue** describing your change or pick an existing one.
+2. **Get assigned** to the issue (ask in a comment if needed).
+3. **Open a PR** that references the assigned issue.
 
-If you're a new contributor and there are no maintainers available to assign, open the issue and add a comment asking for assignment — maintainers will triage and assign as soon as they can.
+PRs must reference an assigned issue, or checks will fail.
 
-## Code style
-- Vanilla JS only. No frameworks, no bundlers.
-- Keep modules small and focused.
-- Favor semantic HTML and accessible markup.
-- Use `assets/styles.css` tokens and utility classes where possible to keep visual consistency.
+## Code style tips
+- Use plain JavaScript (no frameworks).
+- Keep files small and focused.
+- Write semantic HTML and accessible markup.
+- Use styles from `assets/styles.css` for consistency.
 
 ## Reporting issues
-Please include:
-- What you expected vs what happened
+Include:
+- What you expected vs. what happened
 - Steps to reproduce
-- Screenshots or code snippets if helpful
+- Screenshots or code snippets if possible
 
 ## Code of Conduct
-By participating, you agree to abide by our `CODE_OF_CONDUCT.md`.
+By contributing, you agree to follow our [`CODE_OF_CONDUCT.md`](CODE_OF_CONDUCT.md).
+
+---
+
+**You got this!** If you get stuck, ask questions in issues. Maintainers are here to help.