|
1 | 1 | --- |
2 | | -title: Documentation |
| 2 | +title: How To Contribute |
3 | 3 | layout: default |
4 | 4 | nav_order: 2 |
5 | 5 | description: "Course notes and resources for DataTalks.Club Zoomcamps" |
6 | 6 | has_children: true |
7 | 7 | --- |
8 | 8 |
|
9 | | -# Course Documentation |
| 9 | +# How To Contribute |
10 | 10 | {: .fs-9 } |
11 | 11 |
|
12 | | -Welcome to the documentation section for DataTalks.Club Zoomcamps. |
13 | | -{: .fs-6 .fw-300 } |
| 12 | +Welcome to the DataTalks.Club Zoomcamps Notes repository! This is a community-driven resource that helps thousands of learners worldwide. Your contributions make a real difference in supporting fellow data enthusiasts on their learning journey. |
14 | 13 |
|
15 | | -1. **Choose a Course**: Pick one that matches your interests and career goals |
16 | | -2. **Join the Community**: Connect with fellow learners on [Slack](https://datatalks.club/slack.html) |
17 | | -3. **Start Learning**: Dive into the notes and begin your journey |
18 | | -4. **Get Support**: Ask questions and share your progress |
| 14 | +## Ways to Contribute |
19 | 15 |
|
20 | | -**Remember**: All courses are completely free and designed by practitioners for real-world application! |
| 16 | +- Contribute course notes and summaries |
| 17 | +- Report typos, grammatical errors, or unclear explanations |
| 18 | +- Fix broken links and outdated information |
| 19 | +- Correct technical inaccuracies |
| 20 | +- Improve existing explanations with better examples |
| 21 | +- Add visual aids like diagrams or screenshots |
| 22 | +- Reorganize content for better flow and readability |
| 23 | + |
| 24 | +## Detailed Contribution Process |
| 25 | + |
| 26 | +### 1. Getting Started |
| 27 | + |
| 28 | +#### Prerequisites |
| 29 | +- GitHub account |
| 30 | +- Basic knowledge of Git and Markdown |
| 31 | +- Familiarity with the course content you want to contribute to |
| 32 | + |
| 33 | +#### **Repository Setup** |
| 34 | +1. **Fork the Repository**: Click the "Fork" button on the main repository page |
| 35 | +2. **Clone Your Fork**: |
| 36 | + ```bash |
| 37 | + git clone https://github.com/YOUR_USERNAME/zoomcamps-notes-faq.git |
| 38 | + cd zoomcamps-notes-faq |
| 39 | + ``` |
| 40 | +3. **Add Upstream Remote**: |
| 41 | + ```bash |
| 42 | + git remote add upstream https://github.com/DataTalksClub/zoomcamps-notes-faq.git |
| 43 | + ``` |
| 44 | + |
| 45 | +### 2. Making Changes |
| 46 | + |
| 47 | +#### **Branch Creation** |
| 48 | +Always create a new branch for your changes: |
| 49 | +```bash |
| 50 | +git checkout -b feature/your-contribution-description |
| 51 | +``` |
| 52 | + |
| 53 | +Use descriptive branch names like: |
| 54 | +- `fix/ml-zoomcamp-week3-typos` |
| 55 | +- `add/data-engineering-kafka-notes` |
| 56 | +- `improve/llm-zoomcamp-rag-examples` |
| 57 | + |
| 58 | +#### **Content Guidelines** |
| 59 | + |
| 60 | +**Writing Style**: |
| 61 | +- Use clear, concise language |
| 62 | +- Write in an educational, friendly tone |
| 63 | +- Include practical examples and real-world applications |
| 64 | +- Structure content with proper headings and bullet points |
| 65 | + |
| 66 | +**Technical Content**: |
| 67 | +- Test all code examples before submitting |
| 68 | +- Include necessary imports and dependencies |
| 69 | +- Add comments explaining complex logic |
| 70 | +- Provide context for when and why to use specific approaches |
| 71 | + |
| 72 | +**Formatting Standards**: |
| 73 | +- Use consistent Markdown formatting |
| 74 | +- Follow the existing file structure and naming conventions |
| 75 | +- Include proper front matter for new pages |
| 76 | +- Optimize images and use appropriate alt text |
| 77 | + |
| 78 | +### Submitting Your Contribution |
| 79 | + |
| 80 | +#### **Commit Best Practices** |
| 81 | +- Write clear, descriptive commit messages |
| 82 | +- Make atomic commits (one logical change per commit) |
| 83 | +- Use conventional commit format when possible: |
| 84 | + ``` |
| 85 | + feat: add machine learning zoomcamp week 5 notes |
| 86 | + fix: correct linear regression formula in week 2 |
| 87 | + docs: improve contribution guidelines |
| 88 | + ``` |
| 89 | + |
| 90 | +#### **Pull Request Process** |
| 91 | +1. **Push Your Branch**: |
| 92 | + ```bash |
| 93 | + git push origin your-branch-name |
| 94 | + ``` |
| 95 | + |
| 96 | +2. **Create Pull Request**: |
| 97 | + - Go to your fork on GitHub |
| 98 | + - Click "New Pull Request" |
| 99 | + - Select your branch and the main repository's main branch |
| 100 | + - Fill out the pull request template |
| 101 | + |
| 102 | +3. **Pull Request Description Should Include**: |
| 103 | + - Clear title summarizing the changes |
| 104 | + - Detailed description of what was added/changed |
| 105 | + - Context for why the change is beneficial |
| 106 | + - Any relevant issue numbers |
| 107 | + - Screenshots for visual changes |
| 108 | + |
| 109 | +## Content Organization |
| 110 | + |
| 111 | +### Repository Structure |
| 112 | +``` |
| 113 | +docs/ |
| 114 | +├── machine-learning-zoomcamp/ |
| 115 | +│ ├── 01-intro/ |
| 116 | +│ ├── 02-regression/ |
| 117 | +│ └── ... |
| 118 | +``` |
21 | 119 |
|
22 | 120 | --- |
23 | 121 |
|
24 | | -*Need specific help? Join our [Slack community](https://datatalks.club/slack.html) and ask in the course-specific channels!* |
| 122 | +*Questions? Join our [Slack community](https://datatalks.club/slack.html) and ask in the `#general` channel or the course-specific channels. Our community is always happy to help new contributors get started!* |
0 commit comments