Nova Help Laravel Package

Product Decisions This Supports

• Admin UX investment: Adding contextual help inside Laravel Nova reduces reliance on external docs and support tickets for internal operators.
• Build vs. buy: A small, single-purpose package is cheaper than building and maintaining custom help tooling in your admin panel.
• Upgrade planning: v3.0.0 is a breaking release that requires Nova 5, so the decision to adopt is now tied directly to your Nova major-version roadmap.
• Feature scoping: Use this when the need is lightweight in-app guidance, not a full knowledge base or CMS.

When to Consider This Package

• Consider it if you are already on Laravel Nova 5 and want a minimal-footprint way to surface help content or documentation links to Nova users.
• Consider it if your admin users need contextual help without leaving Nova, and you do not want to maintain custom Nova components.
• Look elsewhere if you are on Nova 4 or earlier; v3.0.0 will not support your environment.
• Look elsewhere if you need authoring workflows, searchable help centers, analytics, or role-based documentation; this package is intentionally small.
• Treat the v3.0.0 upgrade as a paired decision with your Nova 5 migration, not as an isolated package bump.

How to Pitch It (Stakeholders)

For executives: This is a low-cost admin experience improvement that can reduce internal support load by putting help where operators already work. The main strategic point is that the latest version requires Nova 5, so adopting it should be sequenced with the Nova upgrade rather than treated as a standalone tool decision.

For engineering: v3.0.0 is a breaking release: it drops older Nova support and requires Nova 5, with a rebuild focused on minimal footprint. Adopt only after confirming Nova 5 compatibility across the admin stack. The package remains narrow in scope, so the integration effort should be small, but the Nova 5 dependency is the gating factor.