Filament Language Tab Laravel Package

Product Decisions This Supports

• Feature scoping for a Filament-native admin experience: This release confirms first-class Filament integration (custom label closures on fields), meaning we can ship admin UI customization without forking Filament components or building our own field abstraction. This is a build-vs-buy signal: the package already covers the rendering hooks we would otherwise hand-roll.
• Workflow features that need a draft/commit split: The preview addition and the beforeSave lifecycle hook together support editing flows where users preview changes before persisting. This directly enables roadmap items like "draft settings," "staged configuration," and "review before publish" without custom state machinery.
• Extensibility / developer surface area: The facade plus closure-based label customization indicate a public API designed for host apps to override behavior. This supports decisions about whether to expose a plugin API to customers or keep customization internal-only (recommendation: keep internal for v1, since 1.0.0 is the first stable tag).
• Use cases now credible: admin-managed configuration panels, content or catalog metadata editing with a preview step, and any CRUD surface where saves must run pre-persist business logic (validation, normalization, audit stamping).
• Roadmap timing: Because this is the initial 1.0.0, we should scope adoption around a low-blast-radius internal tool first, not a customer-facing critical path.

When to Consider This Package

Consider it when:

• We are already on a Filament-based admin panel and want label/field customization (including dynamic labels via closures) without patching vendor code.
• A feature needs a preview-before-save UX and a pre-persist hook (beforeSave) for validation or normalization — the package's lifecycle already models this.
• We want a facade-driven API that keeps call sites terse and mockable in tests.
• We need a small, composable primitive rather than a full domain module; the surface area here looks intentionally narrow.

Look elsewhere when:

• The requirement is a mature, battle-tested configuration system with a long migration and deprecation history — 1.0.0 with an initial code drop means unproven edge cases and likely churn in the 1.x line.
• We are not on Filament; the label-closure value proposition is largely Filament-shaped.
• We need formal SLAs, security review artifacts, or a multi-year support commitment — there's no evidence of that maturity yet.
• Our flow requires transactional guarantees around beforeSave (atomicity across multiple models); verify hook semantics against DB transaction boundaries before committing, as lifecycle hooks of this kind often fire inside but not across transactions.

Adoption criteria / gates before production: pin the version, read the actual hook execution order, add a test around beforeSave failure paths, and confirm preview state is not persisted inadvertently.

How to Pitch It (Stakeholders)

To executives: This is a small, focused Laravel package that removes bespoke work from our admin tooling. It already delivers the two things our roadmap needs — a preview step before saving changes and a pre-save hook for business rules — on top of our existing Filament admin stack. The strategic value is reduced custom code and faster delivery of admin-facing features, not a platform bet. It just reached its first stable release, so treat it as an early-adopter dependency: low cost to try, contained risk if we pilot it on an internal tool.

To engineering: 1.0.0 is the base release. It ships a facade, a beforeSave lifecycle hook (with tests and a logic fix landed in this release), a preview capability, and Filament integration for custom label closures. The API is closure-friendly, so host apps can customize rendering without subclassing. Caveats: this is an initial drop, so expect 1.x churn; validate hook ordering, exception behavior, and transaction semantics in a spike; and confirm the preview path cannot write to persistent storage. Estimate: a half-day spike to de-risk, then a contained pilot.