- How do I install the filament-logo plugin in my Laravel application?
- Install it with Composer using composer require jeffersongoncalves/filament-logo:^3.0. The package uses Laravel package auto-discovery, so there is no build step, no npm, and no published assets to manage. After installation the logo renders automatically on the next page load without any further setup.
- Which Filament and PHP versions does filament-logo support?
- Version ^3.0 of the plugin targets Filament ^5.0 (release 3.0.2 pins filament/filament ^5.3), version ^2.0 targets Filament ^4.0, and version ^1.0 targets Filament ^3.0. All supported branches require PHP ^8.2. Because the constraint is tight, run composer show filament/filament first to confirm your installed Filament version actually resolves before starting the update.
- Do I need to register FilamentLogoPlugin::make() in my panel provider?
- The README states that zero configuration is required and shows only the Composer install command. Some internal notes reference a plugins => [FilamentLogoPlugin::make()] snippet, which is inconsistent with the documentation. Inspect the service provider of the installed version before committing to an install path, and confirm behaviour with a quick smoke test in your panel rather than trusting the docs.
- Where exactly does the Filament logo appear in the admin panel?
- The plugin mounts a single Blade partial on the PanelsRenderHook::TOPBAR_BEFORE render hook. In practice this means the Filament logo is displayed at the top of the panel for mobile viewports. Desktop rendering is left untouched, so no existing layout or topbar markup changes there.
- Can I change the logo image, size, or placement with this plugin?
- No. The package ships no config file, no published views, and no options — it renders the Filament logo, not your own branding. If you want your own asset, different sizing, or a different hook location, write the Blade partial and hook yourself; it is roughly a 10 to 40 line concern. The MIT license and small surface area mean you can also publish and vendor the view if you prefer to fork.
- Will filament-logo conflict with brandLogo() or a custom Filament theme?
- There is a real risk of duplicate branding. If your panel already sets brandLogo() or uses a custom theme that renders a logo, the mobile topbar may end up showing two logos. Check every panel in your application for existing brand configuration and visually diff the mobile topbar after installing.
- Does the plugin add migrations, config files, or published assets?
- No. It consists of a single Filament panel plugin — a service provider plus one Blade partial — with no migrations, no configuration file, no published assets, and no service bindings. Nothing touches your application database or storage. Because it is purely additive, removing it with composer require's counterpart, composer remove jeffersongoncalves/filament-logo, fully reverts the change.
- Is the logo image bundled with the package or loaded from an external URL?
- The README artwork is served from a raw.githubusercontent.com URL, so check whether the rendered Blade view follows the same pattern before you ship to production. An externally hosted asset introduces a runtime dependency on GitHub availability and can be blocked by strict content security policies. Read the partial to confirm; if it does hotlink, host the image locally instead.
- Is filament-logo safe to use in production given its low adoption?
- The code surface is tiny and the license is MIT, so the technical risk is low even though the project has around 5 stars, no dependents, and a single maintainer whose changelog is largely dependency bumps. The main operational risk is release cadence: a new Filament minor can require a plugin major, so you inherit the maintainer's schedule as a gate on your own upgrades. Treat it as a leaf dependency upgraded in lockstep with Filament, and keep the option to reimplement the partial in under an hour if maintenance stops.
- Should I use this plugin for a white-label or client-facing admin panel?
- Probably not without sign-off. The plugin renders the Filament logo, not your brand, which is a branding decision rather than a UX enhancement for a client-facing panel. If the goal is your own logo on mobile, this is the wrong starting point — write the TOPBAR_BEFORE hook yourself with your own asset. If the goal genuinely is Filament branding, install it and verify the response on mobile breakpoints.