Laravel package

Laravel Page Editor lets you update page content while browsing the page.

I have just released Laravel Page Editor, a new Composer package for Laravel. The basic idea is simple: instead of sending somebody into a separate CMS, you let them open the page they want to change, click edit, and update the content right there.

Why I built it

I have needed a traditional back-end CMS less and less on recent projects. A lot of page creation and iteration now happens directly in the codebase, especially when AI is helping me build pages or make layout changes quickly. In that setup, building a full admin area for a handful of text or image edits can feel like overkill.

The problem is that clients still need to change the odd heading, paragraph, link or image. They should be able to do that without touching code, and without me turning every marketing page into a full component system backed by a custom database structure.

The gap I kept running into

There is an awkward middle ground between “hard-coded Blade page” and “full CMS project”. That middle ground is where a lot of real websites live. They mostly work fine in code, but they need occasional content edits from non-developers.

There is also a practical AI angle to this. If content disappears into a CMS database, the codebase loses a chunk of the context that AI tools can use when helping with page changes. Keeping defaults in Blade while allowing controlled published edits felt like a better balance.

What Laravel Page Editor does

The package adds on-page editing for Laravel Blade views. You mark text, links and images as editable, sign in with your normal Laravel login, and make the change while looking at the page itself. It also supports draft saves, publishing, revision history, and editable SEO metadata, so there is enough control for real client work without spinning up a separate CMS product.

It uses the application's existing authentication rather than inventing another login. Editors are explicitly allow-listed, and the content stays tied to the page instead of being pushed into a much larger admin workflow.

When I would use it

I would use it on Laravel sites where the structure is developer-led but the business still needs light content control. Brochure sites, landing pages, campaign pages, and service pages are the obvious examples. It is especially useful when the team wants a simple way to make small amends without inheriting the cost of a bespoke CMS build.

If a project genuinely needs complex editorial workflows, collections, or heavy content modelling, a fuller CMS may still be the right answer. This is not me pretending every content problem should be solved with one package. It is for the cases in the middle that are usually underserved.

Why this matters to my Laravel work

A lot of my Laravel development work sits in that space between clean engineering and practical day-to-day use. The right solution is not always a bigger system. Sometimes it is a small tool that removes friction without adding another layer to maintain.

If you want to try it

The package is available on GitHub and installable through Composer as digizu/laravel-page-editor. If you are working on a Laravel site that needs straightforward content editing without a full CMS rebuild, it may save you a fair bit of time. And if you want help deciding whether this approach fits your project, you can get in touch here.