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 Menu Laravel Package

norman-huth/nova-menu

A Laravel Nova tool for creating and managing site menus from the Nova admin panel. Build hierarchical, drag-and-drop menus, link to Nova resources or custom URLs, and render them in your frontend with a simple API.

View on GitHub
Deep Wiki
Context7

📦 Archived. No longer maintained. See README for maintained alternatives.

Frequently asked questions about Nova Menu
What is norman-huth/nova-menu used for?
It is a Laravel Nova tool for creating and managing site menus from the Nova admin panel. It supports hierarchical drag-and-drop menus, links to Nova resources or custom URLs, and frontend rendering through a simple API. The package is archived and no longer maintained, so it is only relevant for existing Nova-based projects evaluating a menu admin tool.
Is norman-huth/nova-menu still maintained?
No. The repository is archived and the description explicitly says it is no longer maintained. The README points to maintained alternatives, which you should review before considering this package. There is no upstream support or compatibility patching path.
Does nova-menu work with Laravel Nova?
Yes, the package is built specifically as a Laravel Nova tool, so it depends on Nova's resource, auth, asset, and migration conventions. It is not intended for non-Nova Laravel applications. You must still verify compatibility against your exact Nova major version, Laravel version, and PHP version because the package is archived.
How do I install norman-huth/nova-menu with Composer?
Installation is Composer-based, but you should first confirm the correct package name because the repository and Composer identity appear as norman-huth/nova-menu versus Muetze42/nova-menu. Run the install only in a disposable sandbox and pin the last release. Then publish config, migrations, and assets as documented, and smoke-test menu CRUD, permissions, ordering, and rendering before any production use.
Which Laravel, PHP, and Nova versions does nova-menu support?
The provided context does not list exact version constraints, and the package is archived. Treat the last release as a snapshot rather than a maintained compatibility line. Check its Composer constraints and test it against your target Nova, Laravel, and PHP matrix, because future upgrades will be your responsibility.
Can I use nova-menu in a Laravel app without Nova?
No. This package is tightly coupled to Laravel Nova and is only relevant if your product is already committed to Nova. For a standard Laravel admin panel or a non-Nova stack, it is not a fit. You would need a different menu package or a simple database-backed custom implementation.
How do I render nova-menu menus in my frontend?
The package advertises frontend rendering through a simple API after menus are built in Nova. The exact API and rendering assumptions are not detailed in the provided context, so inspect the README and source before relying on them. Test rendering, caching, and localization in a sandbox and document the behavior your frontend depends on.
Does nova-menu support hierarchical drag-and-drop menus?
Yes. The overview describes building hierarchical, drag-and-drop menus from the Nova admin panel. It also supports linking menu items to Nova resources or custom URLs. Because the package is archived, validate the ordering and nesting behavior against your Nova version and add regression tests if you fork it.
What are the maintained alternatives to nova-menu?
The repository is archived and its README lists maintained alternatives, so start there rather than adopting this package. The context does not name those alternatives, so review the README directly. Evaluate any replacement for Nova version support, active maintenance, permissions, caching, and frontend rendering.
Is norman-huth/nova-menu safe for production use?
It carries high long-term risk because it is archived, has low adoption, zero dependents, and no upstream security or compatibility response. Production use would require an internal owner, a pinned fork, CI compatibility tests, and a documented exit path to a custom Nova tool or simple menu table. Do not treat it as a strategic platform dependency.
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.
dbravoan/dbcms-admin-theme-dbcms
dbravoan/dbcms-theme-db-cyber
dbravoan/dbcms-blocks-basic
dbravoan/dbcms-module-content-audit
dbravoan/dbcms-module-ai-assistant
paygate-to/paygate-php
padosoft/askmydocs-connector-base
defstudio/supercharged-carbon
bernskioldmedia/laravel-matomo
bernskioldmedia/laravel-harvest
bernskiold/laravel-data-scrubber
bernskiold/laravel-currency-converter
bernskiold/laravel-campaign-monitor
bernskioldmedia/laravel-autotranslate
siberfx/telegram-bot
roy-sandip/laravel-view-extended
gregsphotography/site-builder-core
roy-sandip/laravel-view
anodyne/blade-fluentui-icons
webx-ui/module-catalog-collections