Improved Documentation Search (#61)

* chore: (Improve documentation search for V3)

* fix: checks for mispelled words

* fix: mispelled words

* fix spaces and syntax

* Update multi-database-tenancy.blade.md

Co-authored-by: Samuel Stancl <samuel.stancl@gmail.com>

source/docs/v3/integrations/horizon.blade.md

@@ -4,11 +4,11 @@ extends: _layouts.documentation
 section: content
 ---
 
-# Laravel Horizon
+# Laravel Horizon {#laravel-horizon}
 
 Make sure your [queues]({{ $page->link('queues') }}) are configured correctly before using this.
 
-## Tags
+## Tags {#tags}
 
 You may add the current tenant's id to your job tags by defining a `tags` method on the class:
 

source/docs/v3/integrations/livewire.blade.md

@@ -4,7 +4,7 @@ extends: _layouts.documentation
 section: content
 ---
 
-# Livewire
+# Livewire {#livewire}
 
 Open the `config/livewire.php` file and change this:
 

source/docs/v3/integrations/nova.blade.md

@@ -4,7 +4,7 @@ extends: _layouts.documentation
 section: content
 ---
 
-# Laravel Nova
+# Laravel Nova {#laravel-nova}
 
 ## In the central app
 
@@ -12,7 +12,7 @@ If you wish to use Laravel Nova in the central application (to manage tenants),
 
 You can find the full Nova setup for managing tenants in the [SaaS boilerplate](/saas-boilerplate):
 
-## In the tenant app
+## In the tenant app {#in-the-tenant-app}
 
 To use Nova inside of the tenant part of your application, do the following:
 

source/docs/v3/integrations/passport.blade.md

@@ -4,7 +4,7 @@ extends: _layouts.documentation
 section: content
 ---
 
-# Laravel Passport
+# Laravel Passport {#laravel-passport}
 
 > If you just want to write an SPA, but don't need an API for some other use (e.g. mobile app), you can avoid a lot of the complexity of writing SPAs by using [Inertia.js](https://inertiajs.com/).
 
@@ -29,7 +29,7 @@ If you want to use the same keypair for all tenants, do the following.
 
 - Don't use `passport:install`, use just `passport:keys`. The install command creates keys & two clients. Instead of creating clients centrally, create `Client`s manually in your [tenant database seeder]({{ $page->link('configuration#seeder-params') }}).
 
-## **Tenant-specific keys**
+## **Tenant-specific keys** {#tenant-specific-keys}
 
 If you want to use a unique keypair for each tenant, do the following. (Note: The security benefit of doing this isn't probably that big, since you're likely already using the same `APP_KEY` for all tenants.)
 
@@ -47,7 +47,7 @@ There are multiple ways you can store & load tenant keys, but the most straightf
 
 And again, you need to create clients in your tenant database seeding process.
 
-## Using Passport in both the central & tenant app
+## Using Passport in both the central & tenant app {#using-passport-in-both-the-central-and-tenant-app}
 
 ![Passport for both central & tenant app](/assets/images/passport_universal.png)
 

source/docs/v3/integrations/spatie.blade.md

@@ -4,20 +4,20 @@ extends: _layouts.documentation
 section: content
 ---
 
-# Integration with Spatie packages
+# Integration with Spatie packages {#integration-with-spatie-packages}
 
-## **laravel-activitylog**
+## **laravel-activitylog** {#laravel-activitylog}
 
-### For the tenant app:
+### For the tenant app: {#for-the-tenant-app}
 
 - Set the `database_connection` key in `config/activitylog.php` to `null`. This makes activitylog use the default connection.
 - Publish the migrations and move them to `database/migrations/tenant`. (And, of course, don't forget to run `artisan tenants:migrate`.)
 
-### For the central app:
+### For the central app: {#for-the-central-app}
 
 - Set the `database_connection` key in `config/activitylog.php` to the name of your central database connection.
 
-## **laravel-permission**
+## **laravel-permission** {#laravel-permission}
 
 Install the package like usual, but publish the migrations and move them to `migrations/tenant`:
 

source/docs/v3/integrations/telescope.blade.md

@@ -4,7 +4,7 @@ extends: _layouts.documentation
 section: content
 ---
 
-# Laravel Telescope
+# Laravel Telescope {#laravel-telescope}
 
 Enable the the *Telescope tags* feature to have all Telescope requests tagged with the current tenant's id.