Community & Discovery Improvements: - Add CODE_OF_CONDUCT.md (Contributor Covenant 2.0) - Add badges to README (stars, license, last commit, PRs welcome) - Add comparison section (vs Copilot, Cursor, Aider) - Improve tagline with SEO keywords - Add issue templates (bug report, feature request, good first issue) - Add GitHub settings checklist for post-merge configuration SEO & Discoverability: - Keyword-rich description for search ranking - Clear differentiation from alternatives - Professional presentation with badges - Community-friendly templates Next Steps (After Merge): - Update About section with new description - Add 16 topics for search optimization - Enable GitHub Discussions - Create social preview image - Add issue labels Estimated Impact: 10x improvement in GitHub discoverability
38 lines
853 B
Markdown
38 lines
853 B
Markdown
---
|
|
name: Good First Issue
|
|
about: Template for maintainers to create beginner-friendly issues
|
|
title: '[GOOD FIRST ISSUE] '
|
|
labels: 'good first issue, help wanted'
|
|
assignees: ''
|
|
---
|
|
|
|
## Description
|
|
A clear description of what needs to be done.
|
|
|
|
## Why This Matters
|
|
Explain the impact of this change.
|
|
|
|
## Suggested Approach
|
|
1. Step-by-step guidance
|
|
2. Files to modify
|
|
3. Expected outcome
|
|
|
|
## Resources
|
|
- Link to relevant documentation
|
|
- Similar examples in the codebase
|
|
- External references if needed
|
|
|
|
## Acceptance Criteria
|
|
- [ ] Criterion 1
|
|
- [ ] Criterion 2
|
|
- [ ] Tests added/updated
|
|
- [ ] Documentation updated
|
|
|
|
## Getting Started
|
|
1. Fork the repository
|
|
2. Create a branch: `git checkout -b fix/issue-name`
|
|
3. Make your changes
|
|
4. Submit a PR referencing this issue
|
|
|
|
## Questions?
|
|
Feel free to ask questions in the comments. We're here to help! 🙌
|