Full-stack e-commerce · university capstone
One marketplace. Two sides of the system.
A full-stack clothing marketplace connecting customer shopping flows, account management, administration, and relational product data.
- HTML5
- CSS3
- JavaScript
- PHP
- MySQL
- phpMyAdmin
1 / 7
Marketplace system
Inside the marketplace.
One commerce system connecting the customer storefront, application logic, relational data, and administrative control.
Customer experience
StorefrontMystic commerce core
PHP
Application logic
MySQL
Relational data
One shared data layer powers storefront interactions and administrative management.
Administration
ControlCustomer experience
From sign-up to product discovery, cart, wishlist, and profile management.
A focused entry point for returning shoppers.
New-account registration captures the essential shopper details.
Storefront categories provide a direct route into the collection.
Category pages display individual clothing products in a browseable grid.
Product details support quantity selection, cart, and wishlist actions.
Profile management keeps account details under the customer’s control.
The contact experience gives shoppers a titled route to the administrator.
An about page provides the storefront’s brand and service context.
Administration
CRUD tools for managing users, products, categories, and inventory details.
The administration area starts from a lightweight operational home screen.
User records can be reviewed and managed from the admin interface.
Products are managed through a practical table-based CRUD workflow.
An editing form supports individual product updates.
Category records are managed alongside product inventory.
Data foundation
Relational data behind the marketplace.
MySQL connects the marketplace's products, categories, brands, customer accounts, and related commerce data.
- 01
Products
PRODUCT DATAMarketplace inventory, product details, pricing, and quantities.
- 02
Categories
STOREFRONT ORGANIZATIONOrganizes the storefront collection into browsable product groups.
- 03
Brands
PRODUCT CONTEXTAssociates marketplace products with their brand information.
- 04
Users / accounts
CUSTOMER DATAStores customer account details alongside cart and wishlist information.
The MySQL model connects user accounts with products, brands, and categories.
Recorded flows
Core marketplace interactions documented end to end.
Home experience
Shop and category browsing
Login flow
Administrator workflow
Cart flow
Profile editing
Built with PHP, MySQL, and a customer-first web interface.
Project context
University
capstone
The goal
Build an end-to-end commerce application covering both the shopper experience and the operational side of maintaining marketplace data.
Customer + admin + data
Engineering decisions
Foundations behind the build.
Relational commerce data
Products, categories, brands, and accounts are represented through a MySQL-backed relational structure.
MYSQL / DATA MODEL
Role-separated experiences
Customer shopping workflows and administrative management are presented through dedicated interfaces.
CUSTOMER / ADMIN
Server-side application logic
PHP connects interface actions with authentication, product management, and persistent application data.
PHP / APPLICATION
Project reflection
What this project taught me.
Mystic Marketplace brought customer-facing development, server-side application logic, administration, and relational data together in one end-to-end project.
Full-stack ownership
Connecting frontend workflows to PHP application logic and persistent MySQL data.
INTERFACE → PHP → MYSQL
Relational thinking
Structuring users, products, categories, brands, carts, and related commerce information.
USERS · PRODUCTS · CATEGORIES · BRANDS
Operational tooling
Building not only the customer interface, but the administration required to maintain marketplace content and records.
CUSTOMER ↔ ADMIN