Inspiration
At my first CS club meeting, there were two boxes of donuts. By the end of the meeting, there was still a box left, and by then no one wanted any more, let alone to take it home. I’ve also seen peers carrying platters of leftover food, going around asking people if they wanted some. Sometimes no one notices, or the timing doesn’t work out, and good food ends up in the trash. Fordham students and clubs never have an easy way to find each other while the food is still hot.
What it does
RamRescue is a live web page where anyone can share leftover food and any student can see what’s available on campus right now.
Post in seconds: a short form asks for the food, quantity, campus (Lincoln Center or Rose Hill), building and room, how long it will be available, and dietary notes. Live feed: new posts appear automatically, newest first, without refreshing the page. Countdown timers: each post shows how much time is left, and it disappears when the time runs out, so students never walk to food that’s gone. Posts turn amber and then red as time runs low, with the word “Hurry,” so urgency doesn’t rely on color alone. Campus filter: students can view Lincoln Center, Rose Hill, or both. Dietary tags: vegetarian, vegan, halal, kosher, and nut warnings are visible on each card. Mobile-friendly and accessible: large text, high contrast, large tap targets, and light and dark modes.
Intended users: posters are club officers, event organizers, and department staff with leftover food. Finders are any Fordham student who wants free food.
How we built it
I built RamRescue solo, using Claude (Anthropic’s AI assistant) to help write the page’s front-end code, which is a single HTML file with CSS and JavaScript. For the data side, I used Google Forms to collect posts and Google Sheets to store them. The Sheet is published as a CSV link, and the page fetches that link every 30 seconds, parses each row, calculates when it expires (post time plus the minutes the poster chose), hides expired posts, and draws a card for each live one. The site is hosted on Netlify, and the code is on GitHub.
I chose this setup because it let me build a working end-to-end pipeline (form, then spreadsheet, then live page) within the six-hour window, with no server or login system to maintain. I also made sure posted text is inserted as plain text, so someone can’t submit a post that runs code on other people’s screens.
Challenges we ran into
Trying to think outside the box was hard. I did this solo, and I had to step out of my comfort zone and focus on what needed to change, rather than what I thought was fine already. Technically, I also hit real debugging problems, including a published link that wasn’t serving my responses tab and a filter that depended on exact text matching, and I had to track each one down step by step.
Accomplishments that we're proud of
Just getting started. This is something I’ve always wanted to do but was too afraid to push boundaries on. I went from an idea to a live, working site that anyone at Fordham can open on their phone today.
What we learned
I learned to improvise with what I had. When I felt like I was done, I kept strategizing about what else the project needed to feel complete. I also learned how a real data pipeline fits together, and that a small tool that works beats a big idea that doesn’t.
What's next for RamRescue
Authorized posters: give access to post food only to verified people, such as club officers, event organizers, and staff, using Fordham sign-in. This would reduce the risk of unsafe food or false posts. Impact metrics: add a dashboard, such as a pie chart, that shows how much food from posts and events was saved, broken down by campus or by event type. “Mark as gone” button so posts disappear as soon as the food runs out. Notifications by email or push, so students know when food is posted. Partnerships with Student Life, clubs, and dining services for a pilot.