Nova Persian Date Laravel Package

Product Decisions This Supports

• Persian/Jalali admin UX for Laravel Nova: Supports a localized date input/display field for Persian-speaking operators, reducing training and date-entry errors in internal admin workflows.
• Localization roadmap prioritization: Helps decide whether Persian calendar support is a narrow Nova admin enhancement or part of a broader product localization milestone.
• Build vs. buy vs. fork: Offers a low-cost trial candidate for a single Nova field; given only 11 stars and a last release of 2021-05-29, treat it as a spike/fork candidate rather than a strategic dependency.
• Canonical date storage vs. localized display: Reinforces the product requirement that dates should be stored in a canonical format while Persian/Jalali presentation is a UI concern for authorized admin users.
• Feature acceptance criteria: Defines PM expectations: correct Jalali input/display, Gregorian storage compatibility, timezone behavior, validation, filtering/sorting behavior, and compatibility with the team’s Nova/Laravel/PHP versions.
• Operational use cases: Relevant for scheduling, publishing, HR/finance admin, reporting filters, and other Nova-backed back-office forms where Persian-speaking staff work with dates daily.
• Vendor-risk planning: Signals a need to decide whether to pin the package, vendor/fork it, assign an owner, or replace it if Nova upgrades break compatibility.

When to Consider This Package

Consider it when:

• The product already uses Laravel Nova for internal admin or operations.
• A meaningful user group needs Persian/Jalali date entry or display in Nova forms.
• The scope is a single date field, not a full calendar, recurrence, booking, or customer-facing scheduling system.
• Engineering can run a time-boxed compatibility spike against the current Nova, Laravel, PHP, and database stack.
• The team accepts community-package maintenance risk or is prepared to fork/pin/vendor the code.
• Date conversion, timezone handling, validation, and storage format can be covered by tests.

Look elsewhere or build in-house when:

• The team does not use Laravel Nova.
• The project needs a maintained, supported dependency with recent releases and broad adoption.
• Current Nova/Laravel versions are incompatible or unknown, and no engineering capacity exists to fork.
• Requirements include complex date logic: recurring events, date ranges, business calendars, Hijri support, advanced validation, or customer-facing calendar UI.
• The field must meet strict security, accessibility, or long-term support standards.
• A native Nova field, a maintained alternative, or a thin custom field would be safer and cheaper to own.

How to Pitch It (Stakeholders)

Executive summary: This is a narrow localization package for Laravel Nova that can improve date entry for Persian-speaking admin users. It is potentially useful for back-office UX, but it is not a strategic platform dependency: low adoption and no release since May 2021 create maintenance and compatibility risk. Approve only as a small, isolated pilot with engineering validation and a clear fallback.

For engineering: Evaluate compatibility with the current Nova/Laravel/PHP stack, verify Gregorian storage and Jalali display behavior, test timezones and validation, and estimate fork/maintenance cost. If adopted, pin the version, add tests, and assign an owner.

For product: Use it only where Persian date entry in Nova materially improves operator speed or accuracy. Keep canonical date storage standardized, define acceptance criteria for conversion and timezone behavior, and avoid expanding it into complex calendar or customer-facing requirements without a broader build-vs-buy review.