Skip to main content
Thank you for considering contributing to this repository! This collection is built by the hackathon community, for the hackathon community.

​
How to contribute

​
Adding a new resource

1

Fork the repository

Create your own fork of the Hackathon Resources repository to start making changes.
2

Choose the appropriate category

Select the category that best fits your resource:
  • frontend/ - UI components, styling tools
  • data-apis/ - APIs, web scraping, search tools
  • ai-ml/ - ML models, AI platforms, agent frameworks
  • voice-comms/ - Real-time communication, voice AI
  • deployment/ - Hosting, VPS, infrastructure
3

Update the category README

Add your resource following the format shown in the Style Guide section below. Include the tool name, description, key features, free tier details, and why it’s valuable for hackathons. Add code examples where applicable.
4

Update main README.md

If your addition is significant, update the main README.md to reflect the new resource.
5

Submit a pull request

Create a PR with:
  • Clear title (e.g., “Add Cloudflare Workers to deployment”)
  • Description of why this tool is valuable
  • Any personal experience using it in hackathons

​
What we’re looking for

Good additions

  • Tools with generous free tiers
  • India-specific platforms (Razorpay, etc.)
  • Emerging AI/ML platforms
  • Real-time/WebRTC technologies
  • Developer tools that save time
  • Personal battle-tested recommendations

Not suitable

  • Paid-only services
  • Deprecated or unmaintained projects
  • Generic alternatives to listed tools
  • Tools requiring lengthy setup

​
Quality standards

Maintain high quality contributions by following these standards:
Verify pricing and free tier details before submitting. Double-check that all information is current and correct.
Write concise, actionable descriptions. Avoid jargon and keep explanations focused on practical value.
Include code snippets where helpful. Show real-world usage that demonstrates the tool’s value in hackathon scenarios.
Share real hackathon use cases. Explain why this tool helped you or would help others in a hackathon context.

​
Style guide

​
Resource entry format

Use this consistent format for all resource entries: 
### [Tool Name](https://official-url.com/)
**Brief tagline (5-10 words)**
- **Feature 1**: Description
- **Feature 2**: Description
- **Pricing**: Free tier details

**Why use it:** Real hackathon benefit in 1-2 sentences.

​
Code examples

When adding code examples to your resource entries:
  • Use language-specific syntax highlighting
  • Include comments for complex logic
  • Keep examples under 20 lines when possible
  • Show real-world usage, not just “hello world”

​
Reporting issues

Help us keep the repository accurate and up-to-date:
  • Broken links: Open an issue with [BROKEN LINK] in title
  • Outdated pricing: Include current pricing in issue
  • Incorrect info: Provide source for correction

​
Recognition

Your contributions matter! Contributors will be:
  • Listed in repository insights
  • Mentioned in release notes for major additions
  • Part of building the go-to hackathon resource

​
Questions?

Open an issue with the appropriate tag:
  • [QUESTION] tag for general inquiries
  • [SUGGESTION] tag for new categories or structure
  • [HELP] tag if you need guidance contributing
Let’s build the best hackathon toolkit together!

Build docs developers (and LLMs) love

Get started for freeTalk to us