Click here for screencast presentation covering the areas below
Before the user is logged in, the user can view the products and other pages, including the shopping cart. As the user adds products to the shopping cart, the cart counter will go up. The cart counter will be in the navigation bar that will be included on every page. The shopping cart page will be a separate page and accessible by clicking on the cart in the navigation bar. The page will allow the user to edit the quantity of each item and remove items from the cart, but the quantity will be limited to the inventory available. The page will also display the taxes and shipping costs. However, a purchase cannot be made unless the user is logged in. If the user is not logged in when selecting purchase, then the user will be directed to the login page.
Sessions will be used to manage quantity selected for the products in the shopping cart. The shopping cart data that will be stored in the session will include the product name, price, and quantity. The data will be stored as an array of objects. Here’s an example of the product array and the objects stored in the array for the data: “point & shoot” [{“name”: “Canon IXUS 50”, “price”: 50.00, “quantity”: 1}]; The cart array will be stored in the session so that the user can move between pages and the session data will be stored in the memory of the server.
Access will be limited to logged in users (or registered for new account). By using cookies, only successfully logged in users will be able to access their invoice. If the user is not logged in then the user will not be able to access the invoice page after completing their purchase in the shopping cart.
Considering personalization in the navbar or on every page beneath the nav bar once the user is logged in. The text might say, “Aloha, Mr. Name.” The name will also be displayed on the invoice, “Thank you for your purchase, Mr. Name!” Personalization will also be required to email the user the completed invoice for the transaction.
I’m not working with partners.
Start as early as possible, but think through how to set up the webpages, including how I want to the pages to behave before jumping into coding. I need to focus on organizing my thoughts and approach to carrying out the requirements first.