Project Info
Inspiration
One week ago I lost my air pods on my walk back from the gym. Throughout the week I searched up and down the path I took looking for where it could have gone but I never saw my beloved earphones again. Losing things is common everywhere but a problem unique to Santa Cruz is someone returning the item, but the owner not knowing where the item was returned. With so many buildings, each with their own Lost and Found, it is too easy to lose items and never see them again.
What it does
Instead of having a lost and found in each building, SlugSearch creates a centralized Lost and Found where students can post and find lost items.
How we built it
We used Visual Studio Code to create a front-end in HTML, back-end in Python, Flask to connect front to back end, Css for formatting, and Javascript for a few functions.
Challenges we ran into
We had three major challenges. The first was learning how to program in HTML because neither of us had used it before. The second challenge was using SQL for our database because neither of us used that either. The final challenge was figuring out how to connect the HTML front-end to the Python back-end.
Accomplishments we're proud of
We are proud of how nice the user interface looks, how accessible the website is, and how much we learned over this experience.
What we learned
We learned a lot of languages on the fly like HTML, CSS, and Javascript. We also learned how to connect front-end programming in HTML to back-end programming in Python programming using Flask.
What's next
SlugSearch is implementing AI using Google Bard to allow users to only take a picture of the item and allow the AI to fill in all the information automatically, including; what the object is, and its description. We will also create a mobile app to make SlugSearch more accessible and convenient.
SlugSearch
A lost and found web app built for UC Santa Cruz. Students can post lost or found items with a photo, location, and category, and browse or filter listings to reunite people with their belongings.
Features
- Upload a photo of a lost or found item
- Tag items by campus location and category
- Filter the feed by location and/or category
- Claim an item to remove it once it's been returned
- SQLite database to persist all listings
Supported Locations
Cowell, Stevenson, Crown, Merrill, College 9, JRL, Porter, Kresge, RCC, Oakes, McHenry, S&E Library, Other
Supported Categories
Headphones, Bottles, Jackets, Hats, Keys, Wallets, Other
Tech Stack
- Backend: Python, Flask, Flask-SQLAlchemy
- Database: SQLite
- Frontend: HTML, CSS
Analysis
View
Metric
- 1
Figures cover GitHub contributors during the hackathon window. A co-authored commit counts in full for each author, so per-member totals add up to more than the whole-team figures.
Technology
- CSSIn code
- HTMLIn code
- PythonIn code
- FlaskClaimed
- JavaScriptClaimed
- SQLClaimed
3 of 6 appear in the indexed code. 3 claimed on Devpost could not be matched to code, which may simply mean the tool leaves no trace in the repository.
AI coding agents
No AI coding agent signals were found in this repository.
Detected from committed agent config files and commit authorship. Absence of a signal is not proof an agent was unused.
Codebase size
Source size
22 KB
Source files
6
Counts recognized source files only; vendored directories, binaries and lockfiles are excluded, so this is smaller than the repository on disk.
Repository
waterball01/SlugSearch
35 files · 3.7 MB · @ afb05cd
Structure
Interface
2 files · 6%Screens, components and styles rendered to the user.
Application logic
2 files · 6%Domain rules, services and shared utilities.
Supporting
Layers are inferred from where files sit in the tree, not from reading the code. A project that names its directories unconventionally will read oddly here — open the file browser to check anything the diagram implies.
Languages
- CSS43%
- HTML36%
- Python18%
- Markdown3%
Share of indexed source by file size. Binary and vendored files are excluded.
This project’s features have not been analysed yet.
Export this project's context (description, README, evidence, key source files) to chat with an AI agent elsewhere.