How strapi/foodadvisor works
Main Components
A. Frontend Layer (Next.js):
• Client-side application (/client)
• Pages structure (Dynamic routes, Blog, Restaurants)
• Components hierarchy (Blocks, Global, Shared)
• Static assets and public files
B. Backend Layer (Strapi):
• API endpoints
• Content Types (Article, Restaurant, Review, etc.)
• Admin panel
• Authentication system
• Media Library
• Database connection
[Client Layer]
• Next.js Frontend
• Pages Router
• Components
• API Routes (Preview/Exit Preview)
• ↕ REST/GraphQL API Calls
[Backend Layer]
• Strapi API
• Content Types
• Controllers
• Services
• Routes
• Strapi Admin Panel
• User Management
• Content Management
• Media Library
• Database
Key Relationships to Highlight
a. Content Flow:
• How content types (Articles, Restaurants, Reviews) flow from Strapi to Next.js
• Preview functionality between frontend and backend
• Demonstrate media asset handling
b. Authentication Flow:
• User roles (Super Admin, Editor, Author)
• Authentication boundaries
• Permission checks
Component Details
Frontend:
• Page structure (/pages)
• Reusable components
• Routing system
Backend:
• Content type structure
• API endpoints
• Admin customizations
Additional Elements
• Notes for important configurations
• Environment variable dependencies
• Scaling points