Nova Spatie Translatable Laravel Package

Product Decisions This Supports

• Localization roadmap: This package layers on spatie/laravel-translatable, so it directly informs how we model and ship multilingual content (product names, descriptions, marketing copy) without building a bespoke translation layer. PM can position multilingual support as a near-term roadmap item rather than a multi-quarter build.
• Build vs. buy on i18n plumbing: Because translation storage/retrieval is handled by a mature ecosystem (Spatie) and this package extends it, the "build" option is largely replaced by configuration and integration work. This shifts engineering effort toward content operations and editorial workflows, which is where product differentiation actually lives.
• Runtime upgrade planning: PHP 8 support removes the previous runtime ceiling. This unblocks the platform upgrade track and lets us sequence the PHP 8 migration against feature work rather than as a separate risk-laden project.
• Content operations use cases: Editorial/admin tooling for managing translated fields, per-locale QA, and rollout of new markets become feasible deliverables we can scope and prioritize.
• Dependency governance: The spatie/laravel-translatable >= 5.0 alignment signals active ecosystem maintenance, which lowers vendor-risk in our dependency review and simplifies security-patch cadence.

When to Consider This Package

Adopt when:

• The product needs structured, per-locale content (multiple languages on the same entities) and the team is already on Laravel.
• You are standardizing on spatie/laravel-translatable for translation storage and want a supported integration layer rather than custom glue.
• You are planning or executing a PHP 8 upgrade and want dependencies to be compatible before the migration window.
• Editorial/admin translation workflows are on the roadmap and you prefer buying the plumbing over building it.

Look elsewhere when:

• Only one language is in scope now and no credible localization roadmap exists — the added abstraction cost isn't justified.
• You need a full translation management system (TMS) with human/AI translation pipelines, not just model-level field translation.
• The team is not on Laravel or has standardized on a different translation strategy.
• Strict dependency minimalism is a hard constraint and the Spatie coupling is unwelcome.

Caveats to verify pre-adoption: confirm the exact package identity/version history, its maintenance activity, and that it officially supports our Laravel version — the release notes confirm PHP 8 and Spatie compatibility but do not speak to broader framework support.

How to Pitch It (Stakeholders)

To executives: This release is a low-risk, compatibility-focused update — it adds PHP 8 support and aligns with the current version of the translation library it depends on. That means we can keep modernizing our platform while enabling multilingual content, largely through integration rather than custom development. Net effect: faster path to international markets and reduced engineering/maintenance cost versus building translation infrastructure ourselves.

To engineering: Release 2.2.0 is additive and non-breaking: PHP 8 support and compatibility with spatie/laravel-translatable >= 5.0. It unblocks the PHP 8 upgrade track and lets us lean on an actively maintained dependency instead of custom translation plumbing, reducing surface area we own. Recommend a timeboxed spike to confirm Laravel version support and integration fit before committing to the roadmap.