Weave Code
Theme Bundle Laravel Package
liip/theme-bundle
LiipThemeBundle adds flexible theme support to Symfony apps. Define multiple themes with template and asset fallbacks, switch themes per request or environment, and reuse a default theme. It simplifies building branded, multi-theme sites while preserving Symfony’s standard rendering and asset workfl...
Provides theming support for Symfony bundles
Frequently asked questions about Theme Bundle
- Can I use liip/theme-bundle in a Laravel application?
- No. liip/theme-bundle is a Symfony bundle, not a framework-agnostic PHP library, and it hooks into Symfony's Bundle and Extension lifecycle, DI container compiler passes, kernel.request listeners, and Twig's loader chain. Laravel replaces those seams with service providers, middleware, and Blade, so there is no adapter layer to write around. The concepts are portable but the code is not.
- Does liip/theme-bundle support Laravel 10 or Laravel 11?
- There is no Laravel support in any release, including 1.7.0. Composer resolution will likely fail outright against Laravel 10 and 11's Symfony 6/7 components and modern Twig. The 1.7.0 release notes contain no dependency or constraint changes that would suggest otherwise.
- How do I install liip/theme-bundle?
- In a Symfony app you would run composer require liip/theme-bundle, register the bundle in the kernel, and define available and active themes in YAML configuration. None of those steps apply in Laravel, where there is no bundle registration step or Symfony kernel to hook into. Installation in a Laravel project is not a supported path.
- What does liip/theme-bundle actually do?
- It adds named theme registration, an ordered fallback chain to default templates, per-bundle template overriding, runtime theme switching via configuration or request detection, and unified template and asset path resolution. The value is in the fallback resolution semantics rather than any single feature. Those semantics can be reimplemented, but the implementation is Symfony-specific.
- Is there a Laravel equivalent of LiipThemeBundle?
- There is no direct Laravel equivalent with the same fallback resolution model. For most Laravel projects, per-tenant branding is a configuration plus asset-manifest problem rather than a theme-bundle problem. If you genuinely need multi-theme fallback, build a small internal package with a ThemeManager singleton, named themes, and an ordered view-path fallback chain.
- Is liip/theme-bundle still maintained?
- Version 1.7.0 exists after a multi-year gap, but it contains only two bug fixes, a Twig deprecation notice, and CI build-matrix tweaks. There is no supported-versions statement, no security policy, no published release cadence, and no named maintainer with an ongoing mandate evidenced in the notes. Treat a single maintenance cut as incidental rather than a revived stewardship commitment.
- Which PHP and Symfony versions does liip/theme-bundle support?
- The project publishes no explicit supported-versions policy. The 1.7.0 release notes show no PHP 8.x work and no movement toward Symfony 6 or 7 component versions, and the Twig fix addresses a warning rather than a runtime matrix. Assume the code is unverified on modern PHP until a spike proves otherwise.
- Can I use liip/theme-bundle with Blade templates?
- No. The bundle resolves theme-specific template and asset paths by hooking into Twig's loader chain, and Blade has no equivalent extension point that the bundle targets. Installing twigbridge would not solve the deeper mismatch, because the bundle still depends on Symfony bundle lifecycle and kernel event integration. Porting the resolution logic into a Blade view-path resolver is the realistic route.
- Should I fork liip/theme-bundle for a Laravel project?
- Forking is technically permitted under the MIT license, but you would own 100 percent of the maintenance and CVE response for code with no institutional backer watching it. Zero dependents is a signal that the ecosystem has moved on. Building an internal Laravel package that ports the concept gives you the same behavior with code you control.
- What are the alternatives to liip/theme-bundle for multi-theme Laravel sites?
- The practical alternative is a purpose-built internal package rather than a Composer dependency. Extract the bundle's resolution semantics, meaning theme locator, fallback ordering, and override precedence, into a short design note, then implement a ThemeManager bound as a singleton with named themes, ordered view paths, and asset resolution. If the real requirement is only per-tenant branding, configuration plus an asset manifest is simpler and safer.
Weaver
How can I help you explore Laravel packages today?