Download the PHP package matheusmarnt/scoutify without Composer

Scoutify

⌘K global search modal for Laravel — multi-model Livewire UI powered by Scout.

📘 Documentation: https://matheusmarnt.github.io/scoutify/

Drops a production-ready ⌘K search experience into any Laravel application. Register Eloquent models, choose a Scout driver, and ship a keyboard-triggered modal that queries multiple model types simultaneously, groups results by type, and persists recent search history to session.

Features

• Livewire modal — keyboard-triggered (⌘K / Ctrl+K) global search dialog
• Zero-config discovery — models under app/Models/ using Searchable are auto-detected at boot
• Grouped results — results organised by model type with section headers and color tokens
• Multiple drivers — Meilisearch, Algolia, Typesense, or Database
• Accent-insensitive highlight — diacritic-free queries (padrao) match and highlight accented text (Padrão) via NFD normalization
• Auto-discovered subtitles — models with description, subtitle, excerpt, summary, bio, or body attributes surface them as result subtitles automatically; HTML is sanitized to plain text before display, so CMS fields render cleanly without escaped tags
• Query hook — per-model globalSearchBuilder() for custom filters, scopes, or infix matching
• Recent searches — configurable history, persisted to session
• i18n — ships with pt_BR, en, and es translations
• Dark mode — full dark mode support out of the box
• WCAG AA — accessible markup with focus management and keyboard navigation
• Any blade-icons pack — globalSearchIcon() accepts any icon name from any Blade Icons pack installed via Composer (e.g. ri-*, tabler-*, mdi-*); fully-qualified names are auto-detected by matching against all registered pack prefixes and passed through as-is; short names fall back to the registered prefix (heroicon-o- by default; override via Scoutify::types()->iconPrefix() in a service provider)
• File preview & download — models implementing HasGlobalSearchPreview expose an inline file preview pane inside the modal. PDFs, images, and videos render natively; any other type falls back to an external-link/download button. Download is opt-in and dispatches a scoutify:download browser event you can handle with a single listener
• Tailwind v4 — utility classes inlined, override via the fluent theme API

Quick Start

This will:

1. Prompt for a Scout driver (meilisearch, algolia, or typesense)
2. Install the driver's Composer packages
3. Publish config/scoutify.php and config/scout.php
4. Set SCOUT_DRIVER in .env

Registering Models

Make your Eloquent models globally searchable:

The command discovers Eloquent models under app/Models/, prompts you to pick which to register (or pass --all), and automatically edits each chosen model file to:

1. Import Matheusmarnt\Scoutify\Concerns\Searchable and Matheusmarnt\Scoutify\Contracts\GloballySearchable
2. Add implements GloballySearchable to the class declaration
3. Insert use Searchable; as the first statement in the class body

The command then rebuilds the type manifest so models appear in the UI immediately.

The Searchable trait provides sensible defaults for every interface method. Override as needed:

Icon packs: globalSearchIcon() accepts any icon name supported by Blade Icons. Fully-qualified names are auto-detected by matching against all packs registered via Composer service providers — not just those declared in config/blade-icons.php. Install any pack and use its prefix directly:

Short names (e.g. user) get the registered prefix prepended (heroicon-o- by default). Override in a service provider:

globalSearchSubtitle() auto-discovery: if your model has a description, subtitle, excerpt, summary, bio, or body attribute, the trait returns it automatically — HTML is sanitized to plain text (tags stripped, entities decoded, whitespace collapsed) then truncated to 150 chars. Override only when you need custom logic or a different field.

Use --dry-run to preview edits without touching files:

Then import your models into the Scout index:

Add to your layout:

Modal placement: <livewire:scoutify::modal /> must live at the root of your layout, outside any collapsible or conditionally-rendered container (sidebar, drawer, off-canvas nav, etc.). Livewire does not initialise components inside collapsed containers — placing the modal inside a collapsed sidebar means it will not mount until the sidebar is opened, causing the trigger to appear broken. The trigger component (<x-scoutify::gs.trigger />) can go anywhere.

Customizing the Scout Query

Override globalSearchBuilder() on any model to apply custom filters, scopes, or driver-specific options:

Meilisearch note: Meilisearch uses word-boundary prefix search. Substrings that are not word-prefixes (e.g. "ano" inside "Mariano") return no results. If you need substring (infix) matching, override globalSearchBuilder() to configure Meilisearch's attributesToSearchOn or switch to the database driver which uses LIKE-based search.

Opening the Modal Programmatically

Any element can open Scoutify without the official trigger component.

Alpine (recommended):

Plain JS / any context:

Inside a Livewire component:

Do not use wire:click="$dispatch('scoutify:open')" on plain Blade elements — outside a Livewire component tree, Livewire.js never initialises those directives.

Visibility Gating (Authorization)

By default, Scoutify is secure-by-default:

• Guests: cannot see results (always denied).
• Authenticated users: can see results if they pass a registered policy check for view (e.g. Gate::check('view', $record)). If no policy exists for the model, authenticated users are allowed by default.

To customize this behavior per model, implement the HasGlobalSearchVisibility contract and use the fluent VisibilityRule builder:

Supported Rules

Use ->mode(VisibilityMode::All) to require all rules to pass (logical AND) instead of any (logical OR).

Spatie Integration: ->permission() and ->role() require spatie/laravel-permission. Scoutify detects it automatically and fails closed if the package is missing when these rules are used.

Global Configuration

Customize the default behavior in config/scoutify.php:

• secure (default): Guest denied, Auth checks gate if policy/gate exists, else allow.
• permissive: Everyone allowed.
• gate-only: Everyone (including guest if gate closure allows) must pass gate check; fails closed if gate/policy is missing.

File Preview & Download

Any model can expose an inline file preview pane inside the search modal by implementing HasGlobalSearchPreview:

How it works

• PDFs, images, and videos render inline inside the preview pane.
• Other types show a fallback with an external-link button.
• Authorization reuses the same GlobalSearchAuthorizer rules as search results — the record must be visible to the current user.
• Signed route (scoutify.preview.stream) is auto-registered. No manual route publishing needed.
• Temporary URLs — if the disk supports them (e.g. S3 with pre-signed URLs), Scoutify uses them directly; otherwise it streams through the signed route.
• Keyboard accessible — Tab / Shift+Tab cycle focus between the search input and the Preview / Download buttons on the active row. Enter on a focused button activates it without navigating to the record's route. Opening the preview auto-focuses the Back button; Esc closes the pane.

Download

Implement the download by listening to the scoutify:download browser event:

PreviewDto reference

Optional parameters: mime, filename, sizeBytes, view (custom Blade view), ttl (signed URL TTL in seconds, default 3600).

Commands

AI Assistance

Scoutify ships a two-tier AI documentation mechanism so any AI assistant can access current, version-pinned documentation and scaffold correct PHP code.

Layer 1 — static files (any AI client, zero install):

Layer 2 — MCP server (Claude Code, Cursor, Codex, Gemini, Windsurf, Copilot, Cline):

The MCP server exposes 8 tools: search_docs, get_page, list_pages, get_antipatterns, scaffold_searchable_model, scaffold_visibility_rule, scaffold_theme_config, validate_snippet.

→ Full AI integration guide

Upgrading

Moving from v1.x to v2.x requires updating your composer.json constraint and removing legacy config keys before running composer update. Skipping this order causes a RuntimeException crash in the post-update-cmd step.

→ v1.x → v2.0 upgrade guide

Documentation

• Installation guide — step-by-step setup, model registration, Tailwind config, customization
• Production deployment — per-driver production configuration (Meilisearch, Algolia, Typesense, Database)
• Upgrade guide — v1.x → v2.0 migration steps

Testing

Contributing

Please see CONTRIBUTING for details.

License

MIT — see LICENSE.