Weave Code
Voyager Blog Laravel Package
pvtl/voyager-blog
A Laravel Voyager package that adds blog management to the admin panel, providing CRUD for posts, categories, and tags plus frontend-ready models and routes for publishing and displaying articles in your application.
A module to provide blog posts for Voyager ✍️
Frequently asked questions about Voyager Blog
- What does pvtl/voyager-blog actually do?
- It is a Laravel package that plugs blog management into the Voyager admin panel, adding BREAD-style CRUD for posts, categories, and tags. It also ships frontend-ready models and routes so you can publish and display articles in your application. It is not a general-purpose Laravel blogging platform; it is a Voyager-specific module.
- Which Laravel and Voyager versions does pvtl/voyager-blog support?
- The repository is archived and does not publish a maintained compatibility matrix, so you must verify Composer constraints yourself. Check the composer.json requirements against your Laravel, PHP, Voyager, and database versions before installing. Run a version spike in a disposable branch rather than assuming current Laravel or Voyager support.
- Is pvtl/voyager-blog still maintained?
- No. The package is archived with low adoption signal, which means no upstream fixes, dependency updates, or security patches. Treat it as unsupported code that your team owns the moment you install it. If you adopt it, budget for a maintained fork or a documented replacement plan.
- How do I install pvtl/voyager-blog in an existing Voyager app?
- Require the package with Composer on a disposable branch, pinning exact versions to avoid surprises. Review and run the migrations, publish any assets or config, and confirm the Voyager BREAD definitions appear correctly in the admin panel. Then check route registration for collisions before migrating real content through a controlled script.
- Does pvtl/voyager-blog work with Nova, Filament, or a custom admin panel?
- No, it is built specifically around Voyager's BREAD conventions, admin middleware, and model patterns. Adapting it to Nova, Filament, or a bespoke admin would likely cost more than writing first-party Post and Category models. Reject or rewrite it if Voyager is not already your admin stack.
- Does pvtl/voyager-blog provide frontend routes, slugs, and SEO fields?
- The package advertises frontend-ready models and routes for publishing and displaying articles, alongside categories and tags. Exact details such as slug generation, media handling, and any SEO fields should be confirmed by reading the source and route files after install. Do not assume SEO features exist without verifying them in the code.
- Are the migrations in pvtl/voyager-blog safe and reversible?
- You need to audit each migration yourself because the archived status means no guarantee of idempotency or clean rollbacks. Test migrate and rollback in a sandbox database before touching production. Watch for duplicate table creation and naming collisions with existing blog or content tables.
- Is pvtl/voyager-blog secure enough for production rich-text content?
- Because the package is unmaintained, you inherit responsibility for sanitization and security patching. Rich-text fields from an admin editor are a common stored XSS vector, so add your own sanitization layer and review how media uploads are handled. Also verify permission checks on admin routes and orphaned media cleanup.
- Should I use pvtl/voyager-blog for a new Laravel project?
- No. For greenfield builds, write straightforward Post and Category models yourself or choose a maintained blogging or CMS package. This module only makes sense as a tactical accelerator inside an existing Voyager estate, or as a reference implementation for blog schema and admin patterns.
- Can I fork or vendor pvtl/voyager-blog and maintain it internally?
- Yes, forking or vendoring is the realistic path if you adopt it, since the original repository is archived. Check the license terms in the repository first and confirm they permit your intended redistribution or internal modifications. Plan explicit ownership for dependency updates, security patches, and an exit path if Voyager is ever replaced.
Weaver
How can I help you explore Laravel packages today?