Default Theme Laravel Package

Getting Started

Minimal Setup

1. Installation Add the package via Composer (if still functional):

   composer require c2is/bigfoot-default-theme
   

   Register the bundle in config/app.php under providers:

   C2is\BigfootDefaultTheme\BigfootDefaultThemeBundle::class,
   

2. First Use Case

   • Publish the default assets (if available) via:

     php artisan vendor:publish --provider="C2is\BigfootDefaultTheme\BigfootDefaultThemeBundle" --tag=assets
     

   • Integrate the theme’s base template (e.g., base.html.twig) into your Laravel app’s views.
   • Override default variables in config/bigfoot.php (if config exists).

Implementation Patterns

Workflow Integration

1. Template Inheritance Extend the theme’s base template (e.g., base.html.twig) in your app’s resources/views/layouts/app.blade.php:

   {% extends 'BigfootDefaultTheme::base.html.twig' %}
   {% block title %}{{ config('app.name') }}{% endblock %}
   

2. Asset Management

   • Use the theme’s CSS/JS paths (if documented) in Blade:

     <link href="{{ asset('vendor/bigfoot-default-theme/css/style.css') }}" rel="stylesheet">
     

   • Override assets via public/vendor/bigfoot-default-theme/ or publish custom assets.

3. Configuration

   • Merge theme defaults with your app’s config (e.g., colors, logos) in config/bigfoot.php:

     'theme' => [
         'primary_color' => '#3498db',
         'logo' => asset('images/custom-logo.png'),
     ],
     

4. Dynamic Content Blocks

   • Define reusable blocks in the theme (e.g., header, footer) and override them in your views:

     {% block header %}
         {{ include('partials.custom-header') }}
     {% endblock %}
     

Gotchas and Tips

Pitfalls

1. Outdated Dependencies

   • The package was last updated in 2014—test thoroughly for compatibility with modern Laravel (8+/9+) and PHP (8.0+).
   • Workaround: Fork the repo and update dependencies (e.g., Twig, Symfony components) manually.

2. Missing Documentation

   • No clear API or configuration structure exists. Inspect:
     • src/Resources/views/ for templates.
     • src/DependencyInjection/ for bundle logic.
   • Tip: Use php artisan config:clear if config changes aren’t reflecting.

3. Asset Path Assumptions

   • Hardcoded asset paths (e.g., /vendor/bigfoot-default-theme/) may break in custom setups.
   • Fix: Override paths in web.php or use mix/vite to republish assets.

4. Twig vs. Blade Conflicts

   • The theme uses Twig syntax. If your app relies on Blade:
     • Wrap Twig blocks in Blade directives:

       @php echo $__env->make('BigfootDefaultTheme::partial', ['name' => 'header'])->render() @endphp
       

     • Or use a package like laravel-twig-bridge for hybrid support.

Debugging Tips

• Template Overrides: Use {{ dump(_context) }} in Twig templates to inspect available variables.
• Asset Loading: Check if assets are published to public/vendor/ or debug with:

  php artisan vendor:publish --tag=assets --force
  

• Configuration: Dump the merged config:

  dd(config('bigfoot')); // If config key exists
  

Extension Points

1. Custom Templates

   • Override any template by placing a file in resources/views/vendor/bigfoot-default-theme/ with the same name (e.g., header.html.twig).

2. Theme Variables

   • Extend the theme’s context by passing data to templates:

     // In a controller
     return view('BigfootDefaultTheme::page', ['custom_var' => 'value']);
     

3. Event Listeners

   • If the bundle dispatches events (undocumented), listen in EventServiceProvider:

     protected $listen = [
         'bigfoot.theme.ready' => [
             \App\Listeners\CustomizeTheme::class,
         ],
     ];
     

4. Fork and Modify

   • For long-term use, fork the repo and:
     • Update to Laravel’s service container (e.g., replace Kernel with Application).
     • Replace Twig with Blade or use a modern templating engine.