tidal-platform

byNetworking Surya Digital

Subject: Full-Stack E-Learning Platform (LMS) with Advanced Backend Logic Prompt: "Build a comprehensive full-stack E-learning platform similar to Udemy. The application must be robust, scalable, and handle complex backend logic. 1. Core Tech Stack Frontend: React with Tailwind CSS and Lucide React for icons. Backend: Node.js with Express. Database: PostgreSQL (managed via Replit's internal DB or Sequelize). Authentication: Full JWT-based auth or Clerk, featuring two distinct roles: Instructor and Student. 2. Advanced Backend Logic & Features Course Management: Instructors can create courses with multiple sections and video lessons. Implement a progress tracking system where a student's progress (percentage) is calculated on the backend based on completed lessons. Search & Filter: Implement a server-side search engine for courses with categories, price range, and rating filters. Video Handling: Support for video URL embedding or integration with a storage provider (like Cloudinary or AWS S3) for direct uploads. Dashboard: Student: View enrolled courses, progress bars, and 'continue watching' logic. Instructor: Sales analytics, student enrollment count, and course management. 3. Payment Gateway Integration Integrate Stripe or Midtrans (Sandbox mode) for payments. Workflow: When a student clicks 'Buy', create a Checkout Session. Use Webhooks to listen for successful payment events. Only after a successful webhook response should the course be added to the 'Student Enrolled' table in the database. 4. Database Schema Requirements Create a relational schema including: Users (Roles: Admin, Instructor, Student) Courses (Title, Description, Price, InstructorID, Thumbnail) Lessons (CourseID, Section, Content/VideoURL, Order) Enrollments (UserID, CourseID, PaymentStatus) Progress (UserID, LessonID, CompletedAt) 5. Design & UI/UX Professional, clean, and modern UI. Fully responsive for mobile and desktop. Use a 'Dark/Light mode' toggle. Instructions for Execution: Start by setting up the database schema and the Express server. Then, build the authentication flow before moving to course creation logic. Ensure all sensitive information is handled via .env files."

LandingPlayerLogin
Landing

Comments (0)

No comments yet. Be the first!

System Requirements

System Requirement Document
Page 1 of 4

tidal-platform System Requirements Document

Introduction

The tidal-platform is a comprehensive full-stack E-learning platform designed to deliver a premium user experience with robust backend logic. This document outlines the system requirements, including functional and non-functional specifications, user personas, visual branding, and technical architecture.

System Overview

The tidal-platform aims to provide an engaging and secure learning environment similar to Udemy, with advanced features for course management, student progress tracking, and instructor analytics. The platform will initially use YouTube for video hosting, with a modular architecture to allow future integration with AWS S3 or Cloudinary.

Functional Requirements

  • As an Instructor, I should be able to create courses with multiple sections and video lessons.
  • As an Instructor, I should be able to view sales analytics and student engagement metrics.
  • As an Instructor, I should be able to manage student enrollments and course content.
  • As a Student, I should be able to enroll in courses, track my progress, and continue watching lessons.
  • As a Student, I should be able to search and filter courses by category and price.
  • As a System, I should handle payment processing and enrollment through Stripe or Midtrans.
  • As a System, I should generate signed URLs for secure video content delivery.
  • As a System, I should log heartbeat analytics every 30 seconds during video playback.
  • As a System, I should manage active sessions to prevent account sharing.
Page 2 of 4

User Personas

  • Instructor: Creates and manages courses, views analytics, and interacts with students.
  • Student: Enrolls in courses, tracks progress, and engages with course content.
  • Admin: Manages platform settings, user roles, and oversees system operations.

Visuals Colors and Theme

  • primary: #1A73E8 (Deep Blue)
  • primary_light: #E8F0FE
  • secondary: #FF6F61 (Coral)
  • accent: #FFD700 (Gold)
  • highlight: #FFA500 (Orange)
  • bg: #FFFFFF (Clean White)
  • surface: rgba(240, 240, 240, 0.8)
  • text: #333333 (Dark Grey)
  • text_muted: #777777
  • border: rgba(200, 200, 200, 0.5)

Signature Design Concept

The tidal-platform will feature an interactive landing page with a parallax effect in the Hero Section. This will create a dynamic and engaging first impression. Additionally, the course preview section will utilize an image carousel with framer-motion, allowing users to hover over course thumbnails for a smooth transition or quick view overlay. The dashboard will maintain a static interaction model for clarity and speed.

Page 3 of 4

Interaction Model & Motion Direction

  • Landing Page: Parallax interaction model with layered depth via scroll.
  • Dashboard: Static interaction model for clarity and speed.
  • Course Preview: Animated transitions using framer-motion for hover effects.

Non-Functional Requirements

  • The platform must be scalable to handle a growing number of users and courses.
  • The system should ensure data security and privacy, especially for video content and user information.
  • The UI should be responsive and accessible across devices.

Tech Stack

  • Frontend: React, Tailwind CSS, Framer Motion
  • Backend: Node.js, Express
  • Database: PostgreSQL
  • Video Hosting: YouTube (Unlisted videos)
  • Payment Gateway: Stripe or Midtrans
  • Authentication: JWT-based auth

Assumptions and Constraints

  • The platform will initially use YouTube for video hosting, with plans to switch to AWS S3 or Cloudinary in the future.
  • The system will handle payment processing and enrollment through Stripe or Midtrans.
  • The architecture will remain modular to accommodate future changes in video hosting services.
Page 4 of 4

Glossary

  • JWT: JSON Web Token, a compact, URL-safe means of representing claims to be transferred between two parties.
  • MVP: Minimum Viable Product, the most pared-down version of a product that can still be released.
  • Parallax: An effect where the background content moves at a different speed than the foreground content while scrolling.
  • Signed URL: A URL that provides limited access to a resource for a specific period of time.
Landing design preview
Landing: View Info
Login: Sign In
AdminDashboard: View Overview
Users: Manage Roles
Users: Edit User
Courses: Oversee Courses
Courses: Moderate Content
Payments: View Transactions
Payments: Handle Refunds
Sessions: Monitor Sessions
Sessions: Revoke Access
Settings: Configure Platform