- What is phpsa/filament-headless-cms and what does it do?
- phpsa/filament-headless-cms is a Laravel package that adds content-management domain concepts such as content types, entries, fields, and media on top of Filament. Filament serves as the authoring and admin surface, while a decoupled frontend consumes the content through APIs. It is intended for TALL-stack teams that want CMS capability without running a separate CMS platform. Note that the v1.1.0 release has no human-authored release notes, so verify specifics against the code and README.
- How do I install phpsa/filament-headless-cms in a Laravel app?
- The expected flow is composer require phpsa/filament-headless-cms, publish the package config and migrations, then register the Filament panel or plugin. You should review the published config and migration files before running them, because the package owns the content schema shape. Because no dependency manifest was supplied for this assessment, confirm exact install steps against the repository README and composer.json for your Laravel and Filament versions.
- Which Laravel and Filament versions does phpsa/filament-headless-cms support?
- The package is built for Laravel applications that use Filament, and the assessment targets Laravel 10 through 12 on PHP 8.2+ with Filament 3.x or 4.x. However, declared Composer constraints and a CI matrix were not provided, so treat that as an evaluation target rather than a confirmed support promise. Check composer.json and the project CI configuration before committing to a version pair.
- Does phpsa/filament-headless-cms provide a REST or GraphQL API?
- The package is described as headless, meaning content is authored in Filament and delivered to a decoupled frontend, but the assessment could not confirm whether the delivery API is REST, GraphQL, or configurable. You also own the API contract your frontends depend on, even if the package supplies endpoints. Read the routes, controllers, and documentation in the repository to confirm response shapes and versioning.
- How do I model content types and fields with phpsa/filament-headless-cms?
- You model structured content through content types, entries, and fields, which are managed in the Filament admin panel. The package controls the schema shape, so plan your domain model and migration strategy before seeding production content. Confirm which field types ship in v1.1.0 by reading the source, since release notes do not describe changes.
- Is phpsa/filament-headless-cms production-ready and stable for a real project?
- Treat the API contract as unstable until you have verified it. A 1.0.1 to 1.1.0 minor bump should be additive, but without a human changelog you cannot confirm whether field definitions, storage schemas, or API responses changed. Filament plugin ecosystems sometimes ship schema-affecting changes in minor releases, so pin versions and review diffs before upgrading.
- How does phpsa/filament-headless-cms handle media uploads and storage?
- Media handling is part of the package content-management domain, but the assessment did not verify supported storage drivers, image transforms, queue behavior, or failure handling. In production, confirm upload validation and authorization are enforced by the package rather than assumed. Test S3-compatible or local driver behavior directly in a staging environment.
- Does phpsa/filament-headless-cms support drafts, publishing workflows, and content versioning?
- Draft and publishing workflow plus content versioning are not confirmed by the supplied material. The assessment explicitly flags editorial workflow and content-versioning depth as areas where thin CMS packages often under-deliver. If those are hard requirements, verify them in the admin UI and database schema before adopting, or consider a commercial CMS.
- How should I test phpsa/filament-headless-cms before adopting it?
- Start by reading the v1.0.1 to v1.1.0 diff, composer.json constraints, CI configuration, and any tests or static analysis setup. Install it in a throwaway Laravel app, publish config and migrations, create a content type, and exercise the delivery API behind authentication. Check open issues, commit cadence, and whether one maintainer cuts releases.
- What are alternatives to phpsa/filament-headless-cms and when should I choose one?
- Choose this package when you are already on Laravel and Filament and want CMS capability without a second platform, such as a monolith or a small standalone content service. It is a poor fit when editorial workflow, localization depth, or content-versioning depth are hard requirements, where a commercial CMS may earn its licence. Also compare other Laravel headless CMS packages by verifying maintenance activity, API documentation, and upgrade paths.