Livewire views, edited in the browser — and the honest catch

Live selection and inline editing during a session. Livewire re-renders a component by sending new HTML from the server and morphing it into the existing DOM, so the nodes an editor was holding onto can be replaced underneath it and a selection or an in-progress inline edit resets. The recommended pattern is to make a change and Save rather than to nudge a value repeatedly across several server round trips.

Yes, and that is the part worth separating out. All four write lanes — text, attribute, class and page settings — write on Livewire, proven against a real Livewire fixture project in PortBay's cross-stack test, which edits resources/views/pages/about.blade.php and reads the changed bytes back off disk. The caveat is about the live editing session, not about whether your file changes.

PortBay identifies the Laravel family from a composer.json plus an artisan file, then reads composer.json for livewire/livewire in either require or require-dev. Order matters: inertiajs/inertia-laravel is checked first, so a project carrying both is treated as Inertia, which sits on a better-supported lane. A Laravel project with neither is plain Laravel.

Not on this lane, and it would be easy to imply otherwise. The stamper's capability upgrade is wired to plain Laravel projects specifically, not to the Livewire variant, so a Livewire project edits by locating your markup in your .blade.php files rather than by following a source coordinate. In practice that means text, class and attribute edits write, structural edits are refused rather than guessed, and style edits go to a PortBay override sheet instead of into your templates.

Into the Blade view for that route — the section the layout yields, in the same file you were just editing markup in. PortBay resolves the route through routes/web.php to the view it renders rather than guessing which of your templates serves the URL. The layout has to declare the containers for this to land anywhere useful, which is the ordinary Laravel layout shape rather than something PortBay asks you to add.

No, and for the same reason it is not on any server-rendered stack: the words came from your data, not from the template, so there is nothing in the file to rewrite. What does edit is everything around them — the classes, the attributes, and the literal text you wrote. A class on the element inside a foreach edits normally, because that class is in your file exactly once.

No. It is a PortBay Pro feature, still in early access behind an opt-in toggle in Settings, and it is not compiled into the open-source build. It refuses to run while the project is shared over a public tunnel, and the edit bar works only on local .test hosts. Running Livewire on a real .test domain with trusted HTTPS, with PHP-FPM and a database managed for you, is in the free app.