Weave Code
Voyager Page Blocks Laravel Package
pvtl/voyager-page-blocks
A Laravel package that adds reusable page blocks to Voyager, letting you compose pages from modular content sections managed in the admin panel. Includes block types, page associations, and flexible rendering for faster, more maintainable site building.
A module to provide page blocks for Voyager 📝
Frequently asked questions about Voyager Page Blocks
- What is pvtl/voyager-page-blocks?
- It is a Laravel package that adds reusable page blocks to Voyager, the BREAD-based admin panel. It registers a page_blocks content type plus an association so blocks can be attached to pages, letting you compose pages from modular content sections. It is a Voyager feature pack rather than a standalone content library, so it ships no REST or GraphQL surface of its own.
- How do I install pvtl/voyager-page-blocks?
- Use Composer to require the package, then register its service provider and publish the config, migrations, and assets. Run php artisan migrate to create the block tables and set up the Voyager BREAD entries for the new content type. Budget about a day for a developer already fluent in Voyager, plus additional time for content modelling.
- Which Laravel and PHP versions does this package support?
- The package was shipped in a PHP 7.2 to 7.4 and Laravel 5.8 to 8 era envelope, and its last release was July 2020. There is no official PHP 8.x or Laravel 9+ compatibility work. Verify it with composer require against your pinned versions before committing to anything.
- Does voyager-page-blocks work with Laravel 10 or 11?
- Not out of the box. With no releases since July 2020, the package predates Laravel 9, 10, and 11 and will likely break on framework contract changes and PHP 8 deprecations. Using it there means forking to a private VCS repository, bumping constraints, and fixing deprecations yourself.
- Do I need Voyager installed to use this package?
- Yes. It is a Voyager module and depends on Voyager's BREAD admin model, its admin UI, and Blade rendering. In a non-Voyager, headless, or API-first stack it is a non-starter because it contributes no standalone domain model and no API surface.
- How do I render page blocks in a Blade template?
- Rendering happens through Blade partials that read the block associations attached to the current page. The package provides block types and page associations but assumes a specific content model, so you will typically write or adapt partials per block type. Documentation is README-level, so expect to read the source to confirm the exact relationships.
- Can I create custom block types with this package?
- The package is built around block types plus page associations, so custom types generally mean extending that model with your own partials and BREAD definitions. Because documentation is thin, plan on reading the source and migrations to understand the schema. Any customization also becomes yours to maintain since there are no upstream updates.
- Is pvtl/voyager-page-blocks still maintained?
- No. The repository is archived and the last release was July 2020, so there are no security patches, PHP 8 fixes, or Laravel 9+ support. At roughly 75 stars it has no meaningful community to fall back on. Treat it as a vendored, forked dependency at best.
- Is voyager-page-blocks safe to use in production?
- Only inside an existing Voyager codebase where the alternative is rebuilding block content from scratch, and only as a vendored fork you own. There will be no upstream security patches, and the orphaned Composer dependency adds supply-chain exposure. Define who owns the fork and the patch SLA before committing.
- What are the alternatives to voyager-page-blocks?
- If you are already on Voyager and need block content, forking this package or building a small in-house block model is usually the cheapest route. If you are on modern Laravel, evaluate a maintained block-content package or a simple polymorphic blocks table with your own admin UI. Adopting Voyager purely to gain this module costs far more than building the equivalent.
Weaver
How can I help you explore Laravel packages today?