How jozieliosantiago/anime-library works
Project type and purpose
• This is a frontend-focused full-stack (Next.js) React/TypeScript web application called “Anime Library.”
• Purpose: Display a catalog of anime titles on a home page and detailed views per anime (synopsis, categories, trailer, episode list). It fetches data at runtime (SSR/CSR) from the external Kitsu API.
File structure
• Top-level config and meta:
• next.config.js, tsconfig.json, .eslintrc.json, package.json
• README.md, .gitignore, .github folder (CI, LICENSE)
• Public assets:
• Source code under src/:
• pages/ — Next.js file-based routes (_app.tsx, index.tsx, anime/[id].tsx)
• components/ — UI building blocks (Header, Carousel, MovieCard, AnimeSynopsis, EpisodeDetails, Loading, etc.)
• services/ — API client (kitsuApi.ts)
• styles/ — global.scss and per-page SASS modules
• types.ts and utils/ (helper functions)
README for additional insights
• Architecture: Standard Next.js SSR/CSR, no custom backend.
• Dependencies: ReactJS, TypeScript, NextJS, Ant Design, SASS.
• Deployment targets: Vercel or Heroku.
• Runtime behavior:
• On each page request, Next.js may fetch data via kitsuApi (Axios or fetch)
• Props are hydrated into React components