- How do I install Laravel Themer in a Laravel application?
- Install the package with Composer using corwindev/laravel-themer, then let Laravel's package discovery register the service provider. After that, publish the package config so you can set your theme directory and default theme. No core application files need to be modified to get started.
- Does Laravel Themer support switching themes at runtime?
- Yes. The package is built around runtime theme switching through a simple facade or helper, so you can activate a different theme during a request rather than at boot time. That makes it practical to pick a theme per tenant, per domain, or per campaign without redeploying. The active theme then drives view and asset resolution for the rest of the request.
- How does Laravel Themer resolve views and assets for the active theme?
- It integrates with Laravel's view finder, so when a view is requested the package looks inside the active theme's directory first. Assets belong to the same self-contained theme folder, keeping styles, scripts, and templates together. This means you avoid scattering overrides across your resources directory.
- What happens if a themed view is missing?
- Laravel Themer falls back to your base application when a themed view does not exist. You can therefore override only the views a theme actually needs and rely on your default templates for everything else. This keeps themes small and makes partial themes safe to ship.
- Which Laravel versions does Laravel Themer support?
- The package targets modern Laravel applications and leans on the framework's view finder rather than custom compilation steps. Because version constraints live in the package's composer.json, check that file, or the Packagist page, for the exact Laravel and PHP ranges before upgrading a project. Running your test suite after any Laravel major upgrade is the quickest way to confirm compatibility.
- Can I configure per-theme settings and custom namespaces?
- Yes. The publishable config covers theme paths and defaults, and each theme can carry its own configuration alongside its views and assets. Custom namespaces are also supported, which helps when you want themed views registered under a specific hint. This is useful when several packages or modules need to resolve their own themed templates.
- Is Laravel Themer a good fit for multi-tenant and white-label apps?
- It is designed for exactly those cases: multi-tenant products, white-label builds, and seasonal or campaign-specific designs. Each tenant or brand maps to a theme directory, and switching the active theme at runtime changes what the user sees. Your base application stays untouched, which keeps maintenance predictable as the number of themes grows.
- How do I set or change the active theme?
- Use the package's facade or helper to activate a theme by name, typically early in the request such as in middleware or a service provider. Once active, the view finder and asset resolution follow that theme until it is changed again. The default theme from the config is used when nothing else is set.
- Where do theme files live and how do I publish the config?
- Themes live in a dedicated directory defined in the package configuration, with each theme holding its own views, assets, and optional config. Publish the config with Laravel's vendor publish command, then adjust the paths and default theme to match your project structure. Keeping the theme root outside your main resources folder makes it obvious which files are theme-specific.
- How can I test theme switching in my Laravel test suite?
- Activate a theme in the test setup, then assert that responses render the expected themed view or asset path. Feature tests can hit routes with different active themes and compare output, and you can assert fallback behaviour by requesting a view the theme deliberately omits. Because switching happens at runtime, no special environment is required beyond your normal Laravel testing setup.