Nova Fixed Bars Laravel Package

Product Decisions This Supports

• Admin UX quick-win triage. This package solves one narrow, tangible complaint — "I lose the nav/header when I scroll long resource tables and forms." That makes it a candidate for a small, self-contained ticket rather than a roadmap item, and gives you a clean example of how to separate table-stakes polish (cheap, do it) from differentiating work (needs a business case).
• Build vs. buy vs. fork. The functionality is a handful of CSS/layout rules. The real decision this package forces is not "should we have sticky nav" but "do we take an unmaintained third-party dependency for a 30-line cosmetic change, or vendor the pattern into our own Nova tool / Nova::style() hook?" Framing it that way is reusable for every small Nova add-on your team proposes.
• Platform bet on Nova itself. Last release 2020-01-11 and 33 stars is a decay signal for the Nova 2/3 customization ecosystem. If your admin roadmap depends on a stack of packages like this, that's evidence for the "keep customizing Nova vs. migrate to a first-party-built admin (or a more actively maintained panel)" decision — worth logging even if you never install this package.
• Compliance/vendor intake policy. The NOASSERTION license is a concrete test case for your OSS intake rule: can a package with no explicit grant enter a commercial codebase, especially one shipped to clients or white-labeled? Deciding this once saves repeated debates.
• Use cases worth scoping: ops/data-entry teams working through long index tables, multi-step resource forms, and small laptop screens where vertical space is fought over. Low opportunity score (0.38) says: no strategic upside, no revenue lever — treat as hygiene.

When to Consider This Package

Adopt (or, more accurately, vendor) it when:

• You are pinned to Nova 3.x with no Nova 4 upgrade in the next two quarters — the frontend was rewritten (Vue 3 / Inertia) in Nova 4, and header/sidebar markup changed, so this package is very likely a no-op or a layout hazard there.
• The admin is internal-only, so a cosmetic regression after a Nova upgrade is an annoyance, not a customer-facing incident.
• Ops users have explicitly asked for persistent navigation and your team has no spare frontend capacity.
• You are willing to copy the CSS into your own tooling rather than depend on the package — this is the realistic mode given its age.

Look elsewhere when:

• You are on Nova 4+, or plan to be. Verify before spending any time; assume incompatible until proven otherwise.
• The license cannot be clarified. NOASSERTION means no explicit grant; if you redistribute the admin or ship source to clients, legal must clear it first, and the cost of that conversation likely exceeds the value.
• You need more than cosmetics — responsive/collapsible mobile nav, grouped navigation, branded theming, focus management and keyboard accessibility with a sticky header. Those want a small custom Nova tool or theme, not a 2020 package.
• You already have a custom tool scaffold or design system; 20–40 lines of CSS is cheaper to own than a dependency with no maintainer.
• Accessibility is a hard requirement for the admin surface. Sticky headers change scroll and focus behavior, and no one is going to fix that here.

How to Pitch It (Stakeholders)

For executives: A free, tiny UI tweak for the internal admin — keeps navigation visible while staff scroll long tables and forms. Expected benefit is modest efficiency for ops users, not a customer-facing feature. Cost is roughly half an engineer-day including compatibility and license checks, and it is fully reversible. The caveats are material: the package has had no release since January 2020, has a trivial install base (~33 stars), and carries an unclear license. Recommendation: do not add it as a standing dependency; use it as a reference implementation and copy the few CSS rules into our own Nova customization if the admin UX request is prioritized. This keeps the benefit, removes the maintenance and legal exposure, and avoids a precedent of depending on abandoned packages.

For engineering: One composer require plus a config publish on Nova 3.x — but confirm the supported Nova version first, since Nova 4's rewrite almost certainly invalidates it. Check the repository's license file before anything lands on main (NOASSERTION on the registry). Plan on forking or, preferably, reimplementing the sticky sidebar/header as a small Nova::style() addition or a custom tool so it survives Nova upgrades and matches our branding. Treat the opportunity score (0.38) as confirmation that this is a pattern to absorb, not a library to adopt.