Weave Code
Filament Cms Laravel Package
webduonederland/filament-cms
A content management toolkit for Filament admin panels. Manage pages, posts, and structured content directly from Filament resources, with a flexible, Laravel-native setup that keeps everything editable in the familiar admin UI.
Highly advanced CMS for your Laravel website built with FilamentPHP!
Frequently asked questions about Filament Cms
- What is webduonederland/filament-cms and what does it do?
- webduonederland/filament-cms is a CMS layer for Laravel applications that run Filament admin panels. It lets you manage pages, posts, and structured content directly from Filament resources instead of building a bespoke content admin yourself. Under the hood it is a Filament plugin stack (Filament, Livewire, Laravel), so it adds a content management surface rather than infrastructure.
- How do I install filament-cms in a Laravel app?
- Install it with Composer using composer require webduonederland/filament-cms, then register the service provider if auto-discovery does not cover it. Publish the package config and migrations, run php artisan migrate, and mount the CMS resources in your Filament panel provider. Check the README for the exact panel registration and any seeder steps for initial content.
- Which Laravel, Filament and Livewire versions does filament-cms require?
- Version 2.0.0 targets Laravel 13, Filament 5, and Livewire 4, all current-generation majors. Older releases such as 1.3.4 are the option for apps still on earlier Laravel or Filament versions. Confirm the rest of your dependency graph is on the same majors before installing.
- Can I use filament-cms on Laravel 11 or 12 with Filament 3?
- Not with 2.0.0, which pins Laravel 13, Filament 5, and Livewire 4, so Laravel 11/12 with Filament 3/4 cannot consume it. Staying on filament-cms 1.3.4 or upgrading the platform first are the realistic choices. Treat the latter as a coordinated platform upgrade rather than a routine dependency bump.
- How do I upgrade from filament-cms 1.x to 2.0?
- 2.0.0 is described as a compatibility release with small refactors, but it still carries breaking changes, so read UPGRADE.md before touching code. Expect config republishing, migration and namespace changes, and possible panel provider or custom block and field rewrites. Freeze feature work, branch, upgrade the platform (Laravel 13, Filament 5, Livewire 4) first, then apply the CMS upgrade.
- Do I need to already use Filament for my admin panel?
- Yes. The package is built on Filament and Livewire, so adopting it means adopting Filament as a de facto architectural dependency. It fits best when the team has already standardised on Filament for back-office tooling. If you use Nova, Backpack, or a custom Blade/Inertia admin, this is not a drop-in addition.
- Does filament-cms add its own database tables and migrations?
- The package ships migrations you publish and run, so it owns its content tables and models. That makes the exit cost worth assessing up front if you might outgrow the package later. Check the UPGRADE.md diff for 2.0.0 to see whether migrations changed and whether they are reversible or backfill-safe on existing content.
- Can I model custom content types or blocks beyond pages and posts?
- The package covers pages, posts, and structured content, with content modelling tracking its opinions. Extending beyond that likely means custom Filament resources or reworking the package's blocks and fields. Diverging heavily from the built-in model is where integration cost grows.
- Is filament-cms production-ready and how is it maintained?
- The 2.0.0 release is a single contributor's PR against a community package, so bus factor and support responsiveness are real considerations for anything content-facing. Ask about the test matrix and CI coverage across Laravel 13, Filament 5, and Livewire 4 minor versions, and check median issue response time. Pin versions and keep upgrade budget for the next Filament major, since a 3.0.0 is likely in that window.
- What are the alternatives to filament-cms for a Laravel CMS?
- Alternatives include building your own Filament resources for content, or a standalone Laravel CMS such as Statamic if you want content modelling outside the admin panel. A custom Filament resource set is more work up front but avoids upstream coupling and gives you full schema ownership. filament-cms makes most sense when you want an opinionated CMS on top of Filament with minimal build time.
Weaver
How can I help you explore Laravel packages today?