# Project export: GreenSlug

This document was generated by HackStack to give an AI agent context about a hackathon project. Sections are labeled with their provenance; content marked as truncated was cut to keep this document small.

## Project metadata

- Hackathon: CruzHacks 2026
- Tagline: Connect farmers with businesses and NPOs in Santa Cruz to sell surplus crops. Results in a efficient food waste solution to sell produce that uplifts the local community.
- Devpost: https://devpost.com/software/greenslug
- GitHub: not linked
- Video: https://player.vimeo.com/video/1155722623?byline=0&portrait=0&title=0#t=
- Team: contributor stats unavailable

## Devpost submission (written by the team)

### Inspiration

Santa Cruz is known for it's strong biodiverse and agriculturally rich ecosystem, but lots of fresh produce goes to waste each years (40% in California). This leads to excessive food waste and pricing issues for farms and consumers (UCSC students and locals). GreenSlug was created because of this issue, since we can use technology bridge communities, uplifting Santa Cruz.

### What it does

GreenSlug is the go-to platform for farmers seeking to sell their produce overflow. It allows farms to list their harvested crops that aren't suitable for grocery stores (often due to shape), and gives consumers a chance to support these farms. The consumers are businesses (restaurants, kitchens, etc.) and NPOs (non-profit organizations) who can bargain for the crops at a reduced price. The software facilitates these transactions by streamlining the process of listing and purchasing, with automated login and purchase authentication.

### How we built it

(Tech Stack) We built GreenSlug as a full-stack web application, using Next.js and Tailwind CSS for the frontend, Auth0 for the passwordless authentication, Typescript for the backend logic, MongoDB Atlas on AWS Cloud for the database and the website is deployed locally.

### Challenges we ran into

The main issue we faced was the file structure for the application, since we were used to the traditional HTML/CSS/JS website development for the Flask/Django, but not for Next.js and Typescript.

### Accomplishments we're proud of

Learned completely new languages and frameworks we didn't know before. While we knew Python, HTML, SQLite and how to use a terminal. We didn't know Typescript, MongoDB, Tailwind CSS, etc. And we learned it all in 36 hours.

### What we learned

The important of parallel collaboration. We didn't have a live coding editor, so everyone had to branch the Github repository and develop their features separately. Understanding how the different aspects of a product come together, from the database to the UI/UX design, was essential to the success of our team.

### What's next

We intend to reach out to local restaurants and kitchens to identify our customer base. Additionally, we would like to integrate Google Maps without web application to show consumers where their produce is being sourced from. We also intend to utilize QR codes to verify delivery of the produce, facilitating the conversations between parties, along with deploying our site on Vercel.

## README (from the GitHub repository)

No README available.

## Detected evidence (automated analysis)

No repository was indexed for this project. Claimed technologies below could not be checked against code.
- AWS (technology) — claimed on Devpost, not found in the code
- CSS (language) — claimed on Devpost, not found in the code
- MongoDB (technology) — claimed on Devpost, not found in the code
- Next.js (technology) — claimed on Devpost, not found in the code
- React (technology) — claimed on Devpost, not found in the code
- Tailwind CSS (technology) — claimed on Devpost, not found in the code
- TypeScript (language) — claimed on Devpost, not found in the code

## Codebase structure

No repository index available.

## Key source files

No repository index available; no source files included.