How farhan9684/eduskill-knowledge-hub-brain-booster works
Project Type and Purpose
• This is a full-stack, monolithic web application built on Django (MTV pattern)
• Purpose: an educational platform (“Edu-Skill”) providing course content, quizzes, video tutorials, and doubt resolution
File Structure
• Top-level Django project (“main”) contains settings, URL routing, ASGI/WSGI entry points
• Four Django apps under the project root:
– app1: core features (models, views, admin)
– reviews: interactive quizzes & feedback submission
– service: doubt resolution/contact form
– main: authentication, site pages, routing
• Static folder: CSS, JS, images, sample papers
• Templates folder: HTML templates used by each app
• SQLite database file (db.sqlite3)
README for Additional Insights
• Features: courses, quizzes, video tutorials, doubt submission
• Fully responsive design for desktop/tablet/mobile
• Implies server‐side rendering + static assets
Main Components & Responsibilities
a. Client (Browser/Mobile App)
– Requests HTML pages, submits forms (quizzes, reviews, doubts)
– Fetches static assets (CSS, JS, images)
b. Load Balancer / Web Server
c. Django Application Server (Gunicorn / Uvicorn)
– ASGI/WGSI entry point (main/asgi.py or wsgi.py)
– URL router (main/urls.py) dispatches to app1, reviews, service, main views
– Views execute business logic, render templates, or serialize JSON
d. Django MTV Layers
– Models (app1/models.py, reviews/models.py, service/models.py) → ORM
– Templates (templates/*.html) → presentation
– Forms (main/forms.py, reviews/forms.py) → user input validation
e. Database
– SQLite (db.sqlite3)
– Django ORM issues SQL and retrieves/stores data
f. Static Asset Server
– Serves files from static/ directory
Relationships & Data Flows
• Browser → (HTTP) → Load Balancer/Web Server → Django ASGI/WSGI
• In Django:
1. URL Router → appropriate App’s View
2. View ↔ Model (ORM) → Database
3. View → Template Engine → HTML
4. HTML + Static Assets → Browser
• For form submissions (quizzes, reviews, doubts): Browser → POST → View → save to DB → redirect/response
Architectural Patterns
• Django’s MVC (MTV) pattern
• Modular apps for separation of concerns (courses, reviews, services)
• Monolithic deployment (all apps in a single codebase + single DB)
Technologies & Frameworks to Call Out
• Python 3.x, Django framework
• SQLite (development DB)
• HTML5/CSS3/JavaScript for front end
• Django templating engine
• (Optional) Nginx/Gunicorn or Uvicorn for ASGI