Food Ordering Application
For Customers
- Users can create their account in our database and sign in.
- Once the user is successfully signed in, they will be redirected to the Homepage.
- The user can see all the restaurant currently available.
- The home page also contains a search bar to search for a particular restaurant by its name.
- The user can also sort the restaurants depending on various Categories like Chinese, Burgers, etc or according to the delivery time, Veg Only, Rating.
- The user can order from only one specific restaurant.
- Also, the user can view their order history in the Past Orders Page.
- Also, the user can view their personal details, and can also update them.
- Also, the user can change their current password.
- On the Restaurant Page, the user can search for a particular dish using the search bar.
- Once ordered the user can see the order details.
- Users can also rate the order.
For Restaurant Owners
- Restaurant Owners can login using the Restaurant Name and its corresponding password.
- The owner can update their current dish name, price, description, dish image, its category.
- The owner can also add new dishes on its current restaurant page.
- Landing page:
- The landing page contains the overview of the website about how we intend the users to use this website.
- Sign in and sign up page :
- All the checks have been made on the frontend side for email and password. For example, we have defined the password pattern that the user must enter while signing up.
- Home Page :
- Once the user is signed in, a user id is generated, saved in Local Storage, which helps maintain session activity. This user id is verified every time the user visits any page. A Sliding Banner is implemented, using JS and CSS. Once logged in, the browser would prompt for the users location, which will be displayed in the Navigation Bar. It also includes a Search Bar used to search for various restaurants. Once the restaurant is finalized by the user, they are transfered to that particular restaurant's page.
- Restaurant Page :
- Restaurant Page contains various details regarding that restaurat, like delivery time, location, rating, restaurant type and the offers available at the moment. Below the restaurant banner, the user can view various dishes, and add them to the cart, on the right. After finalising the dishes the user can place the order and view its details on the Order Details Page.
- Order Details Page :
- User can view the current order, all the dish details, along with the Bill Details. And there is also an option for rating the order, which then gets added to the restaurant's overall rating.
- Past Order Page :
- User can view their accounts past order history, with the Total Bill and the exact date and time of the order, the restaurant's name.
- Account Page :
- The account details of the user can be viewed and updated. The user can also change their current password, using the old password.
- Restaurant Owner page :
- The restaurant owner can edit their existing dish, by using the Edit Dish Button, then a modal window would pop up, which contains the dish information, that can be edited - dish name, image link, price, catergory, and description.
- Now the onwer can also add new dish using the Add Dish Button, and all the above details must be filled.
- View Routes
/
/login
/signup
/loginRestaurant
/overview
/pastOrders/:userId
/restaurant/:slug
/me
/orderPlaced/:id
/restaurantOwner/:restaurantId
/orderDel/:orderId
/resAuth
/orderDetails
/pastOrders
- API Routes
/api/v1/restaurants
/api/v1/restaurants/:restaurantId/reviews
/api/v1/restaurants/:id
/api/v1/restaurants/:restId/:dishId
/api/v1/users/signup
/api/v1/users/login
/api/v1/users/logout
/api/v1/users/forgotPassword
/api/v1/users/resetPassword/:token
/api/v1/users/me
/api/v1/users/updatePassword
/api/v1/users/updateMe
/api/v1/users
/api/v1/users/:id
/api/v1/reviews
/api/v1/reviews/:id
/api/v1/orders
/api/v1/orders/:id
/api/v1/orders/checkout-session/:orderId
| Packages | README |
|---|---|
| bcrypt | To store hashed password in database |
| dotenv | To keep db connection string, client id, client secret key safe |
| nodemon | To run application in dev mode |
| pug | To Embed JavaScript code in a template that is then used to generate HTML |
| cookie-parser | To store or access session (JWT token) data |
| jsonwebtoken | To authenticate requests |
| helmet | Help secure Express/Connect apps with various HTTP headers |
| hpp | Express middleware to protect against HTTP Parameter Pollution attacks |
| mongoose | Mongoose MongoDB ODM |
| stripe | For handling payments |
| nodemailer | For sending e-mail from your Node.js applications |
| slugify | Slugifies a String |
Execute node app.js in terminal after cloning the project
Note that database connection string & secret keys are in env file which are not uploaded on github
- Github: @pawarpranav83
- LinkedIn: @pranav-pawar
- Gmail: mail
- Instagram: @pranav.pawar_
Give a ⭐️ to this project if you liked it