Nova Range Filter Laravel Package

Product Decisions This Supports

• Configurable autoplay cadence on carousels/slider surfaces: The 0.0.2 release adds a settable slider interval, meaning product/design can now tune rotation speed per surface (homepage hero, promo banners, testimonial rotators) without custom JS. This informs UX decisions like "how long does a slide stay visible" per placement rather than a hardcoded global default.
• Whether to adopt vs. build: Because the interval is now configurable, the package moves from "demo-grade" toward "configurable primitive." This is the minimum bar for considering it in a feature spec versus building a lightweight slider in-house.
• Roadmap timing: Still at 0.0.2 (pre-1.0). Treat as an experiment/prototype dependency, not a committed platform choice. Do not anchor a launch-critical marketing surface to it yet.
• Low-risk pilot use cases: Internal dashboards, admin panels, or non-critical marketing widgets where a slightly unstable slider doesn't jeopardize revenue.

When to Consider This Package

Consider it when:

• You need a Laravel/PHP-native slider and want to avoid pulling in a heavier JS carousel framework.
• Autoplay timing must differ per placement and you want that configured server-side/config-side rather than in front-end code.
• The use case is low-blast-radius (internal tools, secondary marketing modules, prototypes).

Look elsewhere when:

• You need accessibility guarantees, RTL, reduced-motion handling, lazy-loading, or touch/swipe — none of which this release note evidences.
• You require a stable API (semver ≥1.0), active maintenance guarantees, or documented support.
• The slider is a core conversion surface (homepage hero, pricing, checkout-adjacent) where a pre-1.0 dependency is a delivery risk.
• You already use a mature front-end component library; adopting this adds a dependency for marginal gain.

How to Pitch It (Stakeholders)

For executives: A small, low-cost Laravel slider component just gained configurable rotation timing — useful for tuning promotional surfaces. It is still pre-1.0 and should be framed as a pilot, not a platform commitment; expected value is developer-time savings on simple carousels, with contained risk if limited to non-critical surfaces.

For engineering: v0.0.2 exposes a configurable interval, replacing a likely hardcoded autoplay value. This is a minor, additive feature — no breaking-change signal in the note, but the 0.0.x version line means the API is not yet stable. Recommendation: evaluate in a sandbox on an internal surface, verify accessibility/reduced-motion behavior ourselves, and avoid production-critical adoption until a 1.0 or documented maintenance signal appears.