DEV Community

Cover image for I Contributed to Forem Using Only My Android Phone 📱"
meow.hair
meow.hair

Posted on

I Contributed to Forem Using Only My Android Phone 📱"

#javascript #security #opensource #programming

"I Contributed to Forem Using Only My Android Phone 📱"
published: true

tags: [opensource, forem, github, beginners, accessibility, android]

I Contributed to Forem Using Only My Android Phone 📱🦆

Hi there! 😁🍷🗻🤍🧊🌊🌳

I'm a self-taught developer who learns from an old Android phone with only 4GB of RAM. No laptop. No powerful setup. Just curiosity and a browser.

In this article, I'll share my first open-source contribution to Forem — the platform that powers dev.to.

I hope this story inspires every beginner who thinks contributing to open source is too difficult or requires superhuman abilities!

😁Why Forem?

  • Massive impact: Used by thousands of developers daily
  • Welcoming community: Known for being beginner-friendly
  • good first issue labels: Perfect for newcomers
  • Ruby on Rails codebase: A chance to learn from a real-world project

💡 The Real Challenge: A 4GB Android Phone

Yes, you read that correctly! I have an Android phone with only 4 GB of RAM, and I completed every single step on it.

The problem: GitHub's mobile interface is limited.

My solution: Enable Desktop Mode in my browser. It wasn't easy — tiny text, slow loading, awkward scrolling — but it worked!

📝 What I Changed: A Tiny Accessibility Fix

While browsing the Forem repository, I noticed something in the README.md:

<!-- Before -->
<img src="...ci.yml/badge.svg" alt="Build Status">
<img src="...cd.yml/badge.svg" alt="Build Status">
Enter fullscreen mode Exit fullscreen mode

Both badges had the same alt text. For screen reader users, this is confusing — they'd hear "Build Status" twice without knowing which is which.

My fix:

<!-- After -->
<img src="...ci.yml/badge.svg" alt="CI Build Status">
<img src="...cd.yml/badge.svg" alt="CD Build Status">
Enter fullscreen mode Exit fullscreen mode

Just two letters. CI and CD. But this tiny change helps visually impaired users understand the difference.

🔗 The PR: forem/forem#9184

🛠️ The Steps (No Command Line Needed!)

  1. Fork the repository to my GitHub account
  2. Edit README.md via mobile browser (Desktop Mode)
  3. Create a Pull Request with a clear description
  4. Sign the CLA by commenting: > "I have read the CLA Document and I hereby sign the CLA"
  5. Wait for review from the Forem maintainers

That's it. No terminal. No complex tools. Just a browser and patience.

🗻 What I Achieved

✅ Created my first Pull Request to a major project
✅ Learned the full workflow: Fork → PR → CLA → Review
✅ Discovered that small changes matter
✅ Proved that hardware doesn't limit curiosity
✅ GitHub Actions tests passed — my code doesn't break anything!

🧊🌊 What I Learned

  • Small changes matter: Two letters improved accessibility for thousands of users
  • You don't need powerful hardware: Curiosity beats specs
  • The community is welcoming: Maintainers review PRs with kindness
  • Accessibility is everyone's job: Even a README file can make a difference
  • Patience is part of the journey: Not every PR gets merged immediately, and that's okay

💬 My Advice to Beginners

Don't wait until you become an expert.🤍
Open source needs people who are learning.🧊


Start small:

  • Fix a typo in a README
  • Improve documentation
  • Add an alt text to an image
  • Translate a sentence

Every expert was once a beginner.

🤍🧊🌊🦆 Your Turn!

Have you contributed to open source? Or are you thinking about starting?

Tell me in the comments — I'd love to hear your story! 🍃

📫 Let's connect:

Thanks for reading! 📜🤍🗻😁🌊🧊🦆
Enter fullscreen mode Exit fullscreen mode

Top comments (0)