Filament Translatable Fields Laravel Package

Product Decisions This Supports

• Localization / market-expansion roadmap. This package is the cheapest lever for "ship our admin-authored content in N languages." It turns i18n of CMS pages, product names/descriptions, categories, and SEO meta from an engineering epic into a content-ops task with a locale switcher in the panel editors already use.
• Build vs. buy on admin form UX. The alternative is a bespoke "translatable tabs" Filament component — typically 1–3 weeks of build plus perpetual maintenance against every Filament upgrade. For most teams this is a clear buy; the build only wins if your form requirements are unusual (per-locale validation rules, workflow states, custom layouts).
• Data-model commitment: JSON columns + spatie/laravel-translatable vs. per-locale tables. This is the real decision the package forces. Adopting it means your translatable content lives in JSON columns with locale keys. That is fine for editorial content at 2–5 locales; it becomes painful for per-locale full-text search, sorting, or reporting at scale. Decide this deliberately, not as a side effect of picking the form widget.
• Launch gating for a specific market. If a market launch is blocked only on "editors can't enter translated copy," this package unblocks it without a schema migration or a new CMS.
• Translation-workflow sourcing. If product needs draft → review → approved states per locale, translator roles, or glossary/TM support, this package does not deliver that — it's a field-level editor, not a translation management system. That's an early roadmap fork (in-app editing vs. integrating Phrase/Lokalise/Crowdin).

When to Consider This Package

Adopt when:

• The admin is built on Filament and you already use (or are willing to adopt) spatie/laravel-translatable.
• You have a small, stable locale set (roughly 2–5) and editors authoring their own translations in-house.
• Your translatable fields are editorial text (rich editor, textarea, titles, meta) rather than high-volume, query-heavy data.
• You want locale-tabbed editing ergonomics without owning that component.

Look elsewhere when:

• You need per-locale workflow states, translator permissions, review queues, or TM/glossary — that's a TMS integration, not a field wrapper.
• You're outside Filament, or on a Filament major version the package doesn't explicitly support.
• You need per-locale indexed search/sort/reporting at scale — prefer per-locale tables or a dedicated translations table.
• Locale count is large (10+) or translations come from an external pipeline; hand-editing tabs does not scale operationally.

Maintenance / release signal (v2.0.15): The published notes for this release are a bare v2.0.13...v2.0.15 compare link with no changelog, and it skips a patch number. Treat it as patch-level with no evidenced breaking changes or deprecations, but do not assume — read the diff, pin the exact version in composer.json, and require a green CI run in a staging branch before merging. The absence of release notes is itself a due-diligence data point: confirm the package's support policy, Filament version coverage, and recent commit cadence before making it a load-bearing dependency.

How to Pitch It (Stakeholders)

For executives: This is a small, low-cost dependency that removes the engineering bottleneck from our localization roadmap. Instead of building and forever maintaining a custom multilingual admin form, our editors enter translated copy themselves in the panel they already use. Expected impact: market launches gated on content translation move from an engineering sprint to a content task measured in days. Risk is low and contained — it's a UI layer over a well-established Laravel translation library, not new infrastructure, and it can be swapped out without touching stored data.

For engineering: Thin, single-purpose wrapper over spatie/laravel-translatable that supplies locale-aware Filament form and table fields. Blast radius is the admin panel only; data lives in JSON columns and remains readable without the package. Two caveats: it couples us to Filament and Spatie major versions, so upgrades need a compatibility check; and the v2.0.15 release shipped without notes, so we pin the version, review the diff, and validate in staging rather than tracking ^2.0 blindly.

Recommended next step: Timebox a one-day spike — install pinned at v2.0.15, convert one real translatable resource, and confirm editor UX with the content team. Proceed or reject on that evidence, and decide the JSON-column vs. per-locale-table question in the same pass so it isn't inherited by default.