GUIDES
Three different front-end libraries for the same basic pattern: an AJAX endpoint returning matching records, and a widget that queries it as the user types.
Setting up tymon/jwt-auth for a stateless API, and why JWT is the wrong choice for a normal server-rendered app with sessions.
AJAX itself can't trigger a browser navigation — the redirect happens with plain JavaScript inside the success callback, once the AJAX call has confirmed the server-side action completed.
Angular needs a small service (or a package) to touch document.cookie safely, while Laravel wraps cookies in its own facade with automatic encryption baked in.
A modern Laravel API separates routes, validation, authorization, persistence, resources, authentication and tests instead of returning raw models from controllers.
PDO is the modern, framework-agnostic way to talk to MySQL from plain PHP — and prepared statements aren't optional if user input touches the query.
Three ways to call an external API from PHP or Laravel — raw cURL, file_get_contents with a stream context, and Laravel's own Http facade, which is the one worth reaching for in a Laravel app.
This 419 error almost always means the CSRF token sent with an AJAX request is missing, stale, or the session simply expired — the fix depends on which of those three it actually is.
withTrashed(), onlyTrashed(), and restore() — plus the query-scope gotcha that makes soft-deleted rows silently vanish from relationships by default.
GDPR requires genuine opt-in consent before non-essential cookies are set — this means holding off on analytics and marketing cookies until the user actually agrees, not just displaying a banner.
session()->flash() for a message that survives exactly one redirect, and why it disappears if you check for it before the redirect actually happens.
How Laravel's broadcasting system turns a server-side event into a message a browser receives instantly — and what actually needs to run for it to work.
