Merge pull request #20 from vaibhavyxx/main

Contribution 1: First Contribution

Author: MoralCode

.github/workflows/jekyll.yml

@@ -0,0 +1,65 @@
+# This workflow uses actions that are not certified by GitHub.
+# They are provided by a third-party and are governed by
+# separate terms of service, privacy policy, and support
+# documentation.
+
+# Sample workflow for building and deploying a Jekyll site to GitHub Pages
+name: Deploy Jekyll site to Pages
+
+on:
+  # Runs on pushes targeting the default branch
+  push:
+    branches: ["main"]
+
+  # Allows you to run this workflow manually from the Actions tab
+  workflow_dispatch:
+
+# Sets permissions of the GITHUB_TOKEN to allow deployment to GitHub Pages
+permissions:
+  contents: read
+  pages: write
+  id-token: write
+
+# Allow only one concurrent deployment, skipping runs queued between the run in-progress and latest queued.
+# However, do NOT cancel in-progress runs as we want to allow these production deployments to complete.
+concurrency:
+  group: "pages"
+  cancel-in-progress: false
+
+jobs:
+  # Build job
+  build:
+    runs-on: ubuntu-latest
+    steps:
+      - name: Checkout
+        uses: actions/checkout@v4
+      - name: Setup Ruby
+        # https://github.com/ruby/setup-ruby/releases/tag/v1.207.0
+        uses: ruby/setup-ruby@4a9ddd6f338a97768b8006bf671dfbad383215f4
+        with:
+          ruby-version: '3.1' # Not needed with a .ruby-version file
+          bundler-cache: true # runs 'bundle install' and caches installed gems automatically
+          cache-version: 0 # Increment this number if you need to re-download cached gems
+      - name: Setup Pages
+        id: pages
+        uses: actions/configure-pages@v5
+      - name: Build with Jekyll
+        # Outputs to the './_site' directory by default
+        run: bundle exec jekyll build --baseurl "${{ steps.pages.outputs.base_path }}"
+        env:
+          JEKYLL_ENV: production
+      - name: Upload artifact
+        # Automatically uploads an artifact from the './_site' directory by default
+        uses: actions/upload-pages-artifact@v3
+
+  # Deployment job
+  deploy:
+    environment:
+      name: github-pages
+      url: ${{ steps.deployment.outputs.page_url }}
+    runs-on: ubuntu-latest
+    needs: build
+    steps:
+      - name: Deploy to GitHub Pages
+        id: deployment
+        uses: actions/deploy-pages@v4

_posts/2025-04-06-contributions-1.md

@@ -0,0 +1,73 @@
+---
+layout: post
+# If your post title is longer or more complicated
+# than can be represented in the filename, uncomment the following line
+# and specify a custom title
+title:  "Contribution 1: First-Contributions"
+
+categories: 
+- Contribution
+
+# Enter your name below
+author: Vaibhavy Darshan
+---
+# My Open Source Contribution Experience
+
+## Choosing a Community
+Choosing a community was the hardest part. I did not know enough about the open source ecosystem to confidently choose where to contribute. It felt daunting—more like walking into the unknown—so I focused on documentation as a starting point. Hence, most of the communities that I prefered were first good-first-issue or required simple fixes.
+
+## Communities I Considered
+
+- **[Arduino Docs](https://github.com/arduino/docs-content)**  
+  I use Arduino frequently enough to understand how it works. However, I wasn’t able to locate the specific page with the bug. Additionally, it was written in Markdown, but not in a format I was comfortable working with.
+  ![typo discussion](https://github.com/vaibhavyxx/hfoss2025-blogs/blob/main/assets/images/contributions-1/arduino-docs-content.png?raw=true)
+  I earlier commented on it but I ended up deleting as I could not figure it out.
+
+- **[Twine](https://github.com/klembot/twinejs)**  
+  The bug seemed simple enough to fix, but it was an old issue. I couldn’t find it and tried contacting others to check if it was still relevant or accessible.
+  ![favicon issue]()
+
+- **[FreeSoundOrg](https://github.com/MTG/freesound)**  
+  The issue was really interesting, but also quite complex for a first contribution. I might revisit this in the future.
+  ![dynamic css suggestion](https://github.com/vaibhavyxx/hfoss2025-blogs/blob/main/assets/images/contributions-1/freesound.png?raw=true)
+
+- **[Awesome Audio Visualization](https://github.com/willianjusten/awesome-audio-visualization/issues)**  
+  The repository had a lot of outdated links, which seemed like a simple fix. However, the repository has been inactive for a few years, so I was hesitant to work on it.
+
+## What Did I Pick?
+
+I ultimately decided to contribute to the **[first-contributions](https://github.com/firstcontributions/first-contributions)** repository on GitHub, which is aimed at teaching beginners how to make their first contributions.
+
+I found this repository through class resources. There was a bug regarding confusing instructions, which made for an easy fix and gave me the opportunity to learn how to send my first Pull Request (PR). So, I needed to edit the [ReadMe](https://github.com/firstcontributions/first-contributions/blob/main/README.md).
+
+## How Did My Comm Arch Experience Help?
+
+Honestly, my Comm Arch experience wasn’t directly helpful in picking this repository. The ones we discussed in class required deeper familiarity with the software or the codebase. I ended up asking the TA for help and looking through class resources for support.
+
+## Contribution.md?
+
+The `CONTRIBUTING.md` file in the first-contributions repository made the process much easier. It clearly explained how to make changes and submit a PR.
+
+## Issue I Fixed
+
+There were conflicting instructions between GitHub Desktop and the `README.md`. GitHub Desktop told users to place their names at the end of the list, so I updated the `README.md` to match that instruction. I found that through an issue mentioned [here](https://github.com/firstcontributions/first-contributions/issues/96053).
+
+![Issue](https://github.com/vaibhavyxx/hfoss2025-blogs/blob/main/assets/images/contributions-1/first-contribution-issue.png?raw=true)
+Feel free to click [here](https://github.com/firstcontributions/first-contributions/pull/96227) to take a look at my PR.
+![Screenshot of my Pull Request](https://github.com/vaibhavyxx/hfoss2025-blogs/blob/main/assets/images/contributions-1/first-contributions.png?raw=true)
+
+## My Failed Contribution
+
+I attempted to contribute to the FreeSoundOrg website by removing duplicate CSS imports to improve loading time. However, even though the site used JavaScript (which I am somewhat familiar with), I didn’t feel confident enough with the overall codebase to proceed. I did, however, look at tutorials to see if I could potentially fix it.
+
+## What Blocked Me?
+
+- **FreeSound.Org** – My limited technical knowledge.
+- **First-Contributions** – I initially didn’t know how to refer my PR to the issue another user pointed out, but after some online research, I figured it out.
+
+## Was I Successful?
+
+Technically, my PR hasn’t been accepted or declined yet, so I can’t say for sure. But personally, yes—I was successful. At first, I felt I wouldn’t be able to do this assignment due to lack of knowledge and fear of contributing to an unfamiliar community. But I overcame that fear and made sure my commits and PR were clear and direct.
+
+
+