How ctoic/campushive-frontend works
Project type and purpose
• From the file tree and the minimal README title (“Campus Hive”), we see:
• A Vite-powered React application (presence of vite.config.js, src/main.jsx).
• A purely front-end codebase—no backend or server directories.
• UI components for sections like Hero, About, Features, Team, Login/Signup, and a Chatbot.
• Purpose: A single-page campus community site (“Campus Hive”) that likely offers static content pages plus a chatbot feature.
File structure
• Top-level files:
• index.html – host page template.
• package.json / package-lock.json – dependency management.
• .bolt/config.json, eslint.config.js – linting / developer tooling.
• public/ – static assets served as-is.
• src/ – core source code:
• src/main.jsx – React entry point.
• src/App.jsx / App.css – root component and styling.
• src/components/ – individual UI components (Navbar, Footer, Hero, About, Features, Team, Login, Signup, Chatbot).
• src/utils/ScrollObserver.jsx – utility for scroll-based behavior.
• src/assets/ – media files (video, images).
Key insights from the README
• Very brief; implies we must infer architecture from structure.