Course Preview

Laravel Fundamentals

Laravel is a PHP framework for building server-side web applications and APIs. It bundles routing, an object-relational mapper called Eloquent, the Blade template engine, validation, authentication, queues, and a command-line tool called Artisan into one coherent system, so a team follows shared conventions instead of assembling a separate library for every common task.

itWeb development | OpenSkills.info

Course pathWalk it in order

Look it upDip in anytime

Go furtherLeaves this page

Don't Panic: Laravel Fundamentals

Laravel is a PHP framework for web applications and APIs where the server owns the data and the business rules. It exists because building routing, database access, templating, validation, login, permissions, and background jobs from separate parts leaves every project with its own set of seams to trip over. Laravel picks one set of conventions so a team, and the next person who reads the code, only has to learn them once. Before it, the PHP world mostly did assemble those parts by hand, or used CodeIgniter, which Laravel was written to improve on.

The first thing worth holding onto is a single request. Every web request enters at one file, public/index.php, which builds the application. That application is also the service container, the object that constructs your classes and hands each one the things its constructor asks for. The request then passes through middleware, which can inspect or reject it, reaches a route that points at a controller, and the controller does the work and returns HTML, JSON, or a redirect. Trace that trip once and a lot of Laravel stops looking like sleight of hand.

The second idea is Eloquent, the part that talks to the database. One model class both describes a table and reads and writes its rows. This is pleasant right up to the moment it isn't: writing $post->author inside a loop looks like reading a property and is actually a database query each time, so a page that is fine on ten test rows fires hundreds of queries in production. The cure is to load the relationship up front, and the framework can be told to throw an error in development when you forget.

The third idea is that the conveniences do not remove responsibility. Validation has to happen on the server even though the browser also checked. A logged-in user still needs a policy check before touching a specific record, because authentication only says who they are, not what they may do. And a queue worker, the process that runs deferred jobs, keeps the whole application in memory between jobs, so it leaks memory if left alone and ignores your new code until you restart it.

The surprise, if there is one, is that "batteries included" is a trade. The happy path is fast because nothing forces you to name what a class depends on, and that same freedom is what makes a large, old Laravel codebase hard to follow. Teams that stayed sane moved logic into small, explicit classes before it hurt.

Start with the Intro for the whole map. Slides give you the relationships between the parts, the Cheatsheet has the commands and the decision rules, and Practice is a compact project loop. The Exercise walks one article from route to form request to model to redirect to test. Field Notes carries the judgment that the reference pages leave out, and the Reference tab is your route into the official documentation once the shape is clear.

Where this skill leads

Relevant careers

See how this topic contributes to broader role-level skill maps.

Sources