Skip to content

Latest commit

 

History

History
221 lines (175 loc) · 11.9 KB

README.md

File metadata and controls

221 lines (175 loc) · 11.9 KB

StudyNotion Online Education Platform (MERN App) Website Link

GitHub code size in bytes GitHub last commit GitHub stars My stars GitHub forks Code size Languages Top Issues Watchers

study-notion-demo.mp4

Tech Stack

Client: React, Redux, TailwindCSS, HTML, CSS, JavaScript

Server: Node, Express, MongoDB, Razorpay

Deployment: Docker, Kubernetes, AWS EKS

Project Description

StudyNotion is a fully functional ed-tech platform that enables users to create, consume, and rate educational content. The platform is built using the MERN stack, which includes ReactJS, NodeJS, MongoDB, and ExpressJS. StudyNotion aims to provide:

  • A seamless and interactive learning experience for students, making education more accessible and engaging.
  • A platform for instructors to showcase their expertise and connect with learners across the globe.

StudyNotion is a versatile and intuitive ed-tech platform that is designed to provide an immersive learning experience to students and a platform for instructors to showcase their expertise. In the following sections, we will delve into the technical details of the platform, which will provide a comprehensive understanding of the platform's features and functionalities.

System Architecture

The StudyNotion ed-tech platform consists of three main components: the front end, the back end, and the database. The platform follows a client-server architecture, with the front end serving as the client and the back end and database serving as the server.

Front-end

The front end of the platform is built using ReactJS, ReactJS allows for the creation of dynamic and responsive user interfaces, which are critical for providing an engaging learning experience to the students. The front end communicates with the back end using RESTful API calls

Back-end

The back end of the platform is built using NodeJS and ExpressJS,. The back end provides APIs for the front end to consume, which include functionalities such as user authentication, course creation, and course consumption. The back end also handles the logic for processing and storing the course content and user data.

Database

The database for the platform is built using MongoDB, which is a NoSQL database that provides a flexible and scalable data storage solution. MongoDB allows for the storage of unstructured and semi-structured data. The database stores the course content, user data, and other relevant information related to the platform.

Deployment

This project has been deployed using Docker, Kubernetes, and AWS EKS. Docker is used to containerize the application, creating a standalone executable package that includes everything needed to run the application - the code, runtime, libraries, and system tools. This ensures that the application runs the same way in every environment. Kubernetes, a powerful container orchestration system, is then used to manage these Docker containers. It handles tasks like scaling (increasing or decreasing the number of container instances based on demand), self-healing (restarting containers that fail), and rolling updates (gradually updating containers to a new version).

AWS EKS (Elastic Kubernetes Service) is the specific Kubernetes service used for this project. EKS is a managed service that makes it easier to run Kubernetes on AWS, as it eliminates much of the manual configuration and management involved in setting up a Kubernetes cluster. It integrates with other AWS services for storage, networking, and security, making it a robust solution for deploying applications at scale.

Architecture Diagram

Here is a high-level diagram that illustrates the architecture of the StudyNotion ed-tech platform:

Architecture

Front End

The front end of StudyNotion has all the necessary pages that an ed-tech platform should have. Some of these pages are:

For Students:

  • Homepage: This page will have a brief introduction to the platform, as well as links to the course list and user details.
  • Course List: This page will have a list of all the courses available on the platform, along with their descriptions and ratings.
  • Wishlist: This page will display all the courses that a student has added to their wishlist.
  • Cart Checkout: This page will allow the user to complete the course purchase.
  • Course Content: This page will have the course content for a particular course, including videos, and other related material.
  • User Details: This page will have details about the student's account, including their name, email, and other relevant information.
  • User Edit Details: This page will allow the student to edit their account details.

For Instructors:

  • Dashboard: This page will have an overview of the instructor's courses, as well as the ratings and feedback for each course.
  • Insights: This page will have detailed insights into the instructor's courses, including the number of views, clicks, and other relevant metrics.
  • Course Management Pages: These pages will allow the instructor to create, update, and delete courses, as well as manage the course content and pricing.
  • View and Edit Profile Details: These pages will allow the instructor to view and edit their account details. PAGE 3 For Admin (this is for future scope):
  • Dashboard: This page will have an overview of the platform's courses, instructors, and students.
  • Insights: This page will have detailed insights into the platform's metrics, including the number of registered users, courses, and revenue.
  • Instructor Management: This page will allow the admin to manage the platform's instructors, including their account details, courses, and ratings.
  • Other Relevant Pages: The admin will also have access to other relevant pages, such as user management and course management pages.

To build the front end, we use frameworks and libraries such as ReactJS, We also use CSS and Tailwind, which are styling frameworks that help make the user interface look good and responsive. To manage the state of the application, we use Redux, which is a popular state management library for React.

Back End

Description of the Back-end Architecture: StudyNotion uses a monolithic architecture, with the backend built using Node.js and Express.js, and MongoDB as the primary database.

Features and Functionalities of the Back-end: The back end of StudyNotion provides a range of features and functionalities, including:

  1. User authentication and authorization: Students and instructors can sign up and log in to the platform using their email addresses and password. The platform also supports OTP (One-Time Password) verification and forgot password functionality for added security.
  2. Course management: Instructors can create, read, update, and delete courses, as well as manage course content and media. Students can view and rate courses.
  3. Payment Integration: Students will purchase and enrol on courses by completing the checkout flow that is followed by Razorpay integration for payment handling.
  4. Cloud-based media management: StudyNotion uses Cloudinary, a cloud-based media management service, to store and manage all media content, including images, videos, and documents.
  5. Markdown formatting: Course content in document format is stored in Markdown format, which allows for easier display and rendering on the front end.

Frameworks, Libraries, and Tools used: The back end of StudyNotion uses a range of frameworks, libraries, and tools to ensure its functionality and performance, including:

  1. Node.js: Node.js is used as the primary framework for the back end.
  2. MongoDB: MongoDB is used as the primary database, providing a flexible and scalable data storage solution.
  3. Express.js: Express.js is used as a web application framework, providing a range of features and tools for building web applications.
  4. JWT: JWT (JSON Web Tokens) are used for authentication and authorization, providing a secure and reliable way to manage user credentials.
  5. Bcrypt: Bcrypt is used for password hashing, adding an extra layer of security to user data.
  6. Mongoose: Mongoose is used as an Object Data Modeling (ODM) library, providing a way to interact with MongoDB using JavaScript

Data Models and Database Schema:

The back end of StudyNotion uses a range of data models and database schemas to manage data, including:

  1. Student schema: Includes fields such as name, email, password, and course details for each student.
  2. Instructor schema: Includes fields such as name, email, password, and course details for each instructor.
  3. Course schema: Includes fields such as course name, description, instructor details, and media content.

Overall, the back-end of StudyNotion is designed to provide a robust and scalable solution for an ed-tech platform, with a focus on security, reliability, and ease of use. By using the right frameworks, libraries, and tools, we can ensure that the platform functions smoothly and provides an optimal user experience for all its users.

Database Schema

The REST API design for the StudyNotion ed-tech platform is a crucial part of the project. The API endpoints and their functionalities are designed to ensure seamless communication between the front-end and back-end of the application. By following RESTful principles, the API will be scalable, maintainable, and reliable. The sample API requests and responses provided above illustrate how each endpoint will function and what kind of data it will accept or return. With this API design, StudyNotion will be able to provide a smooth user experience while ensuring security and stability.

Run Locally

  git clone https://github.com/amitamrutiya2210/Study-Notion
  cd Study-Notion
  npm install
  cd backend
  npm install
  cp .env .sample.env and setup environment variable
  cd ..
  cd frontend
  npm install
  cp .env .sample.env and setup environment variable
  cd ..
  npm run dev

Using docker-copose

  Setup env variable in both frontend and backend directory
  Run: docker-compose up

Sample Accounts

Student

Admin