How moajmalp/g7-website works
Project type & purpose (from file tree + README)
This is a Next.js (App Router) web application bootstrapped with create-next-app. The structure indicates a content-driven site with:
• A blog section: app/blog/page.tsx and dynamic route app/blog/[slug]/page.tsx
• A static legal/info page: app/risk-disclosure/page.tsx
• Shared layout and UI components: components/layout/*, components/ui/*
• Local “data access” helpers: lib/blog-data.ts (likely reads posts from public/blog/*)
• Styling and motion: Tailwind CSS (tailwind.config.ts, postcss.config.mjs, app/globals.css) and likely Framer Motion (components/providers/framer-provider.tsx, lib/motion.ts)
So the architecture is primarily single deployable Next.js app (no separate backend service visible), with filesystem-backed content (blog assets under public/blog).
Routing / Pages (App Router)
• app/layout.tsx (global layout shell)
• app/page.tsx (home)
• app/blog/page.tsx (blog index)
• app/blog/[slug]/page.tsx (blog detail; slug-based)
• app/risk-disclosure/page.tsx
Shared UI
• Layout components: components/layout/Navbar.tsx, components/layout/Footer.tsx
• UI components: components/ui/custom-dropdown.tsx, components/ui/fade-in.tsx
Providers / Cross-cutting
• components/providers/framer-provider.tsx (global animation/motion context)
Domain / Data access
• lib/blog-data.ts (blog post discovery + parsing; likely reads from filesystem under public/blog)
• lib/motion.ts (motion configuration / variants)
Deployment/Runtime (C4 Level 2-ish)
• Browser ↔ CDN/static ↔ Next.js runtime (Vercel)
• Build pipeline optionally (Git → Vercel Build → Deploy)
• app/* routes → components/* + lib/* + public/*
• layout.tsx composing Navbar/Footer and provider
• Browser → Next.js route → blog-data → public/blog → render → response
These three together will be the most accurate representation of *this* repo’s actual architecture.