Filament Cms Github Laravel Package

Product Decisions This Supports

• Platform upgrade timing: v5.0.0 aligns the package with Filament v5 and Laravel 12/13 (PHP 8.2+). This release is the gating signal for any roadmap item that depends on moving the admin panel to Filament v5 — until now, that upgrade would have meant dropping CMS functionality or building a stopgap.
• Build vs. buy for content management: a ready-made CMS surface inside the existing Filament admin is a credible alternative to a custom content model + CRUD build. The decision hinges on whether your content needs are "structured pages, posts, media, revisions" rather than bespoke editorial workflow.
• Content migration as a de-risked launch activity: allowContentImport() surfaces a GitHub import action in the CMS plugin. For teams replatforming an existing site or seeding content from a repo-based source, this is a concrete reduction in migration scope — worth validating before committing to a manual content-loading plan.
• Dependency and cadence risk on the roadmap: the package tracks upstream Filament majors (v5 here). That means your CMS upgrade path is coupled to Filament's release cadence, which should be an explicit line item in upgrade planning rather than a surprise in a sprint.
• Use cases worth scoping: marketing/blog content, docs or help-center pages, and small editorial sites administered by internal staff — all inside an admin your team already operates.

When to Consider This Package

Adopt when:

• You are already on (or actively migrating to) Filament v5 with Laravel 12/13 and PHP 8.2+ — this release is explicitly built for that matrix and has a CI matrix across Laravel 12/13 × PHP 8.3/8.4.
• Your content model is conventional (pages, posts, media) and your editors work inside the app's admin, not a separate CMS.
• You want to avoid owning a content schema, editor UI, and permissions layer yourself.
• You need a low-friction import path for existing content and GitHub is an acceptable source.
• You can accept a community-maintained package and pin/monitor versions rather than depend on a vendor SLA.

Look elsewhere when:

• You are on Filament v3/v4, Laravel ≤11, or PHP <8.2 — v5.0.0 is a major-version break tied to upstream majors; staying put means staying on an older line of this package.
• You need multilingual editorial workflows, complex approval chains, scheduled publishing with audit requirements, or content APIs at scale — evaluate a dedicated CMS or headless platform instead.
• Your import sources are not GitHub (WordPress exports, legacy DBs, DAM systems) — the built-in action won't cover that, and you'd be building connectors anyway.
• Procurement requires vendor support, indemnity, or a security review with a named maintainer. Note also that content import is opt-in and off by default; enabling it is a deliberate decision to expose an import action in the admin UI, and should go through your normal permission and audit review.
• You need a guarantee of API stability across Filament majors — the version coupling here is structural, not incidental.

How to Pitch It (Stakeholders)

For executives: This is a small, free, community package that gives our Laravel admin panel a working content-management layer — pages, posts, media, editing — without a custom build or a separate CMS license. The new v5 release catches it up to the current Filament and Laravel versions, so it unblocks the admin upgrade we've had queued, and it adds a content-import action that shortens the content-migration work on any replatforming effort. Cost is near zero; the trade-off is that it's maintained by a small team, so we manage it the way we manage any open-source dependency — pinned versions, a compatibility check each upgrade cycle, and no reliance on vendor support.

For engineering: v5.0.0 is a breaking major — it requires Filament v5, Laravel 12/13, PHP 8.2+, and moves tomatophp/filament-cms to ^5.0; treat it as a coordinated upgrade, not a patch. Test coverage now runs against the package's own model factories and includes an install-command test plus a Laravel 12/13 × PHP 8.3/8.4 matrix, which is a meaningful improvement in upgrade confidence. The GitHub import action is gated behind allowContentImport() on the CMS plugin — it is off unless we turn it on, so enabling it is a product and permissions decision, not a default.