How sitcon-tw/2025 works
Project type and purpose
• This is a Next.js 13 “App Router” web application that serves as the conference website (SITCON-2025).
• It is primarily a front-end application with SSR/SSG pages, dynamic routes (e.g., agenda/[id], cfp/(submission)), static JSON data (staff.json, sponsors.json) and ICS calendar files in /public.
File structure
• Top-level directories:
• app/ – Next.js App Router source: nested folders map directly to pages and layouts.
• public/ – static assets (images, PDFs, ICS files, JSON content).
• hooks/ & lib/ – reusable React hooks and utility functions.
• Configuration: next.config.mjs, tailwind.config.ts, ESLint, Prettier, Husky, GitHub Actions workflows.
README insights
• Confirms Next.js framework, suggests deployment on Vercel.
• No external database or API: site uses static files and server-rendered React components.
Core components
a. Developer & Code Repo
• GitHub repository with branches
• Husky pre-commit (lint/staged checks)
• GitHub Actions (CI pipelines: deploy.yaml, vercel.yaml)
b. CI/CD & Hosting
• GitHub Actions → Vercel deployment
• Vercel Edge Network + Serverless Functions (SSR/SSG)
• CDN for static assets under public/
c. Next.js Application
• App Router Entry (app/layout.tsx, app/page.tsx)
• Nested layouts & pages under app/(website) and app/cfp
• Reusable UI (app/_components, app/(website)/_components)
• Dynamic route handlers (agenda/[id]/page.tsx, cfp/(submission)/…)
d. Data & Assets
• Static JSON (e.g., /public/sponsor/sponsors.json, /public/staff/staff.json)
• ICS calendar files (.ics under /public)
• Poster PDFs, images, logos served from /public
e. Tooling & Config
• ESLint, Prettier for code quality
• Tailwind CSS for styling
• TypeScript configuration
Relationships & data flow
• Developer → pushes code → GitHub
• GitHub Actions CI → runs tests/lint → on success triggers Vercel deploy
• Vercel builds Next.js → produces SSR endpoints + static assets → deploys to Edge CDN
• Browser requests a URL → served by Vercel Edge CDN (static or SSR) → Next.js SSR may read JSON from /public
• React renders component tree (layout → page → nested components) and returns HTML/CSS/JS to client
Architectural patterns & principles
• File-system routing (Next.js App Router)
• Hybrid SSG/SSR:
• SSG for truly static content (staff, sponsors, venue pages)
• SSR or dynamic rendering for pages with parameters ([id])
• Component reuse: central _components and hooks
• CI/CD best practices: automated linting, formatting, test gate, zero-downtime deploys on Vercel
Final recommendations
• Be detailed: break out CI steps, hosting, build output, and runtime.
• Separation of concerns: routing layer vs. component layer vs. data layer vs. infrastructure.
• Keep it focused: although no traditional backend service exists, highlight the SSR/SSG functions on Vercel as your “runtime.”