Filament Navigation Enhanced Laravel Package

Product Decisions This Supports

• Build vs. buy for admin-panel navigation. This package occupies the "navigation ergonomics" slot in a Filament panel: item grouping, labels, and per-item visibility. v1.0.4 shows the scope is presentation and visibility wiring, not a full CMS-style menu system — which is the right scope for most internal tools and helps you decide whether to own that code or rent it.
• Feature/roadmap input on permissioned UI. The 403 fix is the useful signal here: hidden items were still rendering and dead-ending users on forbidden pages. If your roadmap includes role- or plan-gated navigation (multi-tenant panels, tiered customer portals, RBAC-driven admin surfaces), treat "invisible means not rendered" as an explicit acceptance criterion in your own specs — this release shows it's a real, easy-to-miss failure mode.
• Upgrade-cost budgeting for the admin surface. The label fix ships a fallback to the previous slot behavior and required no composer.json constraint change. That's a concrete data point for roadmap planning: patch upgrades of this dependency are low-friction and don't force you to pin or fork during a Filament minor bump.
• Vendor-health / dependency tracking. Two fixes in one patch, both responsive to an upstream Filament 5.10.2 change, is evidence of active maintenance. That supports keeping it in the dependency set rather than internalizing the component.
• Use cases to validate before committing: multi-panel apps (separate nav per panel), per-role sidebar variations, and any place where a menu entry must disappear rather than error out.

When to Consider This Package

Consider it when:

• You're on Filament 5.x and your sidebar needs exceed what the stock panel offers — conditional visibility, custom labels, nested/child items, multiple panels with divergent nav.
• You want navigation changes to be code-defined in the panel provider (reviewable in PRs, diffable) rather than edited in a database by admins.
• You need role- or permission-gated menu entries and want hidden items to be genuinely absent from the DOM, not just visually suppressed.
• You value a maintainer who tracks Filament point releases and preserves backward compatibility across 5.x minors.

Look elsewhere or build in-house when:

• You need DB-managed, editor-owned menus with draft/publish, revisions, or audit history — that's a different product category.
• You're on Filament 3.x/4.x, or you can't yet confirm 5.x support in composer.json; the release notes only speak to 5.x behavior.
• You have a hard policy against third-party packages in the admin surface, or your sidebar needs are trivial enough that a dozen lines in the panel provider suffice.
• You need guarantees the maintainer can't offer — the evidence base here is a single patch release; there's no signal yet on long-term support commitments, security response, or a stable 1.x API contract. Ask for release cadence and issue-response history before standardizing on it.
• Note on this release specifically: v1.0.4 is a patch with no new features, no deprecations, and no breaking changes. It is not a reason to adopt; it's a reason not to defer an upgrade if you're already on the package.

How to Pitch It (Stakeholders)

For executives: This is a small, actively maintained add-on for our admin interface that lets us tailor the sidebar navigation per team, per role, and per customer tier. The latest update is maintenance, not new scope — it fixes two defects: menu items we'd marked as hidden could still be clicked and dumped users onto a "permission denied" page, and item labels briefly disappeared on a newer version of our UI framework. Both are fixed, the upgrade is drop-in with no dependency changes, and it requires no engineering sprint. Net: continued low-cost polish on an internal tool, no added risk.

For engineering: Patch release v1.0.4, no API changes, no composer.json constraint change required. Two fixes: (1) items with ->visible(false) / ->hidden() are no longer emitted as child items — previously they rendered and clicking through produced a 403, so this closes an authorization-UX gap; (2) labels restored on Filament 5.10.2+, which passes navigation labels via a dedicated label prop — the component now prefers the prop and falls back to the slot, so behavior on earlier 5.x is unchanged. Recommend a routine version bump and a quick smoke test of any role-gated nav entries.