CODEIN COMMUNITY

Your first contribution starts here.

Choose a track, learn the workflow, and turn curiosity into a focused, thoughtful change.

From an idea to a pull request.

Fork the project, clone your fork, create a branch, make one focused change, commit, and open a pull request. Read the project’s README and contribution guide first. If you get stuck, ask the community with your branch link and the exact error.

Choose your mission.

TRACK 01

Documentation Starter

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

View steps and repositories

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.

CodeIN-Community ↗Aec-Library-Website ↗

TRACK 02

UI & Accessibility Starter

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

View steps and repositories

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.

CodeIN-Community ↗Portfolio-Saurav-Mukherjee ↗

TRACK 03

Issue-to-PR Starter

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

View steps and repositories

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

CodeIN-Community ↗Aec-Library-Website ↗

Your contribution checklist

Progress is saved only in this browser. Check each item when you have completed it.

0 of 7 steps completed

I read the repository README and CONTRIBUTING guide.
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 with context and screenshots when useful.

Practice tasks from the community.

These suggestions carry forward the original practice lab. Check the current repository and coordinate with its maintainers; these examples are not a claim that a particular issue is open or assigned.

Beginner · CodeIN-Community

Improve README first-time contribution path

Refine onboarding language and reduce ambiguity in contribution instructions.

Expected PR type: Documentation

Repository ↗Issues & guidance ↗

Beginner · CodeIN-Community

Fix mobile spacing in one landing-page section

Resolve a visible spacing or overflow issue for mobile widths.

Expected PR type: Frontend UI Fix

Repository ↗Issues & guidance ↗

Beginner · CodeIN-Community

Add missing alt text to visual assets

Improve accessibility by auditing and updating image alt attributes.

Expected PR type: Accessibility Improvement

Repository ↗Issues & guidance ↗

Beginner · Aec-Library-Website

Polish contribution docs for clarity

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

Expected PR type: Documentation

Repository ↗Issues & guidance ↗

Beginner · Aec-Library-Website

Resolve one beginner-safe CSS consistency bug

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

Expected PR type: Frontend UI Fix

Repository ↗Issues & guidance ↗

Beginner · Portfolio-Saurav-Mukherjee

Improve portfolio section responsiveness

Address one layout issue affecting smaller screens.

Expected PR type: Responsive Layout Update

Repository ↗Issues & guidance ↗

Share what you learned.

Once your PR is open, email the community with your GitHub profile, PR URL, mission track, and what you learned. Include the context you would like help with.

Submit by email ↗