Weave Code
Core Laravel Package
contao-thememanager/core
Contao ThemeManager is a lightweight, forward-thinking CSS component-first framework for Contao. Leveraging flexbox and custom properties, it provides modular theme components, a flexible design base, and a solid foundation for modern, maintainable websites built with Contao.
Contao ThemeManager is a lightweight, forward-thinking CSS component-first framework for Contao, built on flexbox and custom properties. It lets you assemble themes from reusable components while keeping output lean and fully customizable.
- Component-first CSS architecture for reusable theme building blocks
- Built on flexbox and CSS custom properties for flexible styling
- Manageable via the Contao backend theme workflow
- Extensible structure maintained by oveleon
- Lightweight, modern output without framework bloat
Frequently asked questions about Core
- Can I install contao-thememanager/core in a Laravel app via Composer?
- Composer will pull the package and its Contao dependencies into a Laravel project, but it will not produce a working theme manager. The bundle has no Laravel service provider, no config publishing, and no illuminate/* dependency, so nothing registers or renders without the Contao kernel. Treat it as a Contao CMS bundle, not a Laravel package.
- Is contao-thememanager/core a Laravel package?
- No. It is a Contao CMS bundle that ships a CSS component framework, an scssphp-based asset compiler, and deep backend integrations such as DCA palettes, backend modules, and template hooks. Contao 5 is Symfony-based, so its runtime assumptions are Symfony HttpKernel plus the Contao Framework, not Illuminate. There is no Laravel bridge.
- What Laravel versions are supported by contao-thememanager/core?
- None. The package is not versioned against Laravel and has no Laravel integration layer. Its only overlap with a typical Laravel stack is PHP 8.3 and some transitively shared Symfony components. If you need Laravel version compatibility, this package is not a candidate.
- What PHP and Contao versions does contao-thememanager/core require?
- The package targets Contao 4.13 and ^5.3, and release 2.4.0 raised the PHP floor to ^8.3. Release 2.3.0 dropped Contao 4.13 entirely and removed backward-compatibility layers, so version pinning matters. Check the changelog before committing because the upgrade path has been aggressive.
- How do I install and configure contao-thememanager/core for Contao CMS?
- Install it into a Contao 4.13 or ^5.3 project with Composer, then run the Contao install tool or database update and configure the theme through the Contao backend. The value is delivered through Contao backend UI panels and dynamic StyleManager options, not through a headless API or Laravel config files. It is tightly coupled to sibling Oveleon packages such as contao-config-driver-bundle, contao-theme-compiler-bundle, and contao-component-style-manager.
- Why does composer require contao-thememanager/core not register anything in Laravel?
- Because the package has no Laravel auto-discovery, service provider, facade, or publishable configuration. Its runtime depends on the Contao Framework and Symfony HttpKernel, and its features are wired through Contao DCA palettes, backend modules, and template hooks. Without a Contao kernel, there is nothing for Laravel to boot or render.
- Is contao-thememanager/core AGPL-3.0 safe for a commercial SaaS?
- AGPL-3.0 is the dominant technical risk here, and it is a legal review item rather than an engineering footnote. The network-use clause means operating a modified version as part of a hosted service can trigger source-disclosure obligations for the combined work. Many teams treat this as a blocker for embedding in a commercial product; it is acceptable mainly for internal tools or fully open-sourced applications.
- How can I reuse contao-thememanager/core CSS components or design tokens in Laravel with Vite?
- Only the artifact layer is portable: compiled CSS, CSS custom properties, the flexbox grid, generated icon fonts, and dynamic background-image generation. One realistic shape is a sidecar Contao instance running ThemeManager as a CSS factory, exporting compiled assets or design tokens into a Laravel Vite build. The cheaper option is extraction by reference only: read the source for the custom-property naming scheme and component taxonomy, then hand-author a token layer in Laravel. There is no path where composer require into Laravel yields a working theme manager.
- Is contao-thememanager/core actively maintained and what is the bus factor?
- Maintenance is single-vendor through Oveleon, a commercial agency funded by sponsorship, with roughly 6 stars and 0 dependents in the context provided. There is no independent downstream ecosystem to absorb abandonment, and the changelog shows aggressive major releases including a v1 to v2 upgrade explicitly marked not recommended. Documentation is German and explicitly work in progress, so English onboarding cost is real.
- What are good alternatives to contao-thememanager/core for Laravel theme management?
- For Laravel, use Laravel's Vite pipeline with Tailwind CSS or plain CSS custom properties, plus a design-token layer and a component library. Those give you reusable components and maintainable customization without a Contao runtime or AGPL obligations. If you specifically need a CMS-backed theme manager, run it in Contao or choose a Laravel-native CMS package instead of forcing this bundle into Laravel.
Weaver
How can I help you explore Laravel packages today?