# Contributing

Thanks for helping make this repository better.

## How to contribute

1. Pick a section that needs a better workflow, example, diagram, or template.
2. Open an issue with the exact problem and the proposed fix.
3. Fork the repo and create a focused branch.
4. Keep changes practical, copy-pasteable, and beginner-friendly.
5. Add examples, not just theory.
6. Update the README if the navigation changes.
7. Submit a clean pull request with before and after screenshots when relevant.

## Contribution rules

- Prefer implementation over explanation.
- Prefer real tools over vague categories.
- Prefer screenshots, checklists, and templates over long paragraphs.
- Keep the language skimmable.
- Avoid duplicate content across sections.
- Every new guide should answer, “What does the student do next?”

## Good contribution ideas

- Better demo scripts for common hackathon ideas
- New API examples with starter code
- Improved pitch templates
- Faster deployment workflows
- More realistic problem statements
- Better judge-facing talking points
- Additional boilerplates

## Review checklist

- Is it practical?
- Is it accurate enough to be useful?
- Is it easy to scan on mobile?
- Does it reduce hackathon stress?
- Can a beginner copy it and start building immediately?

## Code of conduct

Be respectful. Be useful. Be direct. Build things that help people win.