So I Tried Laravel

A complete beginner’s walkthrough of building a micro-blogging app in Laravel turns into a practical tour of how the framework’s pieces fit together—starting from installation, then authentication scaffolding, then CRUD for “chirps,” and finally notifications and deployment options. The core takeaway is that Laravel’s “convention over configuration” approach lets a developer go from a blank project to a working, database-backed web app with minimal custom glue, while still exposing the underlying concepts: models, migrations, controllers, routing, middleware, validation, authorization, and events.

The build begins with setting up a local PHP and Composer environment, creating a new Laravel project named “chirper,” and running the built-in development server. The app uses SQLite by default, and the workflow quickly expands into front-end tooling: Breeze for authentication scaffolding, Tailwind for styling, and Vite for compiling assets. Once the login/register UI appears, the tutorial shifts to the app’s main feature: letting authenticated users post short messages (“chirps”). That requires creating a model, migration, and resource controller, then wiring routes using a resource controller with middleware that enforces both authentication and email verification.

From there, the walkthrough drills into Laravel’s data layer and request lifecycle. Eloquent ORM is introduced as the mechanism that maps database tables to models and enables create/update/delete operations. Migrations are used to define the schema, including adding a foreign key from chirps to users. Validation is added to the store action to enforce required message content and a maximum length (255 characters). After that, the index action evolves from a placeholder to a real feed: it eager-loads the author relationship so each chirp can display its creator’s name, and it uses a “latest” query scope to order results by recency.

Editing and deleting chirps add another layer: Breeze’s UI components provide dropdown actions, while Laravel’s resource routing and controller methods handle the HTTP verbs (GET for edit pages, PATCH/PUT for updates, DELETE for removals). Authorization is enforced with policies—first for updates, then for deletes—so only the chirp’s author can modify it. The tutorial also highlights how Blade templates connect controller data to HTML, including loops over chirps and conditional UI based on timestamps (created vs updated).

The final feature adds email notifications when a new chirp is created. A notification class is generated and customized to include the author’s name and a snippet of the chirp message. Instead of sending emails directly inside the controller, the workflow dispatches a “chirp created” event, then a queued listener sends notifications asynchronously. This decouples the user-facing request from the potentially slow email delivery. The session closes by discussing deployment paths—Laravel Forge for managed server provisioning and Laravel Vapor for serverless—framing both as ways to move from local development to production without abandoning Laravel’s tooling.