Nova Lang Laravel Package

Product Decisions This Supports

• Admin localization for Nova-based back offices. If your product runs on Laravel Nova, this package lets you assign locales to individual resources and sort a resource's index view — directly supporting decisions to ship a multilingual admin experience without building locale management from scratch.
• Build vs. buy for admin tooling. It is a small "buy-and-extend" candidate: adoption cost is low, but it should be treated as a forkable utility rather than a platform dependency. It is not a reason to choose Nova, and it is not a substitute for an application-level i18n framework.
• Roadmap scoping. Fits a phase-2 enhancement: "localize the back office for editors." If admin i18n is on the near-term roadmap and Nova is already the chosen admin layer, spike this package to validate fit before allocating engineering time.
• Use cases. Editorial teams managing region- or language-specific records, internal operations dashboards where ordering resources improves usability, and MVPs where Nova is already in place and small conveniences compound.
• Not supported: customer-facing i18n, multi-tenant content models, or translation workflow design. Those are separate architecture decisions.

When to Consider This Package

Consider it when:

• Your application is already built on Laravel Nova — the package is inert outside Nova.
• Your localization need is simple: assign a locale to a resource and reorder the resource index view.
• The team is willing to own a small MIT-licensed package — likely by forking or patching it.
• You are on a Nova version contemporary with the October 2020 release, or you will explicitly verify compatibility.
• The users are internal admins, where a broken locale switch or sort order is an annoyance rather than a business-critical failure.

Look elsewhere when:

• You need active maintenance, security patching, or vendor support — the last release was 2020-10-28 and adoption is minimal (~14 stars).
• You are on a recent Nova major version; expect incompatibilities and budget for remediation.
• You need a real translation workflow — per-field translatability, fallbacks, locale negotiation. Evaluate the vendor's successor packages (optimistdigital is now outl1ne), spatie/laravel-translatable, or a thin custom Nova tool.
• You need multi-tenant or multi-language customer-facing content; this is admin tooling, not an i18n framework.
• Procurement or architecture standards require healthy maintenance signals (release cadence, contributor base, issue response).

How to Pitch It (Stakeholders)

Executives / sponsors: This is a small, MIT-licensed convenience package for our Laravel Nova admin. It saves a modest amount of custom development for assigning locales to admin resources and ordering resource index views. It is useful but not strategic. The risks are clear: very low adoption (~14 stars), no release since late 2020, and a single-vendor origin (optimistdigital, now outl1ne). It is not something we should rely on for customer-facing experiences. Recommendation: approve only as an internal productivity aid, with a fallback to fork or replace, and cap investment accordingly.

Engineering: The scope is narrow — locale assignment on Nova resources and sortable index views. Integration cost is low, and the MIT license lets us fork freely. The caveat is staleness: verify compatibility against our Nova version before committing, and timebox a short spike to confirm behavior. If it fits, treat it as a forkable utility we own, not a black-box dependency. If richer i18n requirements emerge, evaluate maintained alternatives or build a thin custom Nova tool instead.