How aymanelh/lakarte works
Project Type and Purpose
• This is a full-stack web application comprising:
• A Laravel-powered backend (REST API + Filament admin panel)
• A React SPA public frontend
• A MySQL (or compatible) database plus cache/session stores
• Purpose: manage and display “packs,” “pack offers,” blogs, testimonials and orders, with a secure admin interface (Filament) and a public-facing marketing/payment flow.
Main Components
a. Public Frontend (React SPA)
• Directory: react/
• Key files: src/pages/*, src/components/*, src/services/*, vite.config.ts
• Responsibilities: render pages (Home, Blog, Packs, Templates, Testimonials), handle user auth (login/register), call backend API.
b. Backend API (Laravel)
• Entry point: public/index.php, routes/api.php, routes/web.php
• Layers:
• Controllers (app/Http/Controllers/Api/*)
• Request validation (app/Http/Requests/Auth/*)
• Service layer (app/Services/*)
• Eloquent models (app/Models/*)
• Resources/transformers (app/Http/Resources/*)
• Responsibilities: authenticate (Sanctum/Passport), CRUD for packs, orders, blogs, testimonials; business rules, payment validation.
c. Admin Panel (Filament)
• Directory: app/Filament/*, resources/views/filament/*
• Provides CRUD UI for all entities via PHP classes (Resources, Widgets).
d. Data Stores
• Relational database (MySQL/Postgres): tables for users, packs, orders, blogs, testimonials, etc.
• Cache/session driver (Redis/file)
• File storage (local or S3) for uploads.
e. External Services
• Payment gateway (configured in config/services.php)
• Email/SMS providers (mail drivers in config/mail.php)
• Third-party analytics or logging if used.
f. DevOps / Infrastructure
• Docker (Dockerfile, docker-compose.yml)
• CI pipeline (GitHub Actions badge in README)
• Env management (.env.example)
Relationships and Data Flows
• User ⇄ React SPA (HTTPS)
• React SPA → Laravel API (REST calls with JWT/Sanctum tokens)
• API → Database (CRUD via Eloquent)
• API → Cache/Session (for rate-limiting, sessions)
• API → External Payment Service (HTTP webhooks/callbacks)
• Admin User ⇄ Filament UI → Laravel backend (Blade templates, controllers)
• Migrations/Seeders → Database (init / test data)
Architectural Patterns and Design Principles
• MVC on backend + Service Layer for business logic (app/Services)
• Single-Page Application on frontend with Context API for auth and hooks for data fetching
• RESTful API contracts using Laravel Resources
• Filament Admin: code-driven CRUD panels and widgets (component-based pattern)
• 12-factor app principles (env config, stateless processes, separate build & run)