Nova Fixed Bars Laravel Package

Product Decisions This Supports

• Whether internal admin tooling gets roadmap budget at all. This package is pure UI chrome for Laravel Nova — pinning action bars so Save, Create, and Delete stay reachable on long forms and detail pages. Adopting it is a cheap, visible way to say "operator ergonomics count" without opening a design-system project. Deciding not to adopt is equally useful: internal tools stay at stock Nova until someone files a ticket, and that becomes an explicit prioritization call rather than an oversight.
• The real build-vs-buy frame: package vs. lift-the-CSS vs. do nothing. With 33 stars, zero dependents, a single maintainer, a January 2020 last release, and a NOASSERTION license, "buy" is the wrong mental model. The honest options are "lift ~40–60 lines of CSS into our own Nova::style() registration and own it" or "skip it." The package is best used as prior art and a reference implementation; the discovery work is reusable even if the dependency is not.
• Scoping where fixed chrome actually pays off. Tie adoption to workflows, not aesthetics: ops and support consoles where agents touch dozens of resources per shift (persistent controls cut back-navigation and mis-clicks); long, wide reconciliation and audit tables where column context and pagination matter; and smaller laptop/tablet viewports in field settings where vertical space is contested. That is the ticket language — not "the admin looks nicer."
• Forcing an explicit Nova version and upgrade-ownership answer. Nova ships a compiled front end; selectors like .sidebar and .content are incidental implementation detail, not a public API. Evaluating this package forces the team to state which Nova major we standardize on and who owns admin UI regression review on every bump — an answer the roadmap needs regardless of the outcome here.
• Setting a dependency-vetting bar. NOASSERTION is a decision input, not a footnote. For anything commercial or client-delivered it blocks adoption until legal classifies or waives it in writing. Surface it early and treat it as a precedent for how we vet all small front-end dependencies.
• Informing the "admin polish" backlog item. Whatever we decide, the validation work — does sticky chrome break keyboard focus order, 200% zoom, the mobile drawer, modal and dropdown stacking, print/PDF export — produces a reusable spec if we later invest in admin UX properly.

When to Consider This Package

Consider it only when all of these hold:

• You already run Laravel Nova with the private Composer repo configured. This is not an admin-framework choice; outside Nova it does nothing.
• The surface is internal only — staff, ops, back office — with no customer-facing or regulated-audit exposure.
• Legal has explicitly cleared or waived the NOASSERTION license, with a named owner for that call.
• The team can vendor, patch, or fork it in roughly a day. At this size, "we can own it" is the real bar, not "it installs cleanly."
• You want this specific behavior — pinned action bars, optionally a fixed sidebar/header — and are not trying to bootstrap a broader admin design system.
• You accept that a 2020 release against a moving UI framework is recurring re-validation cost, roughly half a day per Nova major, not a one-time install.

Look elsewhere — or lift the CSS instead of installing — when:

• You are on Nova 4.x/5.x or plan to upgrade within two quarters. An unmaintained front-end overlay against a moving admin UI is a tax on every bump.
• You need a support contract, CVE response, changelog, or any maintenance guarantee. There is no vendor, no SLA, no issue triage.
• Accessibility conformance matters. Fixed/sticky chrome regularly regresses focus order, scroll trapping, and zoom behavior, and no upstream maintainer is watching for that here.
• You want fixed sidebar and fixed navbar decided independently — the sidebar is usually the higher-value one for ops staff; a fixed navbar eats vertical space and is the likelier annoyance on a 13" laptop.
• You would be shipping to a client deliverable or commercially distributed product where the license question is unresolved.

If you proceed: pin an exact version (no caret range), gate the style behind config so it can be killed in one deploy, scope rules to desktop widths and let Nova own small screens, and validate with screenshot diffs at 375 / 768 / 1024 / 1440 px across dashboard, index, detail, create/edit, and modal screens.

How to Pitch It (Stakeholders)

To executives: This is a small, low-risk question with a disproportionate signal. Our internal admin surface is where ops staff spend hours per shift, and right now the primary actions scroll out of reach on long resources. We can improve that — but the package itself is a thin stylesheet that has not been touched since January 2020, has one maintainer, zero dependents, and an unclassified license. My recommendation is not to take the dependency. We reproduce the behavior ourselves in a day, register it through Nova's supported Nova::style() hook, gate it behind a config flag, and own the regression review on Nova upgrades. That gives us the operator benefit, avoids the license and maintenance questions entirely, and costs less than a formal design-system initiative. It also forces a useful conversation we owe ourselves anyway: which Nova version we standardize on, and who owns admin UI quality when we bump it.

To engineering: Treat this as a reference implementation, not a dependency. Read the service provider (it is essentially one Nova::style(...) call) and the stylesheet, then write our own ~40–60 lines with the dimensions tokenized in custom properties, every rule scoped under a body class we control, and a config switch to disable it in one deploy. Two independent toggles — fixed sidebar versus fixed navbar — not one. Let Nova's mobile drawer own widths under ~1024px. Watch the three failure modes that account for most of the pain: content offset when the sidebar leaves normal flow, z-index stacking against modals/dropdowns/toasts, and ancestor overflow: hidden or transform silently breaking position: fixed. Add print rules, verify keyboard focus order and 200% zoom, and ship with before/after screenshots and the validated Nova version in the PR. Never patch vendor/laravel/nova; it is overwritten on every update.