Live Link - Bookztron
In the project directory, you can run:
Runs the app in the development mode.
Open http://localhost:3000 to view it in your browser.
The page will reload when you make changes.
You may also see any lint errors in the console.
- HTML
- CSS
- JavaScript
- React
- Node JS, Express JS and MongoDb is used for Backend server which is deployed on Vercel.
- User Authentication (Signup, Login and Logout)
- Proper Landing page with categories and New Arrivals
- Product Listing Page
- Sort and filter products
- Sort by Price Low to High and High to Low
- Filter using Minimum and Maximum Price Range
- Filter by Book Genre Categories
- Filter by average product rating
- Filter to include/exclude out of stock products
- Filter products as per fast delivery availability
- Clear all filters
- Wishlist Management
- Add / remove from the wishlist
- Add items to cart
- Cart Management
- Add to cart
- Change items quantity in cart
- Remove from cart
- Add to wishlist from cart
- Apply Coupon
- Single Product Page
- Order Summary of the ordered items
- Custom Toast Component with 4 types - Success, Error, Warning and Information
- Razorpay payment Integration
- Orders page
- Search bar to search books by Book name and Author name
- Pagination
- Create a personal fork of the project on Github.
- Clone the fork on your local machine. Your remote repo on Github is called origin.
- Add the original repository as a remote called upstream.
- If you created your fork a while ago be sure to pull upstream changes into your local repository.
- Create a new branch to work on! Branch from development branch.
- Implement/fix your feature, comment your code.
- Squash your commits into a single commit with git's interactive rebase. Create a new branch if necessary.
- Push your branch to your fork on Github, the remote origin.
- From your fork open a pull request in the correct branch. Target the project's development branch.
- Once the pull request is approved and merged you can pull the changes from upstream to your local repo and delete your extra branch(es).
- And last but not least: Always write your commit messages in the present tense. Your commit message should describe what the commit, when applied, does to the code – not what you did to the code.
- You can read more about this from Github Docs