How pythonnortebrasil/pynorte2025-site works
Project Type and Purpose
• This is a static/SSR‑driven front‑end site built with Next.js (App Router), React and TypeScript.
• It serves localized content (en/pt) and static data (JSON) for an event website.
File Structure
• Top level: configuration files (next.config.ts, tailwind.config.ts, CI workflows under .github, linting/setup under .husky), and the package.json ecosystem.
• src/app: Next.js App Router entrypoints, layouts, pages (including dynamic [locale] routes), global CSS, and manifest.
• src/components: React UI components (page‐specific and a large ui subfolder powered by shadcn‑ui + radix).
• src/data: Static JSON files (calendar, faq, sponsors, etc.) used for SSG.
• src/hooks & src/lib: Client/server hooks and utility functions.
• public: Static assets (favicon, robots.txt, sitemap.xml).
Extract Additional Insights from README
• Fully front‑end, no dedicated backend service—the Next.js server handles SSG and optional SSR.
• Hosted via CDN (likely Vercel or Netlify), with automated CI/CD from GitHub workflows.
Main Components
a. Developer Workstation & VCS
• Local IDE → GitHub Repo
b. CI/CD Pipeline
• GitHub Actions: Linting & Deploy workflows
• Husky & commitlint for pre‑commit hooks
c. Build System
• Node.js + npm → Next.js build (SSG/SSR)
• Tailwind CSS compilation
d. Hosting & CDN
• Static assets served from a CDN
• Next.js server (if SSR is used) or purely static hosting
e. Browser / End‑User
• Fetches pre‑rendered pages, JSON data, and static assets
f. Data Sources
• JSON files in /src/data embedded at build time
g. UI Layer
• React components (page structure, shared ui/ library)
Relationships & Data Flows
• Code push → GitHub → CI → build → deploy to CDN/hosting.
• Browser requests URL → CDN → Next.js server or edge functions → serves HTML/CSS/JS bundles.
• During build, Next.js reads JSON data files → generates static pages per locale.
• Client React hydrates interactive components (hooks, UI library) in the browser.
Architectural Patterns & Design Principles
• App Router (Next.js) for file‑based routing and dynamic [locale] segments.
• Static Site Generation (SSG) for performance and SEO.
• UI Component Library: shadcn‑ui + radix for reusable primitives.
• GitOps / CI‑driven Deployments via GitHub Actions.
• Tailwind CSS utility‑first styling at build time.