<aside> 📌

Welcome to the #75HER Developer Docs

This is your central build library for the hackathon. Inside you’ll find curated APIs, SDKs, datasets, and development tools across every track. All resources are free or offer free tiers suitable for rapid prototyping.

Your objective: Build fast. Ship a working prototype. Avoid over-engineering.

This resource hub is designed to eliminate friction and accelerate shipping.

</aside>

<aside> 💚

New to Hackathons?

First hackathon? You’re in the right place.

Here’s how to make it enjoyable and successful:

• Use managed services — they remove unnecessary setup stress
• Skip custom infrastructure — this isn’t the time for deep DevOps experiments
• Focus on delivering a working live demo

Your goal isn’t perfection. It’s progress.

Ship something real. That’s how confidence is built.

</aside>

The best way to predict the future is to build it - #75HER

<aside> ⭐

Primary AI Partner

for this hackathon is Goose by Block.

Goose is an open-source AI agent that runs locally and connects directly to your development environment. It allows you to generate and refactor code, debug issues, manage files, execute shell commands, interact with APIs and accelerate prototyping. Think of it as an AI engineering copilot embedded in your workflow.

Repository: https://github.com/block/goose

Cost: Free & Open Source

⚠️ REQUIRED for AI/ML Track: All AI/ML track submissions MUST integrate Goose. This is mandatory for track eligibility, not optional.

Recommendation: Pair Goose with your primary stack to reduce friction and maintain momentum.

</aside>

📚 Resource Sections

Sections

📋 Required Hackathon Documentation Templates

<aside> ✅

All submissions must include proper documentation. Download these templates to structure your project for judging.

</aside>

📄 Download Templates

These templates help you meet submission requirements and demonstrate technical rigor:

1. 4-Line Problem Frame Template — Define your user, problem, constraints, and success test before you build ⭐ Start here
2. Decision Log Template — Document 5-10 key technical choices and tradeoffs
3. Risk Log Template — Track issues found and fixed (Min 1 required; competitive submissions have 3-5)
4. Evidence Log Template — Cite all sources and licenses (Min 3 required; strong submissions have 8-12)
5. README Template — Complete project documentation structure
6. Complete Hackathon Resources Guide — Full guide with tips, tools, and best practices

🎯 What Judges Look For

<aside> 💡

Pro tip: Start your Decision Log and Evidence Log early—don't wait until the last day! Strong documentation sets competitive submissions apart.

</aside>