Skip to main content

Weekly Challenge

Use this page to keep the repository active and give contributors a practical one-week target.

Challenge format​

Every weekly challenge should produce one concrete outcome:

  • a merged chapter improvement
  • a new diagram
  • a starter project upgrade
  • a README or docs UX improvement
  • a validation or smoke-check improvement

Suggested weekly structure​

Monday​

  • pick one issue
  • define acceptance criteria
  • identify the docs or project files involved

Tuesday to Thursday​

  • implement the change
  • capture screenshots if the UI changes
  • run the smallest relevant validation commands

Friday​

  • open the PR
  • summarize learner impact
  • note next follow-up ideas

Sample weekly challenges​

  1. Improve one project doc with a better architecture diagram.
  2. Add one evaluation walkthrough to an existing chapter.
  3. Replace one vague paragraph with a concrete code-backed explanation.
  4. Add one recruiter-friendly portfolio tip to a learning-path page.
  5. Improve one screenshot or docs visual asset used on the homepage.

Good challenge rules​

  • one week
  • one practical improvement
  • one measurable learner outcome
  • no giant refactors disguised as beginner issues

Best use for community growth​

This page works well when paired with:

  • good first issue labels
  • monthly contributor shout-outs
  • LinkedIn or Dev.to recap posts about what shipped