How marcaureldev/afircan-basketball-league works
Project type and purpose
• This is a Next.js 13+ full-stack React application (frontend-centric) that uses the App Router (src/app), server-side rendering (SSR) and/or static site generation (SSG).
• The README confirms it was bootstrapped with create-next-app and is intended to render a series of UI components (hero section, gallery, match cards, metrics, etc.) with theme toggling.
File structure
• Top-level files:
• next.config.ts, postcss.config.mjs, eslint.config.mjs → build & tooling configuration
• pnpm-lock.yaml, package.json → dependencies & scripts
• public/assets → static images served directly
• src/app → Next.js App Router:
• layout.tsx (site shell, global providers)
• page.tsx (home page entry point)
• globals.css (global styles)
• src/components → React components, two layers:
• src/components/ui → “atomic” UI primitives (Badge, Card, Button)
• src/components → composite/presentational components (Header, HeroSection, ImageGallery, MatchCard, Metrics, etc.)
• src/contexts → shared React contexts (ThemeContext)
• src/lib → data and utility functions (data.ts, utils.ts)
README for additional insights
• No custom API routes or external services called out.
• Optimization via next/font, deployment recommendation is Vercel.