Contribute to Lightning Bounties Docs & Earn Bounties
Improve Lightning Bounties documentation and earn Bitcoin! Fix typos, add guides, or enhance clarity through our simple bounty platform. Get paid in sats for merged contributions.
Want to make our documentation even better? First of all, thank you! This page will guide you through our contribution process, including how to submit changes and claim bounties for your contributions.
Table of Contents
Quick Documentation Edits
Prerequisites
To edit our documentation, you must have a GitHub account. If you already have one, make sure you are logged in. If you don't, please create one.
Understanding GitBook's Integration with GitHub
We use a platform called GitBook to host, manage and serve our documentation. GitBook fetches files from our GitHub repository Lightning-Bounties/docs
, reads them and converts them into the pages you can access on docs.lightningbounties.com.
Method 1: Quick Editing via GitHub Web Interface
Step 1: Access the Edit Function
Open the page you want to edit on docs.lightningbounties.com
Look for an "Edit on GitHub" button above the Table of Contents on the right side
Click on the GitHub icon to navigate to the Markdown file

Step 2: Edit the File
Click on the pencil icon labeled "Edit this file"
Make your edits using Markdown formatting
Use GitBook's Markdown reference guide for proper formatting

Step 3: Create Your Pull Request
Scroll down to the "Commit changes" section
Write a short, descriptive title for your changes
Add a detailed description explaining your improvements
Important: Include
close #[issue-number]
in your description if you're fixing a specific issueSelect "Create a new branch for this commit and start a pull request"
Click "Propose file change"

Step 4: Submit Your Pull Request
On the Pull Request page, add a clear comment explaining your changes
Critical Step: Ensure your PR description includes
close #[issue-number]
syntax if applicableClick "Create pull request"

Method 2: Local Development Workflow
Step 1: Fork and Clone
Navigate to the Lightning-Bounties/docs repository
Click the "Fork" button to create your personal copy
Clone your fork locally:
git clone https://github.com/YOUR-USERNAME/docs.git
cd docs
Step 2: Create a Feature Branch
git checkout -b improve-bounty-guide
Step 3: Make Your Changes
Edit the relevant Markdown files using your preferred editor
Follow GitBook's formatting guidelines
Place any images in the
.gitbook/assets/
folderTest your changes locally if possible
Step 4: Commit and Push
git add .
git commit -m "Improve bounty claiming guide with clearer steps"
git push origin improve-bounty-guide
Step 5: Create Pull Request
Navigate to your fork on GitHub
Click "New Pull Request"
Essential: Include
close #[issue-number]
in the PR descriptionProvide clear explanation of your changes
Submit the pull request
Lightning Bounties Payment System
The Critical close #[issue-number]
Syntax
close #[issue-number]
SyntaxTo earn Bitcoin bounties for your contributions, you must include the close #[issue-number]
syntax in your pull request description.
This connects your PR to the Lightning Bounties issue and triggers automatic payment processing.
Important Notes:
The
close
keyword must be in the PR description itself, not in regular commentsAdding this connection after merging will automatically trigger Lightning Bounty payment
If you forget to add this initially, you can edit your merged PR description later
If You Forgot the Close Syntax
Option 1: Edit Your Merged Pull Request
Go to your merged PR and click into it
Click the "..." button at the top-right of your PR description
Select "Edit"
Add
close #[issue-number]
to your PR descriptionClick "Update Comment"
Option 2: Ask for Help
If you cannot edit the PR, ask the repository owner to add the close
syntax for you.
Claiming Your Bitcoin Bounty
Step-by-Step Claiming Process
Visit the Platform: Go to app.lightningbounties.com
Find Your Bounty: Look for your bounty
Example: "Help Improve Lightning Bounties Documentation and Earn Sats!"
Claim Your Reward:
Click on "Claim Reward"
Add your pull request number
Click the "Check" button to verify eligibility
Receive Payment: The reward will be added to your balance and paid instantly via the Lightning Network

Payment Requirements
Your pull request must be merged
The PR description must contain
close #[issue-number]
syntaxLightning Bounties uses the GitHub API as an oracle to prevent fraudulent claims
Payments are processed automatically when all conditions are met
Common Documentation Bounties
Lightning Bounties offers Bitcoin rewards for documentation improvements:
Typo fixes
1,000-2,000 sats
Grammar, spelling, punctuation
Broken links
2,000-2,500 sats
Fix outdated or incorrect URLs
Clarity improvements
5,000-10,000 sats
Simplify complex explanations
Screenshots/Video Tutorials
8,000-15,000 sats
Add missing visual guides
New sections
15,000-25,000 sats
Create new documentation pages
Major guides
30,000+ sats
Comprehensive tutorials
Amounts vary based on complexity and Bitcoin price
What We're Looking For
Simple Fixes (Great for Beginners)
Typos and grammar corrections
Broken or outdated links
Formatting inconsistencies
Missing punctuation
Unclear instructions
Add missing alt-text to images
Content Improvements
Step-by-step tutorials with screenshots
Troubleshooting guides for common problems
Beginner-friendly explanations of Bitcoin/Lightning concepts
Real-world examples and use cases
Better organization and navigation
Global Accessibility
Simplifying US-centric references
Nostr Guide's For Lightning Bounties
Explain Bitcoin terminology for newcomers
Including multiple Lightning wallet guides
Clarifying payment processing variations
Writing Guidelines
Writing Best Practices
Use clear, concise language suitable for global developers
Follow consistent Markdown formatting
Include relevant links to Lightning Bounties resources
Ensure proper heading hierarchy (H1, H2, H3, etc.)
Test all external links for functionality
Explain Bitcoin and Lightning Network concepts for newcomers
Use simple examples and step-by-step instructions
Technical Standards
Keep contributions focused on specific improvements
Follow existing file structure and naming conventions
Optimize images and include descriptive alt text
Add missing screenshots and visual guides
Use proper Git commit message conventions
Include screenshots for complex UI interactions
Add troubleshooting sections where appropriate
Documentation Priorities
Community Engagement
Respond promptly to feedback during reviews
Be open to suggestions from maintainers
Credit sources appropriately when building on existing work
Maintain professional and constructive communication
Help other contributors in discussions
Local Development Workflow
For substantial changes, work locally:
Setup Your Environment
# Fork Lightning-Bounties/docs on GitHub first
git clone https://github.com/YOUR-USERNAME/docs.git
cd docs
git checkout -b improve-documentation
Make Your Changes
Edit markdown files in your preferred editor
Add images to
.gitbook/assets/
folderUpdate navigation in
SUMMARY.md
if neededTest links and formatting
Submit Your Work
git add .
git commit -m "Example commit message
Improve bounty claiming documentation
- Add screenshots for claim interface
- Clarify Lightning wallet requirements
- Fix broken links in troubleshooting section
- Update outdated fee information
close #789"
git push origin improve-documentation
Create pull request on GitHub with close #[issue-number]
in description.
Repository Structure
Our documentation lives at Lightning-Bounties/docs:
docs/
├── README.md \# Homepage content
├── SUMMARY.md \# Navigation structure
├── getting-started/ \# New user guides
│ ├── first-time-onboarding/ \# Account setup
│ ├── posting-a-bounty/ \# For bounty creators
│ └── solving-a-bounty/ \# For bounty hunters
├── glossary-work-in-progress/ \# Platform features
├── resources/ \# Help \& references
│ ├── frequently-asked-questions/
│ ├── troubleshooting/
│ └── socials/
└── .gitbook/
└── assets/ \# Images and media
Key Components:
The
.gitbook/assets
folder manages every file used in any pageThe
SUMMARY.md
file tells GitBook the order and grouping of pagesThe
README.md
file contains the first page content users seeGroups of pages are controlled by folders named after the group title
Nested pages have a similar structure, but require a
README.md
file in the parent folder
Getting Support
For additional help with contributions:
Documentation: Check our detailed guides at docs.lightningbounties.com
Community: Join our Discord for real-time assistance
GitHub Issues: Report bugs or request features on our docs repository
Thank you for helping us improve our documentation and contributing to the Bitcoin development ecosystem! Your contributions help make Lightning Bounties more accessible and valuable for developers worldwide, especially those in regions underserved by traditional payment systems.
Remember: Always include close #[issue-number]
in your pull request description to ensure you receive your Bitcoin bounty reward!
Last updated
Was this helpful?