- What is matiux/dublin used for in Laravel applications?
- matiux/dublin adds Dublin Core metadata support to Laravel applications. It provides a simple API for defining and rendering standardized metadata tags for models, pages, and other resources. Use it when you need consistent, reusable metadata output rather than hand-writing meta tags in Blade templates.
- How do I install matiux/dublin with Composer?
- Install it with composer require matiux/dublin and let Laravel's package auto-discovery register the service provider. If the package ships publishable configuration, run the vendor:publish command documented in its README to tailor behaviour per project. Check the README for the exact provider, alias, and config tag names before wiring it into your app.
- Does matiux/dublin support Laravel auto-discovery?
- Yes. The package overview states that installation and auto-discovery follow Laravel's package conventions. That means Composer should register the service provider without manual bootstrap edits in a standard Laravel app. If you use package discovery disabled or a nonstandard skeleton, register the provider manually.
- How do I define and render Dublin Core metadata for a model or page?
- Use the package API to define metadata values for the resource, then render the resulting Dublin Core tags in your response. Dublin Core commonly covers elements such as title, creator, subject, description, publisher, date, type, format, identifier, source, language, relation, coverage, and rights. Keep definitions close to the model or page layer and render through a shared partial or helper so output stays consistent.
- Which Laravel and PHP versions does matiux/dublin support?
- The provided package context does not list exact Laravel or PHP version constraints. Check the package's composer.json require section and its Packagist release metadata before installing. The package follows Laravel package conventions and exposes a PSR-compatible, framework-agnostic core, but you should still verify compatibility with your app's Laravel and PHP versions.
- Can I use matiux/dublin outside of Laravel?
- Yes, the overview describes a framework-agnostic core that stays testable outside Laravel. The Laravel layer mainly adds service-provider bindings and publishable configuration. In plain PHP you can use the core metadata definition and rendering pieces directly, while skipping Laravel-specific integration.
- How do I test Dublin Core metadata output in my Laravel app?
- Write PHPUnit tests that define metadata and assert the rendered tags contain the expected Dublin Core element names and values. The framework-agnostic core can be tested without booting Laravel, which keeps unit tests fast. For integration coverage, use Laravel feature tests or Orchestra Testbench and assert escaping, ordering, and config-driven behaviour.
- Is matiux/dublin safe to use for production metadata?
- Rendering Dublin Core tags is a low-risk, read-only operation, so production concerns are mainly escaping, caching, and correct values. Ensure all metadata is escaped in HTML output and cache rendered fragments if you generate tags for many pages. Dublin Core complements but does not replace canonical tags, Open Graph, or JSON-LD, so use it alongside your broader SEO strategy.
- What are good alternatives to matiux/dublin for Laravel metadata?
- Alternatives include hand-written Blade partials or helpers, broader Laravel SEO/meta packages, and custom model metadata casts. If you specifically need Dublin Core, compare packages by their supported elements, rendering API, and Laravel version compatibility. For simple needs, a small internal helper may be easier to maintain than adding another dependency.
- How is matiux/dublin maintained and how can I extend it?
- The package provides clear contracts and service-provider bindings, so you can extend behaviour by binding custom implementations or overriding published configuration. Maintenance activity is not described in the provided context, and the repository is unknown, so check Packagist and the source repository for release history and issue activity before adopting it. Favour a tagged release and review the changelog for Laravel compatibility updates.