How ceres2808/ec-iot-website works
Project type and purpose
• This is a Next.js-based static or server-side rendered website (“ec-iot-website”) built in the new App Router paradigm (app/ directory), using React components for each page and shared UI pieces. Its purpose is to present information about the Ec-IoT group: pages for home, about, achievements, events, members, projects, contact, etc.
File structure
• Top-level directories/files:
• app/ — Next.js App Router folder containing your page routes (app/pages/*.jsx), shared components (app/components/*.jsx), global stylesheet, and layout/page root files.
• public/ — static assets (video.mp4, desktop.ini placeholder).
• jsconfig.json, next.config.mjs, postcss.config.mjs — configure path aliases, Next.js behavior, PostCSS.
• package.json / package-lock.json — Node dependencies (React, Next.js, etc.).
• Patterns & architecture:
• File-system routing via app/pages.
• Component-based design under app/components (Navbar, Footer, FaceCard, Members).
• Global CSS in app/globals.css.
• Build / deploy pipeline implied (Next.js build → static HTML & JS bundles).
README
• Minimal; confirms “Ec-IoT Website.” No additional architectural details.
Detailed breakdown to capture all elements
• At the top, show “Git Repository (GitHub)” → CI/CD pipeline → “Next.js Build” → “Deployment to CDN.”
• In the Next.js Build block, show sub-blocks:
• app/layout.js (root layout)
• app/page.js (homepage)
• app/pages/*.jsx (other pages)
• app/components/*.jsx (shared UI)
• app/globals.css & postcss.config.mjs
• Then to “User Browser” which fetches assets and hydrates via React.