Weave Code
Weaver
Helps Laravel developers discover, compare, and choose open-source packages. See popularity, security, maintainers, and scores at a glance to make better decisions.
Feedback
Share your thoughts, report bugs, or suggest improvements.
Subject
Message

Nova Resource Cards Laravel Package

formfeed-uk/nova-resource-cards

Nova Resource Cards replaces Laravel Nova's default resource index table with responsive card grids, letting you display records as configurable cards with images, badges, and custom fields for easier scanning of listings and search results.

View on GitHub
Deep Wiki
Context7

Product Decisions This Supports

  • Admin/back-office roadmap planning: Nova resource cards let you surface domain resources (orders, tickets, users) as glanceable cards on Nova dashboards. This release extends that to Dashboards and Lenses, meaning cards can now reflect scoped, pre-filtered views of data rather than only the default resource index — useful for role-based or workflow-based admin experiences.
  • Build vs. buy on internal tooling: Rather than building custom Nova cards (or bespoke admin panels) from scratch, this package covers the common "show me key records at a glance" pattern. Evaluating it is a cheap way to avoid a custom card build cycle for each new resource.
  • Feature prioritization signal: The 1.0.1 → 1.1.0 jump adds exactly one capability (Dashboard/Lens support). That tells you the maintainer is responsive but the surface area is deliberately narrow — plan for the package to cover card-style resource widgets, and do not assume it will grow into broader admin customization.
  • Use cases to validate against: operations dashboards per team, lens-scoped queues (e.g. "my open tickets"), executive summary cards on a Nova dashboard, and multi-tenant admin views where each card is scoped by a Nova lens.
  • Roadmap risk input: A pre-1.x/early-1.x package with a small contributor base is a dependency-risk item. Factor the cost of forking or replacing it into any roadmap commitment that depends on Nova dashboards.

When to Consider This Package

Consider it when:

  • Your admin surface is Laravel Nova, and you want resource data presented as cards on dashboards rather than only as index tables.
  • You need Lens-scoped cards — i.e. the card's contents should follow an existing Nova lens filter rather than duplicating filter logic.
  • You want to avoid writing and maintaining custom Nova card Vue/PHP components for each resource; the package abstracts the repetitive parts.
  • Your team is small and prefers configuration over custom front-end work.

Look elsewhere when:

  • You are not on Nova (this package is Nova-specific and provides no value outside it).
  • You need a mature, widely adopted component library with a long support history and large community — the release cadence and contributor concentration here suggest a smaller project; validate maintenance expectations before betting a roadmap on it.
  • Your card requirements are highly bespoke (custom charts, cross-resource aggregation, non-Nova data sources) — you will likely end up writing custom cards anyway.
  • You need guaranteed semantic-versioning stability across major Nova releases; pin versions and budget for upgrade work.

How to Pitch It (Stakeholders)

For executives: This is a small, low-cost Laravel Nova add-on that turns admin data into at-a-glance cards on dashboards. The new 1.1.0 release adds support for Nova Dashboards and Lenses, which means we can build role- and workflow-specific admin views (e.g. "my team's open items") without custom development for each one. It is an accelerator for internal tooling, not a customer-facing product dependency — the primary risk is that it is a small open-source project, so we should pin the version and treat it as replaceable.

For engineering: Version 1.1.0 adds Dashboard and Lens support (PR #2), letting cards render against a dashboard or lens context instead of only the default resource index. Adoption path is straightforward: install, register cards per resource, and point them at existing lenses. There are no breaking changes indicated in the 1.0.1 → 1.1.0 diff, so an upgrade is low-risk. Caveats: the project has a very small contributor base and a narrow scope, so expect to own the integration and be prepared to fork if Nova's card API shifts; pin the version in composer.json and add a smoke test around the dashboards that use it.

Recommendation: Adopt for internal admin dashboards where a Lens already expresses the filter we need. Do not adopt as a foundation for anything customer-facing or for card behavior that goes beyond Nova's resource/lens model.

Weaver

How can I help you explore Laravel packages today?

Conversation history is not saved when not logged in.
Prompt
Add packages to context
No packages found.
uni-method/symfony-lib
tacticmedia/scim-server-bundle
neika-ai/symfony-bundle
mattleads/agent-publishing-bundle
glavweb/framework-bundle
glavweb/extra-bundle
glavweb/api-bundle
glavweb/admin-bundle
adachsoft/api-version-bundle
elsayed85/laravel-api-exceptions
ouhssini/laravel-demo-mode
daworks/ncloud-outbound-mailer-driver
gp247/cms
ignibyte/aic-gates
nexa-merchant/blog
novasa/laravel-language-center
opencage/geocode
adolfoholzer/parameters
livenetworks/ln-starter
cgv/localized-resource