- What is phpsa/filament-cms and what does it do?
- phpsa/filament-cms is a Laravel package that layers CMS functionality on top of Filament, giving you a single admin panel for pages, posts, media, navigation, and publishing. Instead of building content resources from scratch, you get ready-made Filament resources and workflows for everyday website management. It is aimed at teams already using Filament who want editorial tooling without adopting a separate CMS platform.
- How do I install phpsa/filament-cms in a Laravel application?
- Install it with Composer using composer require phpsa/filament-cms, then run the package migrations so the content tables are created. You will typically publish any provided config or assets and register or discover the resources inside your Filament panel provider. Check the repository README for the exact publish tags and any seed or setup commands, since those details can change between releases.
- Does phpsa/filament-cms require Filament to be installed first?
- Yes. The package is a CMS layer for Filament, so you need a working Laravel app with Filament installed and at least one panel configured before using it. The CMS screens are Filament resources and pages, so they appear inside your existing panel rather than as a standalone admin area. If you have not set up a panel yet, do that first and confirm you can log in.
- Which Laravel and Filament versions does this package support?
- Version support is defined in the package's composer.json constraints, so check those before installing or upgrading. Filament has had breaking changes between major versions, so match the package release to your Filament major version rather than assuming compatibility. When upgrading Laravel or Filament, review the package changelog and test your content resources in a staging environment first.
- What content types can I manage with phpsa/filament-cms?
- The package covers pages, posts, media, navigation, and publishing, which are the usual building blocks of a content-managed site. Pages typically map to static or structured site sections, while posts suit blog or news style content. Navigation management lets editors control menus from the panel instead of editing templates by hand.
- How does media handling work and where are uploaded files stored?
- Media is managed through the panel and stored using Laravel's filesystem abstraction, so uploads land on whichever disk you have configured, such as local storage or S3. That means your existing filesystem configuration and storage linking conventions apply. For production, confirm your public disk, storage symlink, and any image conversion or size limits are set up as you expect.
- Can I customise the Filament resources, fields, and frontend views?
- Yes, in the usual Laravel and Filament way. You can extend or override the provided resources, publish views and config where the package allows it, and point your application's routes and Blade templates at the stored content. Because everything lives in your own Laravel codebase, you are not locked into a hosted CMS or external API.
- How do drafts and publishing work in phpsa/filament-cms?
- Content is authored and published from the Filament panel, so editors can create entries, save work in progress, and then make them live. The package's publishing workflow is intended to replace manual database edits or hardcoded copy with a repeatable editorial process. Review the package documentation for the exact status fields and whether scheduled publishing is supported in your version.
- Is phpsa/filament-cms suitable for production use?
- It can be, provided you treat it like any other admin package: restrict panel access with Filament's authentication and authorisation, use policies for content roles, and keep dependencies updated. Run the migrations and test the publishing flow on staging before deploying, and back up your database during upgrades. Because content changes happen through the panel, make sure only trusted users can reach those routes in production.
- How does it compare with alternatives, and is it actively maintained?
- The main alternatives are hand-building Filament resources, using a full CMS such as Statamic or WordPress, or adopting another Filament CMS package. phpsa/filament-cms makes sense if you want editorial features without leaving the Filament ecosystem you already use. Check the GitHub repository for recent commits, releases, open issues, and whether the maintainers respond, and write a few feature tests around your own resources so upgrades stay predictable.