How rupesh6786/info-point works
Project type and purpose
• This is a static, client-side web application (multiple HTML/CSS/JS pages) that consumes a Backend-as-a-Service (Firebase Realtime Database) and is hosted on Netlify.
• Purpose: Provide a responsive syllabus viewer and student resume portal for BSc.IT 3rd-year students, with registration, dynamic profile cards, and a searchable sidebar.
File structure
• Top-level files:
• HTML pages (index.html, syllabus.html, register.html, search.html, plus language-specific pages and numbered HTML files).
• CSS files corresponding to each page or component (style.css, about.css, search-bar-style.css, register-style.css, syllabus.css, etc.).
• README.md and an image directory.
• No “backend” or “api” folder—JavaScript in the HTML pages directly interacts with Firebase.
• Netlify deployment is inferred by the live-demo URL; no custom build scripts or server code.
README
• Stack: HTML5, CSS3, JavaScript on the frontend; Firebase Realtime Database as the data layer; Netlify for hosting.
• Features call out real-time registration, dynamic cards, and a searchable sidebar.
• No self-hosted backend, authentication is presumably anonymous or via Firebase’s REST/SDK.
Main components
a. User’s Browser (Client)
b. Static Hosting/CDN (Netlify)
c. Application Assets (HTML, CSS, JS)
d. Firebase Realtime Database (BaaS)
e. Optional: External services (e.g., Firebase Auth if used, Analytics)
Relationships and data flow
• On page load, Browser fetches HTML/CSS/JS from Netlify.
• JS on the client initiates Firebase SDK or REST calls:
• Read syllabus (static pages)
• Write new student records on registration
• Read student profiles to generate dynamic cards
• Query for resumes in the sidebar
• Firebase Realtime Database responds with JSON data, which the client renders live.
Architectural patterns and design principles
• Client-Side Rendering (CSR) with BaaS
• Single Responsibility: each page has its own CSS file and dedicated JS logic
• Separation of Concerns: static content vs. dynamic data layer
• Responsiveness: mobile-first CSS, fluid layouts
Technologies and libraries
• HTML5 pages for UI
• CSS3 (separate stylesheets per component/page)
• Vanilla JavaScript or Firebase SDK for data operations
• Firebase Realtime Database as the single data source
• Netlify CDN for high-availability static asset delivery