- Can I use druidvav/page-metadata-bundle in Laravel?
- No, it is not a Laravel package; it is a Symfony bundle for page metadata. Using it in Laravel would require a wrapper or fork to bridge Symfony EventDispatcher, Twig rendering, dependency injection, and metadata concepts into Laravel's ecosystem. Laravel-native packages or middleware are lower effort for most applications.
- Does this package support Laravel 10 or 11?
- There is no declared Laravel version support. The package requirements are PHP 7.4 or later, Symfony 5, 6, or 7, and Twig 2.7 or later. Laravel integration would be custom and would not follow Laravel package auto-discovery.
- How do I install druidvav/page-metadata-bundle?
- Install it with composer require druidvav/page-metadata-bundle. In Symfony projects without Flex, register the bundle in config/bundles.php. In Laravel, Composer can download it, but Laravel will not auto-register a Symfony bundle as a service provider.
- What does page_meta() render and where do I call it?
- page_meta() renders the title, standard meta tags, canonical link, Open Graph and Twitter tags, and structured data. page_breadcrumbs() renders breadcrumbs separately in the page body. They are Twig functions, so a Laravel port would need a Blade directive, view composer, or custom renderer.
- How do I configure base_url for canonical URLs and structured data?
- base_url is required and should be the canonical site root used to turn relative metadata paths into absolute URLs. Values with or without a trailing slash are accepted; the bundle strips trailing slashes before storing the value. Missing or empty values are rejected, and absolute URIs are left unchanged.
- Can I use this package with Blade instead of Twig?
- No, the bundle is built around Twig; page_meta() and page_breadcrumbs() are Twig functions and Twig 2.7 or later is required. Using Blade would mean rewriting the rendering logic or building a custom renderer or view composer. That is one of the main integration costs for Laravel.
- Can I use only the Open Graph or JSON-LD features?
- Many configuration sections are optional, such as canonical, opengraph, breadcrumbs, and structured_data. You can enable or disable structured data and configure nodes, but the bundle is tightly coupled to Symfony and Twig. Extracting just Open Graph or JSON-LD logic would likely require rewriting it as a Laravel package or service.
- Is druidvav/page-metadata-bundle maintained and safe for production?
- The assessment flags it as abandoned, with the last release in 2020 and no community. That creates maintenance and compatibility risk for production, especially in Laravel where the ecosystem changes quickly. Prefer a maintained Laravel alternative unless you are prepared to fork and test the bundle.
- What Laravel alternatives should I use for SEO metadata?
- For Laravel SEO metadata, spatie/laravel-seo-tools is the commonly cited maintained option in the assessment. You can also use Blade directives, middleware, view composers, or response macros for dynamic metadata and API headers. Manual implementations may be simpler than adapting a Symfony bundle.
- How would I test a Laravel integration of this Symfony bundle?
- Testing would need to cover cross-framework differences such as Symfony HttpFoundation versus Illuminate Http, Twig versus Blade, and event-driven metadata versus Laravel middleware. You would need unit and integration tests for route-based metadata, canonical URL resolution, and rendered tags. Because the bundle is abandoned, a fork should include regression tests before production use.