Part 10 of Building Lattice — distribute a custom component's PHP class and its React renderer as a single Composer package. No npm publish; the Vite plugin compiles the renderer straight into the consuming app.
Read morePart 9 of Building Lattice — a notification bell built on Laravel's native notifications table, where each notification is a self-describing payload the bell renders, actions and all.
Read morePart 8 of Building Lattice — declare a page's websocket listeners in PHP (channel, events, and the effects to run) and Lattice wires up the subscription. Server-driven realtime, no hand-written JS.
Read morePart 7 of Building Lattice — a fragment is a reusable chunk of schema with its own endpoint, so heavy parts of a page load on demand instead of blocking the first render.
Read morePart 6 of Building Lattice — layouts are server-described schemas with an Outlet where the page renders, and menus are PHP definitions that resolve their own routes.
Read morePart 5 of Building Lattice — an action is a definition plus a handle() that returns effects, so a button click runs server code and dispatches a toast, a redirect or a refresh back to the client.
Read morePart 4 of Building Lattice — declare columns in PHP and let Lattice handle sorting, filtering and pagination, backed by a data source that doesn't have to be Eloquent.
Read morePart 3 of Building Lattice — a form is fields you declare and a handle() you write, validated live with Precognition and never bound to a model's columns.
Read morePart 2 of Building Lattice — the contract underneath it all: PHP serializes a typed tree of nodes, and one React component renders it through a registry.
Read moreMy new side project — describe pages, forms and tables once in PHP and render them as real React over Inertia, decoupled from the data model.
Read more