How laravel/breeze works
Main Components Structure
┌─ Laravel Breeze Starter Kit ─────────────────────┐
• ┌─ Stack Options ──┐ ┌─ Core Features ───┐ │
• Blade │ │ - Authentication │ │
• Inertia.js │ │ - User Profile │ │
• Vue.js │ │ - Email │ │
• React │ │ Verification │ │
• Livewire │ └───────────────────── │
• API │ │
• ┘ │
• ┘
Implementation Layers
Architectural layers with clear separation:
┌─ Frontend Layer ─────┐
• Views/Components │
• Assets (CSS/JS) │
• Frontend Routing │
• ┬──────────┘
┌──────────▼──────────┐
• Controller Layer │
• Auth Controllers │
• Profile Controller │
• ┬──────────┘
┌──────────▼──────────┐
• Service Layer │
• Auth Services │
• Password Reset │
• ┬──────────┘
┌──────────▼──────────┐
• Database Layer │
• User Model │
• Migrations │
• ┘
Stack-Specific Components
• Blade Stack (Blue)
• Inertia Stack (Green)
• Livewire Stack (Purple)
• API Stack (Orange)
Authentication Flow
User Request → Route → Controller → Authentication → Response
Implementation Details
Relationship between:
• Routes (auth.php, web.php)
• Controllers (Auth controllers)
• Views/Components
• Middleware
• Service Providers
Testing Integration
A section showing:
• Feature Tests
• Unit Tests
• Testing Utilities
• High-level architecture
• Implementation details
• Stack-specific variations
• Authentication flows
• Testing coverage
Use tools like:
• Lucidchart
• PlantUML
Remember to:
• Use consistent styling
• Clear labels
• Relationships between components
• Modular nature of the starter kit
This will provide a comprehensive view of Laravel Breeze's architecture while maintaining clarity and usefulness for the development team.