Product Decisions This Supports
- Internal admin UX investment: Row-click behavior in Nova's index is a small but high-frequency interaction. For support, ops, or finance teams living in an admin panel all day, shaving one click per record compounds into real time savings — this package is a concrete data point for whether "operator efficiency" belongs on the roadmap at all.
- Build vs. buy vs. vendor for admin tooling: This is a ~1-file customization wrapped in a package. The decision it actually informs is not "should we adopt this?" but "do we maintain a thin internal Nova extension layer, or do we chase community packages for every micro-interaction?" Given the package is archived with 3 stars and 0 dependents, the honest answer is: replicate the pattern internally.
- Feature scoping for resource-specific workflows: The underlying capability — route a row click to a detail view, a custom URL, an external system (e.g., the Stripe dashboard for an Order record), or a related resource — forces a useful product question: what is the primary action for this entity? That's a design decision worth making deliberately per resource rather than accepting Nova's default of "go to edit."
- Roadmap signal on admin maturity: An archived, single-purpose package with a high opportunity score indicates unmet demand in a niche (customizable Nova interactions) without a maintained supplier. If you're on Nova heavily, that's a signal to budget for in-house Nova tooling rather than relying on the ecosystem.
- Evaluation of "low-cost polish" bets: This is the kind of 1–2 developer-day change that improves perceived quality of an internal tool without touching the customer-facing product. Useful as a calibration item when prioritizing small UX wins against larger bets.
When to Consider This Package
Consider the pattern (not the dependency) when:
- You are already running Laravel Nova and have a resource where "edit" is the wrong default click target.
- Your operators repeatedly navigate to an external system or a read-only view and you want to cut a step.
- You have a small, capable Laravel team that can vendor ~100 lines of MIT-licensed code and own it.
Look elsewhere / do not adopt as a dependency when:
- Maintenance matters. It is archived, has 3 stars, and zero dependents. There is no upgrade path, no Nova 4/5 compatibility guarantee, and no security response. Depending on it is a liability, not a saving.
- You're not on Nova. Nova is a paid, first-party-adjacent product; if you're on Filament, Backpack, or a custom admin, this is irrelevant. Filament in particular has first-class table row action configuration.
- You need more than a click target. Modals, bulk action orchestration, custom index layouts, or permission-aware routing will outgrow this immediately.
- You have dependency governance. Any package review requiring active maintenance, a security owner, or a support contract will fail this one on the first pass.
- Nova now covers it. Before doing anything, verify the current Nova version doesn't already expose row-click configuration — the package is old enough that the gap may have closed.
Recommended posture: treat this repository as a reference implementation. Read the source, reimplement the behavior in your own app/Nova or a first-party nova-tools package, add tests, and pin it to your Nova version. Cost: under a day. Benefit: no abandoned dependency.
How to Pitch It (Stakeholders)
To executives: A small open-source utility that lets us change what happens when an admin clicks a row in our Laravel admin panel — currently it always opens the edit form, which isn't always what our support team wants. The package itself is abandoned, so we would not install it; instead we'd spend roughly one developer-day reimplementing the same behavior in-house under our own control. Low cost, low risk, modest but real time savings for the operators who use the admin daily. Recommend funding it as part of existing admin maintenance, not as a standalone initiative.
To engineering: Do not add marshmallow/nova-resource-click to composer.json. It's archived, unmaintained, 3 stars, zero dependents, and carries Nova version-compatibility risk for a feature that is a thin wrapper over row-click routing. Port the approach into a small internal Nova extension we own and test. If we find ourselves wanting three or more micro-customizations like this, that's the trigger to stand up a proper internal Nova tooling package rather than continuing to evaluate one-off community plugins.