How webdev4001/slc works
Project Type and Purpose
• This is a static, responsive frontend website (“SLC Website”) built to serve as a central hub for students at MMMUT.
• It contains only client-side code: HTML5 pages, Tailwind CSS styles, and vanilla JavaScript for interactivity (forms, filtering, accordion UI, chatbot stub).
• There is no backend yet, but the README calls out future integration points: API server, database storage, real‐world chatbot service.
File Structure
• Public/
• HTML files (index.html, library.html, engage.html, council.html, path.html) – each page of the site
• css/style.css – compiled Tailwind output
• js/*.js – page-specific and shared scripts (main.js, forms.js, chatbot.js, etc.)
• src/input.css – Tailwind directives input file
• tailwind.config.js / postcss.config.js – build tooling
• package.json – dev dependencies for Tailwind, PostCSS
README Insights
• Emphasis on:
• Responsive design, utility-first CSS via Tailwind
• Client-side dynamic filtering (library, events) and forms (book suggestions, join SLC, feedback)
• Placeholder PATH chatbot requiring a backend integration
• Future enhancements:
• Database layer for form data
• API server (Node/Express, Flask, etc.)
• Real AI chatbot service
• User authentication and admin UI
a. Main Components
• User’s Browser (Client): Renders HTML + CSS, runs JavaScript
• Static Asset Host: CDN or static-site host serving Public/ files
• External Services: Google Fonts, potential Chatbot API (Dialogflow/LLM), Analytics (if any)
• (Future) API Server: Node.js/Express or equivalent, exposes REST endpoints for form submissions, library/event data, chatbot proxy
• (Future) Database: MongoDB/PostgreSQL/Firebase to persist suggestions, applications, feedback, dynamic content
b. Relationships and Interactions
1. Browser → Static Host: HTTP GET for HTML/CSS/JS/images
2. JS in Browser → (Future) API Server: POST/GET for forms and dynamic data
3. API Server ↔ Database: CRUD operations on stored data
4. Browser → External Chatbot Service: JSON requests/responses via chatbot.js
5. Browser → Google Fonts: font files loaded on page render
c. Architectural Patterns & Design Principles
• Client-Side Rendering – static pages + JS enhancements
• Utility-First CSS – Tailwind for consistent styling and responsive breakpoints
• Progressive Enhancement – page always loads HTML/CSS; JS augments features
• Separation of Concerns – HTML markup, styling in CSS, behavior in JS, build config in separate files
d. Key Technologies, Frameworks, Libraries
• HTML5, Tailwind CSS, PostCSS, Autoprefixer
• Vanilla JavaScript modules (ES6)
• Node.js toolchain for CSS build (npm, tailwindcss CLI)
• (Planned) Express.js or Flask API, MongoDB/PostgreSQL, Dialogflow/OpenAI API