Merge pull request #21 from OSSPhilippines/copilot/fix-84425943-167b-4f9e-90cc-0ca158317c8d

I need to refactor this first-contribution repository to eliminate merge conflicts. Currently, all contributors edit a single data.json file, causing conflicts when multiple PRs are open.
Required Changes:

Create new directory structure:

Create a con...

Author: jofftiquez

.github/workflows/build.yml

@@ -0,0 +1,48 @@
+name: Build Contributors Data
+
+on:
+  push:
+    branches:
+      - main
+    paths:
+      - 'contributors/**'
+  pull_request:
+    branches:
+      - main
+    paths:
+      - 'contributors/**'
+
+permissions:
+  contents: write
+
+jobs:
+  build:
+    runs-on: ubuntu-latest
+    
+    steps:
+      - name: Checkout repository
+        uses: actions/checkout@v4
+        with:
+          token: ${{ secrets.GITHUB_TOKEN }}
+          
+      - name: Setup Node.js
+        uses: actions/setup-node@v4
+        with:
+          node-version: '20'
+          
+      - name: Build data.json
+        run: npm run build
+        
+      - name: Check for changes
+        id: git-check
+        run: |
+          git diff --exit-code data.json || echo "changed=true" >> $GITHUB_OUTPUT
+          
+      - name: Commit and push if changed
+        if: steps.git-check.outputs.changed == 'true' && github.event_name == 'push'
+        run: |
+          git config user.name "github-actions[bot]"
+          git config user.email "github-actions[bot]@users.noreply.github.com"
+          git add data.json
+          git commit -m "🤖 Auto-update data.json from contributors"
+          git push

.gitignore

@@ -0,0 +1,3 @@
+node_modules/
+.DS_Store
+*.log

CONTRIBUTING.md

@@ -0,0 +1,67 @@
+# Contributing Guidelines
+
+Thank you for your interest in contributing to this project! 🎉
+
+## How the New System Works
+
+This project now uses individual contributor files instead of a single `data.json` file. This means:
+
+- **No More Merge Conflicts**: Each contributor creates their own file, eliminating conflicts between pull requests
+- **Simple Process**: Just create a JSON file with your information
+- **Automatic Build**: GitHub Actions automatically rebuilds the `data.json` file when changes are merged
+
+## File Structure
+
+Your contributor file should be named `contributors/{your-github-username}.json` and follow this format:
+
+```json
+{
+  "github": "your-github-username",
+  "photo": "https://github.com/your-github-username.png",
+  "quote": "Your favorite quote here"
+}
+```
+
+### Fields
+
+- **github** (required): Your GitHub username
+- **photo** (optional): URL to your profile photo. If omitted, your GitHub avatar will be used automatically
+- **quote** (required): Your favorite quote or a message
+
+## Step-by-Step Guide
+
+1. **Fork the repository** - Click the "Fork" button at the top right
+2. **Clone your fork** - `git clone https://github.com/YOUR-USERNAME/first-contribution.git`
+3. **Create a branch** - `git checkout -b add-your-name`
+4. **Create your file** - Add `contributors/your-username.json` with your information
+5. **Commit** - `git add contributors/your-username.json && git commit -m "Add YOUR-NAME to contributors"`
+6. **Push** - `git push origin add-your-name`
+7. **Create a Pull Request** - Go to GitHub and create a PR from your branch
+
+## What Happens After You Submit?
+
+1. Your PR will be reviewed
+2. Once approved and merged, GitHub Actions will automatically run
+3. The `data.json` file will be regenerated from all contributor files
+4. Your name will appear on the contributors page!
+
+## Need Help?
+
+- Check `contributors/TEMPLATE.json` for an example
+- Look at existing files in the `contributors/` directory
+- Open an issue if you have questions
+- Ask for help in your pull request comments
+
+## Building Locally (Optional)
+
+If you want to test the build process locally:
+
+```bash
+npm run build
+```
+
+This will regenerate `data.json` from all the contributor files.
+
+---
+
+Happy Contributing! 🚀

README.md

@@ -37,7 +37,9 @@ Replace `your-name` with your actual name or GitHub username.
 
 ### Step 4: Add Your Information
 
-Open the `data.json` file and add your information to the array. Here's the format:
+Create a new JSON file in the `contributors/` directory with your GitHub username as the filename. For example, if your username is `johndoe`, create `contributors/johndoe.json`.
+
+**Template:**
 
 ```json
 {
@@ -48,37 +50,36 @@ Open the `data.json` file and add your information to the array. Here's the form
 ```
 
 **Important:** 
-- **Always add your entry at the end of the JSON array** (before the closing `]`). It's first come, first serve!
-- Add a comma after the previous entry before adding yours
+- **Create a new file** named `contributors/{your-github-username}.json`
+- Replace `your-github-username` with your actual GitHub username
 - The `photo` field is optional. If you don't provide it, your GitHub avatar will be used automatically
-- Make sure your JSON is properly formatted
+- Make sure your JSON is properly formatted (use the template above)
 
 **Example:**
 
+If your username is `johndoe`, create `contributors/johndoe.json`:
+
 ```json
-[
-  {
-    "github": "exampleuser",
-    "photo": "https://github.com/exampleuser.png",
-    "quote": "The best way to predict the future is to invent it."
-  },
-  {
-    "github": "yournewusername",
-    "photo": "https://github.com/yournewusername.png",
-    "quote": "Code is like humor. When you have to explain it, it's bad."
-  }
-]
+{
+  "github": "johndoe",
+  "photo": "https://github.com/johndoe.png",
+  "quote": "Code is like humor. When you have to explain it, it's bad."
+}
 ```
 
+You can also look at existing files in the `contributors/` directory or use `contributors/TEMPLATE.json` as a reference.
+
 ### Step 5: Commit Your Changes
 
 Add and commit your changes:
 
 ```bash
-git add data.json
+git add contributors/your-github-username.json
 git commit -m "Add YOUR-NAME to contributors"
 ```
 
+Replace `your-github-username` with your actual GitHub username.
+
 ### Step 6: Push to GitHub
 
 Push your changes to your forked repository:
@@ -108,6 +109,7 @@ Or open `index.html` in your browser locally to see the page.
 ## 💡 Need Help?
 
 If you run into any issues or have questions, feel free to:
+- Check out [CONTRIBUTING.md](CONTRIBUTING.md) for detailed guidelines
 - Open an issue in this repository
 - Ask for help in the pull request comments
 - Reach out to the community

contributors/Himans40.json

@@ -0,0 +1,5 @@
+{
+  "github": "Himans40",
+  "photo": "https://github.com/Himans40.png",
+  "quote": "The best way to predict the future is to invent it."
+}

contributors/JefersonDeLeon.json

@@ -0,0 +1,5 @@
+{
+  "github": "JefersonDeLeon",
+  "photo": "https://github.com/JefersonDeLeon.png",
+  "quote": "Fail faster, learn faster."
+}

contributors/MKgu-droid.json

@@ -0,0 +1,5 @@
+{
+  "github": "MKgu-droid",
+  "photo": "https://github.com/MKgu-droid.png",
+  "quote": "Everything happens for a reason"
+}

contributors/TEMPLATE.json

@@ -0,0 +1,5 @@
+{
+  "github": "your-github-username",
+  "photo": "https://github.com/your-github-username.png",
+  "quote": "Your favorite quote here"
+}

contributors/boringdeveloper.json

@@ -0,0 +1,5 @@
+{
+  "github": "boringdeveloper",
+  "photo": "https://github.com/boringdeveloper.png",
+  "quote": "It works on my machine."
+}

contributors/jofftiquez.json

@@ -0,0 +1,5 @@
+{
+  "github": "jofftiquez",
+  "photo": "https://github.com/jofftiquez.png",
+  "quote": "It's something unpredictable but in the end it's right"
+}