Thank you for your interest in contributing to this project! 🚀
- Check if the issue already exists in the Issues section
- Provide clear descriptions of any errors or improvements needed
- Include specific episode numbers and line references when applicable
- Content Corrections: Spotted a typo or technical error? Please let us know!
- Additional Examples: Have a better code example or explanation? Share it!
- Interview Questions: Know great interview questions related to the topics? Add them!
- Fork the repository
- Clone your fork locally
- Create a new branch for your changes:
git checkout -b feature/your-improvement-name
- Make your changes following our guidelines below
- Test your changes (ensure markdown renders correctly)
- Commit with a clear message:
git commit -m "Add: explanation for closure edge case in EP_10" - Push to your fork and create a Pull Request
- Keep explanations clear and beginner-friendly
- Use code comments extensively in examples
- Include real-world scenarios where applicable
- Add interview-style Q&A sections
// ✅ Good: Clear comments explaining the concept
function example() {
// This demonstrates hoisting behavior
console.log(myVar); // undefined (not an error)
var myVar = 5;
}
// ❌ Avoid: Uncommented or unclear code
function example() {
console.log(myVar);
var myVar = 5;
}- Use proper headings hierarchy (H1 → H2 → H3)
- Include code blocks with language specification
- Add emojis sparingly for better readability
- Keep line length reasonable (under 100 characters when possible)
Each episode should follow this structure:
- Introduction - What the episode covers
- Detailed Explanation - Core concepts with examples
- Code Examples - Practical demonstrations
- Interview Questions - Common interview scenarios
- Key Takeaways - Summary points
- Copyrighted content without permission
- Overly complex examples for basic concepts
- Unrelated JavaScript topics not covered in Namaste JavaScript series
- Personal opinions without technical backing
- Open an Issue for general questions
- Reference specific episodes when asking questions
- Be respectful and constructive in all communications
We especially welcome contributions in:
- Code examples improvements
- Interview questions additions
- Typo corrections and clarity improvements
- Visual diagrams or illustrations
- Edge cases and advanced scenarios
Thank you for helping make JavaScript learning better for everyone! 🙏
Remember: Every small contribution matters. Even fixing a single typo helps thousands of learners!