Getting Started

Install the package with Composer, publish its config and migrations, then run php artisan migrate. Check the package service provider for route/view registration and the default config for table names and block types.
First place to look: the page/block model and the search implementation. The v0.3.1 fix affects the database page search, so confirm which version you are on before relying on case-insensitive block search.
Minimal first use case: create a page record containing one or more text blocks (stored as JSON), render it through the package’s Blade view or API, then use the built-in search to find a block by a mixed-case term. On MariaDB, test with a term like “browse” against a block containing “Browse” to verify the fix.

Implementation Patterns

Store page content as structured blocks in a JSON column and render blocks through the package’s block resolver or your own Blade partials. Keep block type names stable so search and rendering stay in sync.
Use the page search as the basis for an admin content filter or a public site search. Wrap it in a controller action or model scope, and add pagination if you expose it to end users.
Integrate with existing routes by binding the package’s page model to your route model binding, or by writing a thin controller that calls the package’s search and render methods.
For custom block types, extend the package’s block registry/resolver rather than editing vendor views. Keep custom searchable text in the same JSON structure the package expects, or override the search query to include your own fields.
In tests, assert search behaviour with mixed-case queries. A feature test that creates a page with “Browse” and searches for “browse” is a cheap regression guard for the v0.3.1 fix.

MariaDB stores JSON columns with a case-sensitive collation, which is why the pre-v0.3.1 search missed “browse” when the block said “Browse”. Upgrade to v0.3.1 or later, or wrap your own search comparisons in LOWER() if you maintain a custom query.
JSON column searches are not the same as full-text search. For large page sets, expect table scans; add a generated column or a dedicated search index if search volume grows.
When debugging search results, log the generated SQL with DB::listen() and check whether the comparison is case-sensitive on your database driver. The same query can behave differently on MySQL, MariaDB, and PostgreSQL.
Publish the package views and config before customising. Overriding vendor files directly makes future upgrades harder, especially for a package still on a 0.x release line.
Check the package’s migration assumptions on MariaDB: JSON support, column collation, and index limits vary by version. Run the migrations on a staging database that matches production before deploying.
The search fix is narrow; it does not change the storage format or public API. If you had worked around the bug with a custom lower-case search, you can likely remove that workaround after upgrading, but keep a test to confirm.