Learn Laravel from your first route to production architecture
A practical learning map for junior, mid level, and senior developers.
Start the roadmap · Every topic · Explore packages · Learn DevOps · Build projects
| Guide | What you will learn | Best time to open it |
|---|---|---|
| 📍 Complete roadmap | PHP foundations, every major Laravel 13 documentation area, architecture, testing, and scale | Start here |
| ✅ Every documentation topic | A one-page checklist matching the Laravel 13 documentation index | Check coverage |
| 📦 Package atlas | Every package in Laravel's documentation, what it solves, and what to study inside it | When you need a feature |
| 🚢 DevOps & servers | Linux, web servers, deployments, queues, scheduler, CI/CD, backups, monitoring, and recovery | Before going live |
| 🛠️ Practice projects | Projects from task list to production SaaS, with completion checks | After each stage |
| 📖 Plain English glossary | Simple explanations of unfamiliar terms | Any time |
Version: this guide follows the Laravel 13.x documentation, checked in September 2026. Use the documentation version that matches the app you work on.
flowchart LR
A[🌱 Foundations<br/>PHP · HTTP · SQL · Git] --> B[🛠️ Junior<br/>Routes · Forms · Eloquent · Auth]
B --> C[🚀 Mid level<br/>APIs · Queues · Tests · Packages]
C --> D[🛡️ Production<br/>Servers · Deploy · Monitor]
D --> E[🧠 Senior<br/>Architecture · Scale · Leadership]
| Stage | Focus | Build | You are ready to continue when… |
|---|---|---|---|
| 01 · Foundations | PHP, Composer, web, SQL | Small PHP form | You can explain a request and a database query |
| 02 · Laravel basics | Routes, controllers, Blade, validation | Task list | You can make CRUD without copying a tutorial |
| 03 · Real apps | Eloquent, auth, policies, APIs | Multi user blog | Users cannot access each other's private data |
| 04 · Team systems | Queues, events, cache, tests | Issue tracker | You can test and debug slow or failing work |
| 05 · Production | Linux, Nginx, CI/CD, backups | Deployed app | You can deploy, monitor, and recover it |
| 06 · Senior | Design decisions, scaling, mentorship | SaaS system | You can explain tradeoffs and guide others |
Use the same five steps for every topic or package:
- Understand — say what problem it solves in one sentence.
- Build — make the smallest working example.
- Break it — try invalid input, permission failures, and service outages.
- Test it — prove the happy path and an important failure path.
- Explain it — write when you would use it and when you would choose something simpler.
For example, while learning queues: send one email through a job, stop the worker, see the job wait, restart the worker, then test a failed job and retry it.
I am brand new: read Foundations → First Laravel app → build the task list.
I already write Laravel: check the full topic checklist, pick a gap, and use the package atlas only when that feature needs a package.
I need to launch an app: use DevOps & servers, including the manual deployment walkthrough.
I want senior depth: focus on production, senior engineering, and the operations labs.
- You can build a feature and explain each request, query, and side effect.
- You can choose a package because you understand the problem it solves.
- You can test security rules and important failure cases.
- You can deploy, observe, back up, and restore a real application.
- You can make tradeoffs visible to your team and help newer developers grow.
No one needs to memorize every Laravel method or install every package. Use this map to make sure you know the areas that exist, then go deep where your project needs it.
Start with one feature. Finish it. Explain it. Then build the next one.
Open the complete roadmap →