Frontend knowledge for Laravel developers (optional)
Status: Outline. This is selective interview context, not a frontend fundamentals course.
| Approach | Strength | Cost |
|---|---|---|
| Blade | Smallest state and deployment surface | More manual interaction for rich UI |
| Livewire | Rich server-driven UI with Laravel mental model | Network-sensitive lifecycle and server component state |
| Inertia | SPA-like UI while retaining Laravel controllers/routes | Client build/state complexity; coupled deployment |
| Separate API + SPA | Independent clients/releases and explicit contract | Auth, CORS, versioning and duplicated boundary work |
To cover
Section titled “To cover”- Blade components, forms, escaped output, and validation errors
- Livewire lifecycle, hydration, authorization, and stale component state
- Inertia request/response model and shared data
- Vite and browser/module boundaries
- Event loop, tasks, microtasks, promises, cancellation, and stale responses
- Browser storage, semantic HTML, and accessibility