Weave Code
Nova Fixed Bars Laravel Package
cloudcake/nova-fixed-bars
Laravel Nova package that keeps the admin panel's header and navigation bars fixed while you scroll, so key actions stay within reach on long resource tables, forms, and detail views. A lightweight UI enhancement that makes everyday Nova browsing smoother.
A Nova package to set the sidebar and/or header bar to a fixed position on the Nova UI.
Frequently asked questions about Nova Fixed Bars
- How do I install cloudcake/nova-fixed-bars?
- Install it with Composer using composer require cloudcake/nova-fixed-bars, then register the package's service provider in your application. The package is frontend-only, so there are no migrations to run and no routes to publish. Installation itself takes minutes; the real work is confirming the CSS still matches the Nova version you run.
- Which Laravel Nova versions does nova-fixed-bars support?
- The last release was January 2020, which places it in the Nova 2 era. Nova 3 changed the Tailwind configuration, and Nova 4 and 5 substantially reworked the layout shell, so the original selectors may not match current markup. Treat Nova 2 as the realistically supported target and test carefully on anything newer.
- Does Laravel Nova already have a fixed or sticky sidebar natively?
- Nova 4 and 5 reworked the layout shell and shipped a first-party sticky/fixed navigation capability. Before adding this package, check whether your Nova version's built-in navigation configuration already satisfies the requirement. On modern Nova, the package is likely redundant.
- How do I configure a fixed sidebar versus a fixed header bar?
- The package ships an optional config file, published through the usual Nova/Laravel publish command, that lets you choose a fixed sidebar, a fixed header, or both. Once published, toggle the relevant option and clear your compiled assets. Because it is purely CSS, the setting has no server-side effect.
- Is cloudcake/nova-fixed-bars still maintained?
- No. The last release dates to January 2020 and the repository has a very small footprint of roughly 33 stars, so there is effectively no community backstop to catch regressions. There is no indication of recent Nova 4 or Nova 5 compatibility work. Plan on owning any fixes yourself.
- What license does nova-fixed-bars use, and can I use it commercially?
- The repository's license is reported as NOASSERTION, meaning GitHub could not classify it, so the actual terms are unclear. Redistributing it or vendoring it into a client deliverable is a legal-review item rather than a formality. Confirm the license with the author before shipping it in anything commercial.
- Is nova-fixed-bars safe to use in production?
- It is a low-blast-radius package in that it adds no routes, migrations, queues, or server-side behavior; it only injects CSS through Nova's asset pipeline. The risk is visual, not functional: pinned positioning can clash with Nova's own sticky elements, dropdowns, and modals through z-index stacking and scroll container changes. Those regressions surface only on specific screens, which makes them hard to catch automatically.
- How is nova-fixed-bars implemented internally?
- It is a micro-package consisting of a thin service provider plus a published stylesheet registered through Nova's asset hooks or a custom tool. Its entire value is a handful of CSS selectors targeting Nova's internal markup and utility classes. That means correctness is coupled to Nova's compiled frontend rather than to any stable contract.
- What are the alternatives to nova-fixed-bars?
- For Nova 4 and 5, the first alternative is Nova's own built-in sticky navigation configuration. If that does not cover your case, reproduce the equivalent styles in your own Nova custom theme or asset bundle, which you control and can update alongside Nova upgrades. Adopting an unmaintained CSS-override package is usually the least durable option.
- How should I test nova-fixed-bars before and after Nova upgrades?
- Because breakage presents as visual regression rather than a hard error, automated PHP tests will not catch it. Use a manual QA checklist across resources, dashboards, settings, and custom tools, and consider screenshot or visual regression tests on those screens. Assign clear ownership for fixing positioning issues whenever Nova is upgraded.
Weaver
How can I help you explore Laravel packages today?