ENSURE TO FOLLOW THE MLH CODE OF CONDUCT

## Requirements

- Two google technologies must be used in the project

- Solution must be an solution to one of the prompts or associated idea

Prompts: 

Prompt 1: The June Bug Center struggles to keep parents informed about class schedules, updates, and announcements due to fragmented communication methods like flyers, texts, and word-of-mouth. This leads to missed classes, confusion, and low engagement. Build a simple, user-friendly web or mobile system that centralizes class scheduling and communication for the June Bug Center. Parents should be able to view upcoming classes, receive reminders, and see important announcements in one place. Staff should be able to easily add or update class details (name, time, instructor, availability) and send notifications for changes or upcoming events. All data should be stored in a simple database or spreadsheet, making it easy to manage and realistic to build within a week-long hackathon.

Prompt 2: The June Bug Center faces challenges in organizing and tracking volunteer schedules, often leading to missed shifts, last-minute cancellations, and gaps in coverage. Volunteers currently lack a simple system to plan their hours in advance and receive consistent reminders, which affects accountability and operational efficiency. Build a lightweight scheduling and reminder system that allows volunteers to sign up for available shifts, view their scheduled hours, and receive automated reminders before their shifts. Staff should be able to easily post available time slots, approve volunteer schedules, and track attendance or completed hours. The system should be simple enough to build in a week-long hackathon and store all scheduling data in a basic database or spreadsheet for easy management.

Prompt 3:
The Green Market Farm greatly struggles to advertise their products and manage orders due to limited technical knowledge. They rely on word-of-mouth or other outdated methods, causing them to lose potential customers and revenue. Build a simple, accessible system/website that allows farm owners to easily showcase their products, manage incoming orders, and track inventory without requiring advanced technical skills. The system should include a clean, visually appealing interface for customers to browse available goods, place orders, and view farm information. On the backend, it should allow farmers to quickly add or update products (name, category, price, availability), and maintain basic record. After the order is put through it could be saved in a database or a spreadsheet for the owner.

Prompt 4: VT Food Pantry Inventory System, The VT Food Pantry runs two programs (open-hours pantry and a grocery setup) and currently tracks everything in a physical notebook re-entered manually into Excel. Build them a simple inventory system where staff can log incoming food by name, vendor, weight, units, category, unit or weight pricing, and program assignment,  and quickly add more stock by looking up an existing item rather than re-entering it. The system should support vendor invoice tracking, periodic inventory checkpoints that set a new baseline, transfers between the two programs, and an end-of-year rollover that calculates totals and carries remaining stock forward. Hard constraints: no barcodes, no student checkout tracking. The best solution is one a non-technical volunteer can actually use.

Prompt 5:

Build a real estate data ingestion engine for a submarket of your choice. Pull from multiple public sources, normalize it, and surface it in a geospatial dashboard that makes a developer or analyst instantly smarter about that market. Think about what it would feel like if someone could open your tool, pick a city or neighborhood, and immediately see a living picture of what's happening there, rents, permits, job growth, vacancy, migration — all tied to the map. That's what we're after.

A strong submission has a data pipeline pulling from public sources (FRED, Census ACS, HUD, Zillow, building permit APIs, Google Trends, whatever you find), outputs clean structured data, and visualizes it spatially using Google Maps. Heatmaps, overlays, submarket boundaries, use whatever tells the story best. Bonus points if it's dynamic and lets a user pick a market and have the engine pull and render on the fly.