- Can I use flob-foundation-bundle in a Laravel application?
- No. flob-foundation-bundle is a Symfony2 bundle, not a Laravel package. Its Twig extensions, service definitions, and console commands rely on Symfony's bundle and dependency-injection model, which Laravel's service providers and Blade components do not resolve. There is no adapter layer, so you would need a rewrite rather than an install.
- Is florianbelhomme/flob-foundation-bundle still maintained?
- No, it is discontinued and archived. The last release was on 2016-10-27, roughly a decade without maintenance. Composer audit tools will flag it as abandoned, and no upstream security patches will ever be issued. Treat any code you take from it as a fork you own.
- What Laravel versions does flob-foundation-bundle support?
- None. The package targets Symfony 2.x-era components and PHP 5.x/7.0-era runtimes, so it does not declare support for any Laravel version. Composer resolution against Laravel 9, 10, or 11 and PHP 8.x will almost certainly fail. It is not a candidate for Laravel version compatibility testing.
- How do I install flob-foundation-bundle?
- You cannot install it meaningfully in a Laravel app. The historical Symfony install path is composer require florianbelhomme/flob-foundation-bundle plus bundle registration in AppKernel, which has no Laravel equivalent. On modern PHP the dependency constraints usually block installation outright. Do not add it to composer.json for a Laravel project.
- What does flob-foundation-bundle actually provide?
- It integrates Zurb Foundation into Symfony by shipping Foundation-oriented Twig templates, form themes, Twig extensions, service definitions, and console commands. The reusable value is mostly markup helpers for panels, alerts, grids, and form macros. Foundation's CSS and JavaScript themselves are freely available through npm and need no bundle.
- Are there Laravel alternatives for integrating Zurb Foundation?
- You do not need a Composer package to use Foundation in Laravel. Install Foundation via npm, import its SCSS and JS through Vite, and build any helper markup as Blade components or partials. If you want a packaged UI layer, evaluate maintained options like Tailwind CSS with Laravel Breeze or Jetstream, or Bootstrap-based Laravel presets instead.
- Is flob-foundation-bundle safe to use in production?
- No. It is archived, unmaintained since 2016, and pinned to Symfony 2.x and old PHP runtimes that are end-of-life. There are no security patches, no downstream dependents creating maintenance pressure, and its Foundation markup likely predates current Foundation releases. Adopting it means owning a fork with no upstream support.
- How do I migrate from flob-foundation-bundle to a modern Laravel front end?
- Clone the repository and inventory the Twig extensions and templates for Foundation patterns worth keeping, which is a small, bounded set. Rebuild those patterns as Blade components or partials, install Foundation or your chosen design system through npm, and bundle assets with Vite. Do not carry the Symfony bundle or its service wiring into the Laravel app.
- Why does composer require flob-foundation-bundle fail on PHP 8?
- The package's composer.json pins Symfony 2.x-era components and PHP 5.x/7.0-era constraints. Modern PHP 8.x and current Symfony or Laravel dependency trees conflict with those requirements, so Composer cannot resolve a compatible set. This is expected for an abandoned 2016 package, not a configuration mistake you can easily patch.
- What should I use instead of flob-foundation-bundle for a Symfony app?
- For Symfony, install Foundation via npm and wire it through Webpack Encore or AssetMapper, then write Twig components or macros for the markup patterns you need. Modern Symfony UX and Twig components cover much of what this bundle once provided. For Laravel, skip Symfony bundles entirely and use Blade components with npm/Vite-managed Foundation assets.