8.1-Restaurant Menu-ColemanCox

[ColemanCox]

Tasks

Getting Started

• [ ] Create a new Ember CLI application
• [ ] Produce a mockup or wireframe for the different screens
• [ ] Setup templates for the different dynamic portions of the application
• [ ] Produce static data for the menu items

  Menu

• [ ] Fetch and console.log the static JSON for the menu items
• [ ] Render a template for each menu item, not according to category
• [ ] Define a Model to represent menu items
• [ ] Define a Component to represent the list of food items
• [ ] Make a Component responsible for each individual item in the menu
• [ ] console.log the food model when I click on its price button
• [ ] Define a Model to represent an order
• [ ] Create an order service or route to manage adding order items
• [ ] console.log the order when I click on the foods price
• [ ] Add the food model to the order when the price is clicked
• [ ] Separate the menu items by category
• [ ] Optionally make a Component for each Category of menu items

  Order Sidebar

• [ ] Create an Order Component to show the current order being built
• [ ] Add an instance of the Order Component to your route template
• [ ] console.log the order whenever an item is added to the order
• [ ] Show each item in your order in your component template
• [ ] In your order model, define a subtotal computed property that shows the price of all of the added items
• [ ] Show the subtotal for your order in your Order Component template
• [ ] Save the order data to tiny-lr or Firebase when the order is submitted with related menu items

  Back of House

• [ ] Create a route group for logging in to the back of house system
• [ ] Create a back of house index for all menu items
• [ ] Create a back of house create view for new menu items
• [ ] Create a back of house edit view for existing menu items
• [ ] Create a back of house action for destroying existing menu items
• [ ] Create a back of house index for orders showing the total price
• [ ] Create a back of house detail view for seeing the purchased items for a single order

  Hard Mode

• [ ] Validate to make sure that a user does not submit an empty order
• [ ] Using a password (this can be set as a string in your code), restrict access to the back of house systems
• [ ] Allow staff members to mark an order as completed