LNbits grows through community contributions.
Whether you are fixing bugs, testing features, designing interfaces, writing tutorials, onboarding merchants, or building businesses on top of LNbits, there is a place to contribute.
Our contributor portal references GitHub issues and PRs that are looking for community help, but it is much more than just a list of tags and tickets.
The portal brings together contribution paths, open work, ideas, resources, onboarding information, and ways to get involved across the LNbits ecosystem. It is meant as a starting point for anyone who wants to explore where they can help and what is possible inside the project.
Today LNbits has contributions from more than 100+ contributors across many disciplines, not just software development. So jump in, explore the portal, and see where your skills fit best.
Ways to contribute to LNbits
Developer
Fix bugs, build features, improve extensions, and get your code merged.
Tester
Run PRs locally, hunt bugs, reproduce issues, and provide feedback before features ship.
Writer
Write documentation, tutorials, guides, announcements, and educational content for the ecosystem.
Designer
Improve UX, create mockups, polish interfaces, design visuals, and help shape the LNbits experience.
Entrepreneur
Build businesses, products, services, or integrations on top of LNbits.
Ambassador
Deploy LNbits in your local community, onboard merchants, educate users, and help grow Lightning adoption.
Labels that surface work to contributors
The contributor page links to filtered views of open issues and PRs on GitHub. These labels help contributors discover work that matches their interests and experience level.
good first issue
Small, well-scoped tasks suitable for first-time contributors.
These should be approachable without requiring deep project knowledge or a long onboarding process. We use this label sparingly and only for issues that newcomers can realistically complete independently.
Examples include:
-
Small bug fixes
-
Minor UI improvements
-
Documentation updates
-
Isolated refactors
needs-testing
A PR or issue that needs community testing before it can be merged or closed.
This can include:
-
Running a branch locally
-
Exercising a feature
-
Confirming bug fixes
-
Reporting regressions or edge cases
This label is different from awaiting review. It specifically signals that hands-on testing from the community is needed.
design
Work related to:
-
UI and UX improvements
-
User flows
-
Styling and visual polish
-
Mockups and illustrations
This label is narrower than general frontend work. A frontend issue may involve implementation, while design highlights tasks where visual and UX contributions are especially needed.
Helping contributors find the right work
These labels help make contribution opportunities visible on the contributor page and make it easier for people to jump into LNbits.
If you are maintaining issues or PRs, please apply these labels during triage so contributors can discover open work more easily.
If you are opening an issue or PR yourself and think one of these labels fits, feel free to suggest it.
LNbits has always grown through community effort, and contributions come in many forms. Some people write code, some test features, some create documentation, design interfaces, onboard merchants, or help others get started.
We especially want to encourage more non-code contributions as well. Good documentation, tutorials, testing, feedback, and design work are just as important for the project.