- What is madeyourday/contao-rocksolid-custom-elements?
- It is a Contao extension from RockSolid Themes for creating your own custom content elements through declarative configuration. You install it with Composer and use the English or German documentation to build and manage tailored elements in a Contao site. It is not a Laravel package, so Laravel teams should treat it as part of a Contao or hybrid Contao-Laravel architecture.
- How do I install RockSolid Custom Elements with Composer?
- Run composer require madeyourday/contao-rocksolid-custom-elements in a Contao project. The package depends on Contao 4.9+ or Contao 5.x, so confirm your Contao version before installing. After installation, follow the RockSolid Themes English or German documentation to configure and manage custom elements.
- Is this package compatible with Laravel?
- There is no native Laravel support; the package has a hard dependency on Contao 4.9+ or 5.x. In a Laravel stack you would need a bridge, API layer, or hybrid architecture rather than expecting Eloquent models and Laravel routing to manage the elements. The release notes do not introduce Laravel compatibility or resolve Contao-Laravel backend integration gaps.
- Which Contao versions does RockSolid Custom Elements support?
- The package supports Contao 4.9+ and Contao 5.x, and recent work includes a fix for widget compatibility with Contao 5.7 (#190). That fix confirms ongoing Contao 5.x alignment but does not add Laravel-specific backend support. Always check the current release notes before upgrading a production Contao site.
- Can I use RockSolid Custom Elements with Laravel Blade or Livewire?
- No, RockSolid Custom Elements is built around Contao's backend and Twig rendering rather than Laravel Blade or Livewire. Using it with Livewire or Inertia would require replacing or bridging Contao's backend behavior, which the package does not provide. For Laravel-native admin experiences, a headless Contao API or a separate Laravel admin panel is more viable.
- How does RockSolid Custom Elements handle Twig templates in a Laravel stack?
- Twig support remains robust, but in Laravel you still need something like laravel-twig-bridge for frontend rendering. Backend-specific Twig logic such as BackendTemplate will still need mocking or replacement in a Laravel context. This makes Twig a workable frontend path only if your team accepts a split Contao-Laravel rendering model.
- What are the risks of adding this Contao extension to a Laravel project?
- Integration risk is high because custom elements still rely on Contao's tl_content data model, backend routing, session and state handling, and asset bundles. Laravel's Eloquent ORM, admin routing, and Vite or Mix pipeline do not map cleanly to those Contao conventions. A wrapper or hybrid setup remains significant upfront work, and this release does not reduce that risk.
- How should I test a Laravel app that uses RockSolid Custom Elements?
- Cross-stack testing complexity persists because you need to verify Contao element behavior and Laravel integration separately. Test the Contao side for element configuration and rendering, then test the Laravel side through API contracts or mocked Twig output. The package does not introduce new testing tools or Laravel-specific integrations.
- Does RockSolid Custom Elements work with Laravel Nova or Filament admin panels?
- No, RockSolid Custom Elements does not integrate with Laravel Nova or Filament. Contao's backend routing and tl_content palettes remain incompatible with Laravel admin systems, and the package does not close that abstraction gap. You would need a custom admin panel, a headless Contao approach, or a separate Contao backend.
- Should I fork RockSolid Custom Elements for Laravel support or use alternatives?
- Forking for Laravel support would diverge from upstream Contao updates and increase maintenance risk, especially as Contao 5.x Symfony changes continue. Laravel-native alternatives such as Livewire, Filament, or Nova are better fits for custom content management if you do not need Contao's specific element system. If Contao content is required, a headless API bridge is usually safer than a fork.