- What is hansschouten/laravel-pagebuilder used for?
- It provides a drag-and-drop, block-based page editor for Laravel applications, aimed at admin-managed marketing pages, campaign pages, and CMS-lite editorial content. Pages are stored as structured block and layout data on an Eloquent page model and rendered through Blade. It is not designed for headless or multi-channel content delivery, and it does not provide editorial governance, versioning, or approval workflows out of the box.
- How do I install Laravel Pagebuilder in a Laravel app?
- Install it with Composer, then publish the package's config, migrations, and front-end assets using Laravel's vendor publish command. Your application supplies the Page model and routing, and you wire the builder's render path into your Blade views. Installation is moderate and mostly front-loaded; the bigger effort is deciding where the admin routes live behind your own auth and permission layer.
- Which Laravel and PHP versions does Laravel Pagebuilder support?
- The package's release metadata does not clearly state minimum PHP or Laravel versions, so you must check its composer.json constraints against your platform before scoping. A Laravel major-version mismatch would turn adoption into a platform upgrade project rather than an afternoon task. Confirm the current v0.31.0 constraints specifically, because a minor release can raise requirements in a 0.x package.
- Is Laravel Pagebuilder safe to use in production?
- It can be used in production for CMS-lite pages, but you own the security posture: put the builder's admin routes behind your own authorization and sanitize author-supplied markup to prevent stored XSS. The package is pre-1.0 with a single maintainer, so pin a version and avoid a take-the-latest upgrade policy. Wrapping its render helper behind a thin internal interface limits the blast radius of upgrades.
- How does Laravel Pagebuilder store page content?
- It persists page composition as structured block and layout data against an Eloquent-backed page model, with JSON column support expected from MySQL or Postgres. Because content is stored as structured data, block schema changes between releases can make previously saved pages render incorrectly or fail to re-edit. Verifying schema stability is the most important check before any upgrade.
- Can I upgrade Laravel Pagebuilder from 0.30 to 0.31 without breaking changes?
- Treat every 0.x minor bump as potentially breaking, including 0.30 to 0.31, because semver permits breaking changes before 1.0. The v0.31.0 release note contains no changelog, migration notes, or diff, so an engineer must review the tag diff directly. Check specifically for changes to the page and block data schema, published migrations, config keys, and minimum PHP or Laravel versions, then test that previously saved pages still render and re-edit.
- Does Laravel Pagebuilder work with headless or decoupled front ends?
- No. It is a server-rendered, Blade-based builder, so it fits content-managed pages inside a Laravel monolith rather than headless or multi-channel delivery. If your roadmap includes decoupled front ends, adopting this package creates a migration liability instead of a foundation. Evaluate it only for Blade-rendered marketing or editorial pages.
- How do I render a Pagebuilder page in a Blade view?
- The package provides a render helper that outputs a saved page's blocks through Blade, and your app wires that into its routing and views. Rather than calling the package helper directly throughout your views, create a thin internal renderer interface so a 0.x upgrade has a contained blast radius. This seam also lets you add sanitization or custom block output without touching every template.
- Does Laravel Pagebuilder include automated tests I can run?
- The release metadata does not document test coverage or CI status, so you should inspect the upstream repository's CI configuration and test suite before relying on it. Budget for your own integration tests that cover page creation, saving, re-editing, and Blade rendering against your app. Testing the block schema round-trip is especially important before upgrading.
- What are alternatives to Laravel Pagebuilder for admin-managed pages?
- Alternatives include building a custom block editor with Filament or Nova, adopting a fuller Laravel CMS such as Statamic, or using another block-based page builder package. The right choice depends on whether you need editorial workflows, headless delivery, or a stable 1.0 support window. Laravel Pagebuilder is a reasonable fit only for Blade-rendered, CMS-lite pages where you can accept 0.x maintenance risk.