LadybirdBrowser/ladybird

Looking for good first issues?

Open

#9401 opened on May 14, 2026

View on GitHub
 (0 comments) (0 reactions) (0 assignees)C++ (63,353 stars) (3,028 forks)batch import
good first issue

Description

Welcome to Ladybird! :^)

As you have probably noticed, we do not have any issues labeled "good first issue", for a few reasons: We've found that it's difficult to estimate how difficult an issue will be to solve, it's easy for these to go out of date, and a lot of the time it's faster to just fix a small issue than to write an explanation of it on GitHub.

There are many ways of finding small issues to fix though! Our Getting Started guide has some suggestions. A major way is to try visiting your favorite sites, see what's broken, and try to fix it. It's far more satisfying to fix a bug on a site you care about, than to fix something that doesn't affect you. Our Discord server is always here if you need some suggestions for how to diagnose or fix the issue.

Contributor guide

Tech stack
None
Domain
documentation
Issue type
documentation
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
1
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
under 1 hour
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
fresh
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
None
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
100
Research direction
Refer to the 'Getting Started' guide linked in the issue (Documentation/GettingStartedContributing.md) for suggestions on finding small bugs to fix. Join the Discord server for real time help and guidance on diagnosing issues.