Symfony for FE devsAfter the PHP tutorial

Notes-style walkthrough of Symfony - for front-end folks who already finished /lab/php-tutorial-for-fe-devs/ (modern PHP, Composer, request lifecycle).

Start reading

Cheatsheet

You already did the hard part

Types, Composer, PDO, sessions, CSRF, a mini-router - that's the floor. Symfony is explicit packaging of those ideas (plus a serious DI container).

Front-end brain welcome

Twig vs JSX/Vue, AssetMapper, routes like a router config, forms like form libraries - I'll keep mapping.

Build mental models, not magic

When docs say "Doctrine" or "firewall", you'll know what sits underneath - so leaks don't panic you.

Who this is for

You've shipped front-end apps. You've gone through the PHP tutorial for FE devs (or equivalent): strict types, PSR-4, HTTP lifecycle, forms, PDO, security basics.

Now you want Symfony to feel like a tool - not a wall of YAML.

There's also a Laravel twin if that's your shop's default. Same PHP runway, different nouns. Neither is a prerequisite for the other.

How to follow along

Have PHP 8.3+, Composer, and (optionally) the Symfony CLI ready (Setup)
Create a throwaway Symfony app and keep it open while reading
Chapters build in order - later ones assume the earlier maps
Keep the cheatsheet nearby once you're past routing

bash

npm install
npm run docs:dev

What's intentionally light

Deep API Platform / EasyAdmin / Messenger topology rabbit holes (pointed at in What next)
Deploy / Platform.sh / FrankenPHP ops deep dives
"Rewrite your SPA in Symfony" evangelism

We're here so you can open a Symfony codebase, find the route, follow the controller, touch the entity, and not feel lost.

Wish you all the best - hope you're gonna enjoy this one too.

Best,

-- ł.