Skip to content

darazuiscaptain/ZombieMarket

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

ZombieMarkt e-commerce

Description

These are two front end applications e-commerce + inventory manager(CRUD), that interacts between each other via a third application, a nodeJs rest api server; all together emulates on a very small scale how i imagine a propper shopping application works. on One hand the Inventory Manager perfoms CRUD operations such as creating products, edit them, and deleting products; and the e-commerce creates an order entry and creates users.

More detailed information awaits inside of each applications readme file


Application A - Inventory Manager - Frontend💻

This application is meant to be used by the warehouse worker of the shop, where they would be able to inbound incomming products, outbound them when they expire, and for this demonstration i included other pages to check all the orders that users have created on the e-commerce, as well as listing all the existing users and also all products. The delete page works fine but when deleting an item, it might break some pages of the e-commerce that feed from that product, ex: Profile page.


Application B - E-Commerce - Frontend💻

This application is used by Users to create orders, signup, login, and they can also post comments on different products under the product detail page, as well as mark some product as their favorite, as many favorites as they want. The add to cart functionallity is the same as my previous app (rich-simulator), as well as the checkout page, only one product gets added to the cart; and if the addToCart button gets triggered again, the product then is removed from cart (to avoid duplicate products on the cart)


Application C - Node server - Backend💾

The server side of my Zombiemakrt app (MongoDB, Express, React, Node.js) application is built using Node.js with Express framework. It serves functions based on different endpoints, which are implemented following the REST (Representational State Transfer) architectural style; and by using mongoose's schemas and methods perfom the necessary operations to push, edit or delete documents in the mongoDB database.

Releases

No releases published

Packages

No packages published

Languages