- What does markrassamni/nova-resource-landing-page do?
- It adds configurable landing pages to Laravel Nova resources. Instead of sending users straight to a Nova data table, it can show an overview screen with cards, links, and quick actions for a resource that represents a single record. It also adds a navigation link directly to that record's landing page.
- How do I install markrassamni/nova-resource-landing-page?
- Install it with Composer using composer require markrassamni/nova-resource-landing-page. In a standard Laravel package, the service provider should be auto-discovered; if not, register the package service provider manually. After installation, review the repository for any publishable views, config, or asset steps before enabling it on a Nova resource.
- Which Laravel and Nova versions are supported?
- The v3.0.0 release is described as updating the package view to match Laravel Nova v3.4.1. The provided context does not list exact Laravel, PHP, or Nova version constraints, so check the package composer.json and README before adoption. For production, pin a version that matches your Nova release and test it in staging first.
- How do I configure a Nova resource to use a landing page?
- The package is intended to add a landing page link for a Nova resource that has only one record. Configuration is handled per resource according to the package's documentation. Because the README excerpt is not available here, inspect the repository for the exact resource method, config keys, or view registration required.
- Is this package a Nova card, tool, field, or resource?
- Based on the description, it is a Nova resource UI integration that adds a navigation link and landing page view, not a field or standalone resource type. The release note specifically mentions a view update for Nova v3.4.1. Confirm the exact package surface in the source before planning integration work.
- Can I use it with a Nova resource that has multiple records?
- The package description focuses on showing a link directly to the only record of a resource, so it is best suited to singleton-style resources. If your resource has multiple records, a landing page that targets one record is probably not the right fit. Use Nova's standard resource index or build a custom overview for those cases.
- Can I customize the landing page view or add quick actions?
- The package centers on a Nova view that renders the landing page, so customization generally means overriding or extending that view. The blurb mentions cards, links, and quick actions, which suggests the overview is designed to be extended. Check whether views or assets are publishable, and document any overrides because Nova upgrades can affect rendering.
- What breaking changes are in version 3.0.0?
- The release note only states that the view was updated to match Nova v3.4.1. A major version usually signals breaking changes, but the provided note does not describe them. Inspect the changelog, source diff, and composer constraints before upgrading, and test against your exact Nova version.
- How should I test this package before using it in production?
- Test in a staging Laravel and Nova environment that matches production versions. Verify the navigation link, landing page rendering, single-record behavior, published assets, and any custom Nova view overrides. Also confirm a rollback path by pinning the previous package version before rolling out to an internal admin surface.
- What alternatives exist to nova-resource-landing-page?
- You can use Nova's built-in resource index and detail views, custom Nova cards or tools, or a custom resource view if you need an overview screen. If you do not need Nova-specific integration, a standard Laravel controller and Blade view may be simpler. Choose an alternative if your resource has multiple records or if you need a documented compatibility matrix.