Nova Inspire Laravel Package

Getting Started

devtical/nova-inspire is a Laravel Nova card that surfaces rotating inspirational quotes/knowledge snippets on a Nova dashboard. v2.0.3 is a content-only release (a new "knowledge" topic), so nothing changes in the install path.

1. Install into an app that already has Nova installed and licensed:

   composer require devtical/nova-inspire
   

2. Register the card in app/Providers/NovaServiceProvider.php. Nova 4/5 style:

   public function cards()
   {
       return [
           new \Devtical\NovaInspire\NovaInspire(),
       ];
   }
   

   (Older Nova versions register cards in the cards() array passed to Nova::cards([...]) — same object, different location.)
3. Load /nova and confirm the card renders on the main dashboard.

Where to look first: the package's README.md for the exact card class name/namespace and any publishable config, then vendor/devtical/nova-inspire/src/ — it's a small package, and the quote/topic data lives in the repo (typically a PHP array or JSON file), which is the fastest way to see what v2.0.3's new "knowledge" topic actually contains.

First use case: a zero-config "quote of the day" panel on the admin dashboard — useful as a low-effort morale/onboarding touch for internal teams, with no database tables and no migrations.

Implementation Patterns

• Dashboard-scoped registration. Cards belong to dashboards, not resources. Register on the main dashboard for everyone, or on a custom dashboard (php artisan make:dashboard Team) so the card is visible only to specific user groups via canSee().
• Per-audience instances. Because the card is stateless and config-light, creating separate instances per dashboard is cheap — e.g. a "knowledge" flavoured card on an engineering dashboard and a general quotes card on the default dashboard.
• Rollout workflow. Add the dependency, register the card, then deploy. There are no migrations or scheduled jobs, so this slots cleanly into an existing release; the only cache concern is Nova's compiled assets (see below).
• Version pinning. Pin to ^2.0 rather than *. v2 was a major bump from v1 — if any project still runs v1, treat that upgrade separately and read the 2.0.0 changelog, not the 2.0.3 notes.
• Content refresh as a maintenance task. With 2.0.3 adding a topic, the practical upgrade pattern is: bump the constraint, run composer update devtical/nova-inspire, clear caches, and eyeball the dashboard. Content packages don't need test-suite changes; they need a visual check.
• Integration with internal tooling. If you want your own messaging (release notes, on-call rotation), don't fight the package — either fork/vendor the quote source or place a custom card alongside it. Mixing both is fine; the card is self-contained.

Gotchas and Tips

• "Card doesn't appear" is almost always registration, not the package. Verify the class is in the array returned by cards() (or Nova::cards()), that the file was actually autoloaded (composer dump-autoload), and that the user passes any canSee() check.
• Asset caching. Nova serves compiled JS/CSS. After installing or upgrading, run php artisan nova:publish and php artisan view:clear; a hard browser refresh is often needed before the card shows up.
• Upgrading from v1 to v2 is the real risk, not 2.0.3. The 2.0.x line is a major version — check the 2.0.0 release notes for namespace/config/registration changes. The 2.0.3 note ("add knowledge topic") is additive content and should be safe to take on its own.
• Content is bundled, so it's read-only at runtime. You generally can't add quotes via .env or a config file; check for a vendor:publish tag before assuming you can. If customization matters, publish the views (if exposed) or fork.
• No database footprint. Nothing to migrate, nothing to seed, nothing to back up — which also means no per-user state (no "don't show again", no seen-tracking) unless you build it.
• Dark mode / narrow viewports. Cards render inside Nova's grid; long quotes can overflow on small screens or look washed out in dark mode. Worth a quick check if your team uses dark mode daily.
• Debugging checklist: composer show devtical/nova-inspire (confirm the installed version is 2.0.3), confirm Nova version compatibility in the package's composer.json, check storage/logs/laravel.log for render exceptions, and temporarily replace the card with a bare new \Laravel\Nova\Card() to isolate whether the problem is the package or your dashboard.
• Extension points are limited by design. Treat this as a drop-in widget: for anything beyond display (analytics, click tracking, custom copy), write your own card rather than patching vendor code.