Getting Started

Installation

composer require rawilk/laravel-base
php artisan vendor:publish --provider="Rawilk\LaravelBase\LaravelBaseServiceProvider"

Publish the config file to customize default settings (e.g., config/laravel-base.php).

First Use Case Use the base Blade directive to include the package’s default layout:
```
@base
```
This renders the package’s default layout (if configured) with common UI elements like navigation, footer, and meta tags.
Key Components
- @base: Renders the default layout.
- @baseNav: Generates a responsive navigation bar.
- @baseFooter: Adds a footer section.
- @baseMeta: Injects SEO meta tags (title, description, etc.).

Implementation Patterns

Layout Integration Extend the package’s layout in your app’s resources/views/layouts/app.blade.php:
```
@extends('laravel-base::layouts.base')
@section('content')
    {{ $slot }}
@endsection
```

Dynamic Navigation Override the navigation in config/laravel-base.php:

'nav' => [
    'items' => [
        ['url' => '/', 'label' => 'Home'],
        ['url' => '/about', 'label' => 'About'],
    ],
],

Or use Blade components:

@baseNav(['items' => $customNavItems])

Meta Tags Pass dynamic meta data via view composers or Blade:

@baseMeta(['title' => 'Custom Page Title', 'description' => 'Custom description'])

Authentication Views Use the package’s auth components (if not using Fortify/Jetstream):
```
@auth
    @baseUserDropdown
@else
    @baseAuthLinks
@endauth
```

Customize Assets: Override CSS/JS in public/vendor/laravel-base by publishing assets:
```
php artisan vendor:publish --tag="laravel-base-assets"
```
Partial Overrides: Extend Blade components by copying them from vendor/rawilk/laravel-base/resources/views to your app’s resources/views/vendor/laravel-base.

Service Provider: Register custom views or macros in your app’s AppServiceProvider:

use Rawilk\LaravelBase\Facades\Base;

Base::macro('customComponent', function () {
    // Logic
});

Fortify/Jetstream Conflict
- The package includes auth components (e.g., @baseAuthLinks). If using Fortify/Jetstream, disable these features in config/laravel-base.php:
```
'auth' => [
    'enabled' => false,
],
```
- Or manually remove conflicting Blade directives.
Layout Overrides
- If @base doesn’t render as expected, ensure your layout extends laravel-base::layouts.base and includes @section('content').
- Debug by checking if the package’s views are published:
```
php artisan vendor:publish --tag="laravel-base-views"
```
Dynamic Data Binding
- The package relies on config arrays for navigation/meta tags. For dynamic data (e.g., user-specific nav items), use view composers or pass data via Blade:
```
@baseNav(['items' => $userNavItems])
```
Asset Loading
- Published assets (CSS/JS) may conflict with your app’s assets. Use unique class names or override the entire asset pipeline.

Check Published Views: Verify if views are published to resources/views/vendor/laravel-base.
Config Validation: Ensure config/laravel-base.php is properly merged (run php artisan config:clear if needed).
Blade Directives: Use @dump(Base::config()) to inspect the package’s runtime config.

Custom Components Extend the package by creating new Blade components in app/View/Components and register them in AppServiceProvider:
```
Base::component('customComponent', \App\View\Components\CustomComponent::class);
```

Macros Add custom Blade macros for reusable logic:

Blade::macro('baseAlert', function ($type, $message) {
    return Base::alert($type, $message);
});

Middleware Use the package’s middleware (e.g., Base\Middleware\CheckAuth) by adding it to your kernel.php:
```
protected $middleware = [
    // ...
    \Rawilk\LaravelBase\Middleware\CheckAuth::class,
];
```

Partial Adoption: Use only the components you need (e.g., @baseNav without @base).
Testing: Test Blade components in isolation using Laravel’s Blade::render():
```
$navHtml = Blade::render('@baseNav', ['items' => []]);
```

Fallbacks: Provide fallback content for optional components:

@baseNav
@else
    <nav>Fallback Navigation</nav>
@endbaseNav