AggiePlace

AggiePlace is a student-only marketplace proof of concept for North Carolina A&T State University students. The platform allows verified users to browse listings, create listings, filter items, preview item images, and message sellers through a demo messaging flow.

Project Purpose

Public marketplaces are not designed specifically for campus communities. AggiePlace focuses on creating a safer, cleaner, and more trusted buying and selling experience by limiting marketplace access to users with an @aggies.ncat.edu email address.

Main Features

• Student email verification gate
• Sign in and registration demo flow
• Marketplace listing feed
• Listing creation form with image upload
• Search, price, and location filters
• Item image preview modal
• Messaging proof of concept
• Messages page with saved local threads
• Responsive user interface

Tech Stack

• HTML5
• CSS3
• JavaScript
• Browser localStorage for demo persistence
• Git and GitHub for version control

Project Structure

AggiePlace/
├── auth.html
├── index.html
├── messages.html
├── css/
│   └── styles.css
├── js/
│   ├── data.js
│   ├── auth.js
│   ├── app.js
│   └── messages.js
├── assets/
├── docs/
├── screenshots/
└── team-contributions/

How to Run

1. Download or clone the repository.
2. Open auth.html in a modern browser such as Chrome, Safari, or Edge.
3. Register using an email ending in @aggies.ncat.edu.
4. After registration, the app redirects to the marketplace page.
5. Browse listings, create a listing, and test the messaging flow.

Demo Account Requirement

The app requires a simulated Aggie email address. Example:

student@aggies.ncat.edu

Demo Flow

1. Register as a verified student.
2. Browse marketplace listings.
3. Search/filter listings by item, price, or location.
4. View a listing image.
5. Create a new listing.
6. Message a seller.
7. Open the Messages page and view the saved conversation.

Project Boundary

This is a front-end proof of concept for a senior project demo. Authentication, listings, and messages are stored using browser localStorage for demonstration purposes.

In a production version, AggiePlace would use:

• Server-side authentication
• Password hashing
• Session or token-based authorization
• Database-backed listings and messages
• Secure API routes
• Cloud image storage
• Moderation and reporting tools
• Audit logging and stronger input validation

Team Members

• Jamal Hill
• Destiny Ogar
• Clinton Adebomi