Improved structure of automation docs

Author: jaydrogers

docs/content/docs/3.framework-guides/1.laravel/1.automations.md

@@ -65,16 +65,18 @@ Once the database connection is confirmed, the script executes the appropriate m
 Set `AUTORUN_DEBUG=true` to see detailed connection attempt logs, which is helpful for troubleshooting connection issues.
 ::
 
+## Laravel Artisan commands
+Below is an overview of what Laravel Artisan commands do and how they can be configured.
 
-## php artisan storage:link
+### php artisan storage:link
 Creates a symbolic link from `public/storage` to `storage/app/public`.
 
 :u-button{to="https://laravel.com/docs/12.x/filesystem#the-public-disk" target="_blank" label="Read more about storage links" aria-label="Read more about storage links" size="md" color="primary" variant="outline"  trailing-icon="i-lucide-arrow-right" class="font-bold"}
 
-## php artisan migrate
+### php artisan migrate
 Before running migrations, we ensure the database is online and ready to accept connections. By default, we will wait 30 seconds before timing out.
 
-### Migration Modes
+#### Migration Modes
 You can control how migrations run using `AUTORUN_LARAVEL_MIGRATION_MODE`:
 
 | Mode | Description |
@@ -87,21 +89,21 @@ You can control how migrations run using `AUTORUN_LARAVEL_MIGRATION_MODE`:
 Using `fresh` or `refresh` modes will **drop all tables** in your database. Only use these in development or testing environments.
 ::
 
-### Force Flag
+#### Force Flag
 By default, migrations run with the `--force` flag to bypass production warnings. You can disable this by setting `AUTORUN_LARAVEL_MIGRATION_FORCE` to `false`.
 
-### Seeding
+#### Seeding
 You can automatically seed your database after migrations by setting `AUTORUN_LARAVEL_MIGRATION_SEED` to `true`. This adds the `--seed` flag to your migration command.
 
-### Specific Database Migrations
+#### Specific Database Migrations
 If you need to specify the exact database connection to use for migrations, you can set `AUTORUN_LARAVEL_MIGRATION_DATABASE` to the name of the database connection you want to use.
 
 | Use case | Description | Value |
 |----------|-------|-------------|
 | Single database | Run migrations on the `mysql` database connection. | `AUTORUN_LARAVEL_MIGRATION_DATABASE=mysql` |
 | Multiple databases | In the rare case you need to use multiple databases, you can provide a comma-delimited list of connection names (e.g., "mysql,pgsql"). | `AUTORUN_LARAVEL_MIGRATION_DATABASE=mysql,pgsql` |
 
-### Isolated Migrations
+#### Isolated Migrations
 You can enable the [`--isolated`](https://laravel.com/docs/12.x/migrations#running-migrations) flag by setting `AUTORUN_LARAVEL_MIGRATION_ISOLATION` to `true`, which will ensure no other containers are running a migration.
 
 **Special Notes for Isolated Migrations:**
@@ -111,7 +113,7 @@ You can enable the [`--isolated`](https://laravel.com/docs/12.x/migrations#runni
 
 :u-button{to="https://laravel.com/docs/12.x/migrations#running-migrations" target="_blank" label="Read more about migrations" aria-label="Read more about migrations" size="md" color="primary" variant="outline"  trailing-icon="i-lucide-arrow-right" class="font-bold"}
 
-## php artisan optimize
+### php artisan optimize
 Laravel comes with an artisan command called `optimize`, which will optimize the application by caching the configuration, routes, views, and events all in one command.
 
 You can disable any cache features by setting the corresponding environment variable to `false` (for example, `AUTORUN_LARAVEL_CONFIG_CACHE` would disable configuration caching).
@@ -122,22 +124,22 @@ It's possible to disable the `optimize` command by setting `AUTORUN_LARAVEL_OPTI
 
 :u-button{to="https://laravel.com/docs/12.x/deployment#optimization" target="_blank" label="Read more about optimizing Laravel" aria-label="Read more about optimizing Laravel" size="md" color="primary" variant="outline"  trailing-icon="i-lucide-arrow-right" class="font-bold"}
 
-## php artisan config:cache
+### php artisan config:cache
 This command caches all configuration files into a single file, which can then be quickly loaded by Laravel. Once the configuration is cache, the `.env` file will no longer be loaded.
 
 :u-button{to="https://laravel.com/docs/12.x/configuration#configuration-caching" target="_blank" label="Read more about configuration caching" aria-label="Read more about configuration caching" size="md" color="primary" variant="outline"  trailing-icon="i-lucide-arrow-right" class="font-bold"}
 
-## php artisan route:cache
+### php artisan route:cache
 This command caches the routes, dramatically decrease the time it takes to register all of your application's routes. After running this command, your cached routes file will be loaded on every request.
 
 :u-button{to="https://laravel.com/docs/12.x/routing#route-caching" target="_blank" label="Read more about route caching" aria-label="Read more about route caching" size="md" color="primary" variant="outline"  trailing-icon="i-lucide-arrow-right" class="font-bold"}
 
-## php artisan view:cache
+### php artisan view:cache
 This command caches all of the views in your application, which can greatly decrease the time it takes to render your views.
 
 :u-button{to="https://laravel.com/docs/12.x/views#optimizing-views" target="_blank" label="Read more about view caching" aria-label="Read more about view caching" size="md" color="primary" variant="outline"  trailing-icon="i-lucide-arrow-right" class="font-bold"}
 
-## php artisan event:cache
+### php artisan event:cache
 This command creates a manifest of all your application's events and listeners, which can greatly speed up the process of registering them with Laravel.
 
 :u-button{to="https://laravel.com/docs/12.x/events#event-discovery-in-production" target="_blank" label="Read more about event caching" aria-label="Read more about event caching" size="md" color="primary" variant="outline"  trailing-icon="i-lucide-arrow-right" class="font-bold"}