Open Source Contributions

Designed for first-time contributors to learn, practice, and ship a real pull request.

Build real confidence, not just theory

This page is your contribution practice lab. Follow guided missions, complete the checklist, pick a beginner task, and submit your contribution once your PR is open.

Start Mission Flow

1) How Open Source Works

Core workflow you will use in almost every contribution.

1 Fork

Copy the repository to your GitHub account.

2 Clone

Download your fork locally and create a new branch.

3 Change

Implement a focused fix or improvement.

4 Commit

Write clear commit messages that explain intent.

5 Pull Request

Open a PR and respond to maintainer feedback.

If you get stuck: re-read `README.md` and `CONTRIBUTING.md`, then ask in community channels with your branch link, screenshot, and exact error.

2) Mission Tracks

Pick one track that matches your current level. Every track is beginner-safe and contribution-focused.

Documentation Starter

Best for your first PR: improve docs, steps, or broken instructions.

Pick one unclear section from README or contribution docs.
Rewrite for first-time contributors with better steps and examples.
Submit a focused documentation PR with before/after context.

UI & Accessibility Starter

Fix spacing, labels, responsiveness, and small front-end issues.

Choose a small UI issue (alignment, contrast, or mobile overflow).
Implement a minimal patch and verify on desktop + mobile viewport.
Attach screenshots and short test notes in your PR.

Issue-to-PR Starter

Practice complete workflow from issue selection to merged-ready PR.

Select a beginner-friendly open issue.
Comment your approach before coding.
Submit PR and respond to feedback with clean follow-up commits.

Start with one small mission and complete it end-to-end. Tiny merged PRs beat large unfinished ones.

3) PR Checklist

Track your progress before opening a pull request.

I read the repository `README.md` and `CONTRIBUTING.md`. I forked the repository and cloned it locally. I created a feature branch with a meaningful name. I completed one focused change and reviewed it. I tested changes locally and verified no visible breakage. I committed with a clear, specific commit message. I opened my PR and included context + screenshots if needed.

0 / 7 steps completed

4) Beginner Practice Tasks

Curated beginner tasks from multiple CodeIN community repositories.

Improve README first-time contribution path

CodeIN-Community-Website Beginner

Refine onboarding language and reduce ambiguity in contribution instructions.

Expected PR Type: Documentation

Repository Issues / Guide

Fix mobile spacing in one landing-page section

CodeIN-Community-Website Beginner

Resolve a visible spacing or overflow issue for mobile widths.

Expected PR Type: Frontend UI Fix

Repository Issues / Guide

Add missing alt text to visual assets

CodeIN-Community-Website Beginner

Improve accessibility by auditing and updating image alt attributes.

Expected PR Type: Accessibility Improvement

Repository Issues / Guide

Polish contribution docs for clarity

Aec-Library-Website Beginner

Improve CONTRIBUTING steps and branch/PR examples for new contributors.

Expected PR Type: Documentation

Repository Issues / Guide

Resolve one beginner-safe CSS consistency bug

Aec-Library-Website Beginner

Fix a small consistency issue such as button states or typography mismatch.

Expected PR Type: Frontend UI Fix

Repository Issues / Guide

Improve portfolio section responsiveness

Portfolio-Saurav-Mukherjee Beginner

Address one layout issue affecting smaller screens.

Expected PR Type: Responsive Layout Update

Repository Issues / Guide

Before coding, comment on the issue or track your intent in the PR description to avoid duplicated effort.

5) Submit Completion

Once your PR is open, send your contribution details by email so our team can review and guide your next mission.

Your GitHub profile URL
PR URL(s)
Mission track completed
What you learned during the contribution

Submit by Email