How moraesc/ai-art-gallery works
Project type and purpose
• This is a static “content-driven” website built with Next.js (v13, App Router) and Tailwind CSS.
• Its sole purpose is to showcase AI-generated art in a homepage, gallery, and about pages, serving static assets (images, CSS) and React-rendered pages.
File structure
• Top-level configs:
• tsconfig.json – TypeScript setup
• next.config.js – Next.js build/runtime options
• tailwind.config.js & postcss.config.js – Tailwind CSS processing
• .eslintrc.json & .prettierrc.json – linting/formatting rules
• app/ directory (Next 13 “App Router”):
• layout.tsx – global layout wrapper
• globals.css – global styles (imported into layout)
• page.tsx, Header.tsx, Homepage.tsx – top-level React components
• about/, gallery/ subfolders – nested pages under /about and /gallery
• constants.ts – shared values (e.g., image directories or meta)
• public/static/images – stored AI art images served as static assets
README for additional insights
• No dynamic backend or API calls—purely static art collection.
• Hosting likely on Vercel, Netlify, or any static-serving CDN.
Elements
• Build-time flows (from code → build pipeline → output)
• Runtime flows (browser requests → Next.js/edge → returns HTML/CSS/JS → browser renders → fetches images)
• Blue for code components (React, TSX files)
• Green for build tools (Node.js, Tailwind)
• Yellow for static asset store (public/static)
• Orange for runtime environment (CDN/hosting)