> ## Documentation Index
> Fetch the complete documentation index at: https://kawax.biz/llms.txt
> Use this file to discover all available pages before exploring further.

# Knowledge required before starting Laravel

> This page outlines the four areas you should master before diving into Laravel and guides you through the prerequisite knowledge.

The official Laravel documentation is material for learning Laravel itself.\
This page briefly summarizes "which areas to master before reading the Laravel documentation."

<Info>
  This page is not a detailed explanation. If you find an area you are missing, learn it first, then return to your Laravel studies when you're ready.
</Info>

## PHP fundamentals

If you're going to use Laravel, PHP fundamentals are a prerequisite. If you only rely on the old procedural style, you will easily get stuck understanding the service container and Eloquent.\
It's especially important to keep up with PHP version upgrade information continuously. Laravel actively drops support for older PHP versions.\
In real-world work, you need to be comfortable reading PHP 8.x features such as named arguments, match expressions, Attributes, and Fibers. Laravel 13 requires PHP 8.3 or higher. Veterans even check PHP RFCs.

## Frontend knowledge

In modern web development, frontend knowledge is essential even with Laravel. A setup where "only the API is Laravel and the UI is entirely handled by a separate team" is not mainstream, at least in the standard Laravel development picture.\
Your choice between Blade (server-side centric), Livewire (a reactive UI that minimizes JavaScript), or Inertia + React/Vue (an SPA-like experience) will change both design and implementation.\
Furthermore, understanding the progression from jQuery-centric development to SPAs and then to SSR/hybrid approaches makes it easier to understand today's options. You should also learn the basics of npm and Vite first.

## Historical background of PHP frameworks

Bringing conventions from other frameworks directly into Laravel greatly reduces learning efficiency.\
The more experience you have with CodeIgniter or Symfony, the more important it is to adopt a "forget it for now and learn again the Laravel way" attitude.\
While Laravel leverages Symfony components, it designs the development experience with unique philosophies such as facades and Eloquent. Behind its rapid spread after 2011 lies this consistent philosophy and high productivity.

## Infrastructure knowledge

Even with convenient platforms like Laravel Cloud, foundational infrastructure knowledge is still necessary.\
If you know enough to build a setup manually on a VPS or AWS EC2, you can isolate problems much faster when trouble hits.\
Nginx/Apache, PHP-FPM, basic MySQL or PostgreSQL configuration, environment variables and `.env` management, and Docker fundamentals are unavoidable. Even when using Laravel Sail, operations become more stable the better you understand what's running under the hood.

<Tip>
  Reinforce whichever of the four areas you feel least confident about first. The more prerequisite knowledge you have, the more deeply you can understand the official Laravel documentation in a short time.
</Tip>


## Related topics

- [Migration Guide: Old Structure to Slim Application Skeleton](/en/advanced/app-structure-migration.md)
- [Upgrading from Laravel 8 to 9](/en/blog/upgrade-8-to-9.md)
- [Laravel Cloud — a full look at the Laravel-native PaaS](/en/blog/laravel-cloud.md)
- [Laravel Scout](/en/scout.md)
- [Package Static Analysis (PHPStan / Larastan)](/en/advanced/package-static-analysis.md)