How roshan9419/learned_e-learning_website works
Main Components
• User Interface (Frontend): Include the core HTML pages such as index.html (the main landing page), login.html, and the subject-specific pages (e.g., computer_courses.html, gate.html, jee.html, quiz.html). These represent what the end user sees.
• Styling & Presentation Layer: Represent the CSS files (style.css, loginStyle.css, subjects/subjects.css, subjects/quizStyle.css) that define the look and feel of the website.
• Client-Side Logic: Identify script.js (and any inline scripts within HTML pages), which handles client-side interactivity such as the quiz functionality and possibly the login interactions.
Relationships and Data Flow
• Client (user’s web browser) making requests that load the static HTML, CSS, and JS files.
• Point out how the pages pull in static assets (images, PDFs, etc.) via URL references.
• Possible interactions such as:
• Navigation flows between pages (from index.html to subjects pages or login).
• The quiz system’s data flow: loading questions, calculating scores, and displaying results.
• If there is any form or question submission functionality (mentioned in the README), highlight that it might either send data to a backend or simply process data client-side.
Architectural Patterns and Design Principles
• That the project uses a simple static, modular architecture, with a clear separation of concerns:
• Presentation: Handled by HTML and CSS.
• Behavior: Managed by client-side JavaScript.
• Content/Assets: Organized in dedicated directories for images and PDFs.
• Responsiveness of the design, which means CSS media queries or similar techniques are used to adapt the layout for various devices.
Relevant Technologies and Tools
• HTML5, CSS3, and JavaScript form the core stack.
• GitHub Pages is used to deploy the website.
• Optionally, mark the use of static assets management (even if done manually by organizing the file tree).