- What does nibri10/nova-grid actually do?
- It is a Laravel Nova package that adds a responsive grid or card layout so resources can be displayed and arranged as visual cards or multi-column field groups instead of Nova's default single-column table and form flow. Published descriptions vary between a card grid for the index view and a grid field wrapper for create/update screens, so confirm the real wrapper class and namespace inside the repository before planning around it. It is purely a presentation-layer package: it does not touch domain logic, persistence, authorization rules, or API surfaces. The realistic worst-case failure is a broken admin form, not a broken application.
- Which Laravel Nova versions does nova-grid support?
- Treat it as a Nova 3.x-only package. The last release was 2021-07-15, which makes Nova 4 and Nova 5 incompatibility near-certain because those majors changed the field and component internals. Check the laravel/nova constraint in the package's composer.json before installing anything. If a Nova 4 or 5 upgrade is on your roadmap, plan to unwrap the grids and fall back to native field width helpers as part of that migration rather than discovering the breakage later.
- How do I install and configure nova-grid in a Nova resource?
- Installation is a standard composer require followed by wrapping fields in the package's grid call inside your resource's fields() method. The real effort is verification, not installation: confirm the exact namespace and wrapper class, and check whether the service provider publishes views or assets, since missing assets is the most common cause of an installed package that renders nothing. Also determine whether the integration is a Field or NovaElement subclass that swaps a component or a view override, because that decision affects how Nova's normal field pipeline runs.
- Is nova-grid still maintained and safe to use in production?
- Signals are weak: a single maintainer, a last release in July 2021, roughly 23 stars, zero downstream dependents, no CI, and no test suite. That means nobody else in the ecosystem is surfacing breakage, and your team would be the first to exercise edge cases. For an internal back-office tool the blast radius is small, but adding it as a Composer dependency puts it on your at-risk register. The safer pattern is to copy the layout logic into an internal base resource class or trait you control.
- Can I fork or vendor nova-grid into my own codebase?
- Yes. The package is Apache-2.0 licensed, which is permissive enough to vendor the code under an internal namespace as long as you credit upstream. Because the layout logic is only a few dozen lines, copying it into an internal trait or resource base class is a credible one-day estimate. Forking is essentially copying with extra ceremony, and depending on the abandoned upstream only makes sense if you are permanently pinned to Nova 3.
- Do Nova's built-in halfWidth(), fullWidth(), and field panels make nova-grid unnecessary?
- Often, yes. Nova's native ->halfWidth() and ->fullWidth() helpers plus field panels close a meaningful part of the multi-column gap without any third-party code. Price that option first, since it removes maintenance risk entirely and keeps you on the supported upgrade path. Only reach for nova-grid if you have a measured editing bottleneck, such as ops staff repeatedly editing records with 20 or more fields, that the native helpers genuinely cannot solve.
- Will validation, authorization, and dependsOn conditional fields still work inside a grid?
- That depends entirely on how the package integrates with Nova. A Field or NovaElement subclass that swaps a component keeps validation, authorization, dependsOn, and persistence running through Nova's normal path, while a view override risks bypassing parts of it. Test an invalid submit explicitly to confirm errors still anchor to the correct field inside the grid. Also watch for onlyOn filters and conditional fields leaving empty cells, because the grid does not reflow when a field disappears.
- Does nova-grid support thumbnails and image galleries?
- The overview advertises thumbnail and image support for gallery-style resources, which is the strongest use case for a card layout. Whether it works in practice depends on your fields being renderable in a card context, so verify against a real resource rather than the description. Complex field types such as File, Markdown or Trix, KeyValue, and BelongsTo search-selects commonly render badly in narrow grid cells. Test those specific fields before rolling the layout out broadly.
- Does the grid layout work on mobile and with screen readers?
- The package claims responsive behavior from mobile to wide desktop, but there is no accessibility story in the repository. Multi-column forms commonly degrade screen-reader flow and mobile usability, especially when labels and inputs get visually separated. Check keyboard tab order and screen-reader announcements on a real resource before shipping it to staff who rely on assistive technology. If accessibility is a hard requirement, native Nova layout helpers are the lower-risk choice.
- What should I verify before adopting nova-grid, and what breaks on a Nova upgrade?
- Before any branch work, confirm the real namespace and wrapper class, whether the service provider publishes views and assets, and whether the integration is a field subclass or a view override. Then check the composer.json version constraints against your current Nova major and confirm your PHP and Laravel matrix. On a Nova 4 or 5 upgrade, expect to unwrap the grids and replace them with native width helpers, so design that fallback in from the start. Finally, decide who takes named ownership of the fork if you vendor it.