Weave Code
Voyager Pages Laravel Package
pvtl/voyager-pages
A Pages module for Laravel Voyager that adds admin CRUD for managing CMS pages, including titles, slugs, content, and templates, so you can build editable site sections without custom code.
A module to provide pages for Voyager 📃
Frequently asked questions about Voyager Pages
- What is pvtl/voyager-pages used for?
- pvtl/voyager-pages is a Pages module for Laravel Voyager that adds admin CRUD for managing CMS pages. It is intended for applications already using Voyager as their admin and BREAD layer, so editors can manage titles, slugs, content, and templates without custom code. It is not a general-purpose Laravel CMS and should only be evaluated when Voyager is already part of the stack.
- Is pvtl/voyager-pages compatible with Laravel 9, 10, or 11?
- Compatibility is not guaranteed and must be verified before adoption. The package is archived, with its last release dated 2020-01-14, so it predates Laravel 9, 10, and 11 and may not satisfy modern PHP or framework constraints. Run Composer why-not against your pinned Laravel, PHP, and Voyager versions, and assume incompatibility until proven otherwise.
- How do I install pvtl/voyager-pages in a Laravel Voyager application?
- The expected path is to require it through Composer in a Laravel app that already uses a supported Voyager version. Because the upstream package is archived, a safer approach is to fork it into internal VCS and require that fork with exact version pins. Then verify service provider discovery, publish and audit config, migrations, views, assets, and Voyager BREAD setup in a spike branch before production.
- Does pvtl/voyager-pages work with PHP 8?
- PHP 8 compatibility is not assured from the available package context and must be tested on your production PHP version. The last release was in January 2020, so dependency constraints may target older PHP branches. Do not assume PHP 8.x support; run the package through your test suite and a staging environment first.
- Is pvtl/voyager-pages still maintained?
- No, the repository is archived and the last release was 2020-01-14. There is no upstream security patching, Laravel or PHP compatibility work, or bug fixing. Treat it as internal code: fork it, assign an owner, and budget periodic dependency and security reviews.
- What are the alternatives to pvtl/voyager-pages for Laravel CMS pages?
- If you are not already committed to Voyager, do not introduce Voyager just to use this archived module. Build a small custom page model with CRUD, slugs, templates, status, and metadata, or choose a maintained Laravel CMS or page package that supports your Laravel and PHP versions. For existing Voyager apps, compare a maintained Voyager-compatible module or an internal fork before adopting this one.
- How does pvtl/voyager-pages handle page slugs, templates, and publishing status?
- The module is described as providing admin CRUD for CMS pages with titles, slugs, content, templates, and status concepts. The exact data model, routing assumptions, template rendering, publishing workflow, and permissions must be validated in source and staging. Do not assume localization, SEO metadata, versioning, or preview behavior without inspecting the package and testing editor workflows.
- Can I use pvtl/voyager-pages without Laravel Voyager?
- No, its architecture fit is conditional on the application already standardizing on Voyager as the admin and BREAD layer. It is a Voyager admin module, not a standalone Laravel page CMS. Using it without Voyager would add unnecessary surface area and likely break its CRUD, BREAD, middleware, and routing assumptions.
- What security risks should I review before using pvtl/voyager-pages?
- Review stored HTML and XSS risk, because CMS page content and templates may be rendered into public views. Confirm admin authorization, Voyager BREAD permissions, middleware, and route behavior, and verify that migrations and rollback plans are safe. Because the package is archived, your team owns patching any security issues and should complete a security review before production.
- How do I fork and maintain pvtl/voyager-pages for a legacy Laravel app?
- Fork the repository into internal VCS, tag an internal version, and require it through a VCS or path repository with exact Composer pins. Assign a maintainer, document the fork, run Composer why-not checks, and test service provider discovery, migrations, views, routes, and BREAD permissions on your production PHP version. Plan a replacement or exit strategy, including content portability and rollback, because upstream support is unavailable.
Weaver
How can I help you explore Laravel packages today?