How yagnik-patel-47/admission-spider-site works
Project type and purpose
• Admission Spider (Frontend) is a static, multi‐page frontend web application built with HTML, CSS, and vanilla JavaScript.
• Its purpose is to present admission opportunities and educational announcements scraped from various college/university websites in India.
Main components
a. Client Browser
• Loads HTML pages (index.html, details.html, announcements.html, feedback.html)
• Applies CSS (from css-files/*.css) for layout and styling
• Runs JavaScript (from js-files/*.js) to implement UI logic, search/filter, and dynamic rendering of data
b. Web Server (Static Asset Host)
• Serves the HTML, CSS, and JS assets over HTTP/HTTPS
• Could be a simple web server (e.g., Nginx, Apache, GitHub Pages) or CDN
c. Admission Data API (External Service)
• Could be a RESTful service that the JS code fetches at runtime
d. External Data Sources (Colleges/Universities Websites)
• The actual content is scraped from these sites by a separate backend/scraper service before being exposed via the Admission Data API
Relationships and interactions
• [Browser] → HTTP GET → [Web Server] to fetch HTML/CSS/JS
• [Browser-JS] → AJAX/Fetch → [Admission Data API] to retrieve admissions and announcements data (JSON)
• [Admission Data API] → Scrapes or queries → [External Data Sources] (periodic or on-demand)
• [Browser] ← Renders ← Dynamic data returned from the API
Architectural patterns and design principles
• Separation of concerns
• Presentation layer: HTML + CSS
• Client logic layer: JavaScript controllers handling events, fetching data, and updating the DOM
• Data layer: External Admission Data API exposing a clean JSON interface
• Progressive enhancement and responsive design (per README’s mobile/desktop support)
• Static asset pipeline: keeps frontend deployment simple and scalable (can host on any static file server or CDN)
Technologies and frameworks to annotate
• HTML5 (semantic markup for each page template)
• CSS3 (custom layout, grid/flex utility classes, media queries for responsiveness)
• Vanilla JavaScript (ES6 modules or script files handling UI state, fetch calls, event listeners)
• (Optional) Web server/CDN name, and the Admission Data API technology (e.g., Node.js/Express, Python/Flask)