Weave Code
Twill Metadata Laravel Package
cwsdigital/twill-metadata
A Twill CMS package that adds configurable SEO metadata fields to your modules, letting editors manage page titles, descriptions, and Open Graph tags from the admin UI, plus Blade helpers to render the resulting meta tags in your front end.
SEO Metadata Package for Twill CMS
Frequently asked questions about Twill Metadata
- How do I install cwsdigital/twill-metadata in a Laravel Twill project?
- Install the package with Composer, then publish its migrations and configuration files. Run the migrations, add the package trait or relation to each Twill-managed model you want to enrich, and register the metadata fields in the relevant Twill form definitions. Confirm the package version constraints match your Laravel and Twill versions before deploying.
- Does cwsdigital/twill-metadata support Laravel 11?
- Version 1.4.1 includes changes that force metadata columns to be nullable, which targets Laravel 11 compatibility. For existing Laravel 10 installations, verify whether the fix shipped as a new migration or as an edit to the original migration, because in-place edits are not applied to already-installed databases. Run a schema diff after upgrading and add a manual ALTER TABLE migration if needed. Also confirm that your Twill version supports Laravel 11, since Twill is the tighter compatibility constraint.
- Is Laravel 12 supported by cwsdigital/twill-metadata?
- Laravel 12 support is not confirmed in the available package information. Version 1.4.1 is focused on Laravel 11 enablement, so check the repository composer constraints and upstream release notes before assuming Laravel 12 compatibility. If you need Laravel 12, treat it as unverified until the maintainers explicitly add support.
- What Twill versions are compatible with this SEO metadata package?
- The package is built specifically for Twill CMS and assumes Twill's form and repository conventions. The exact supported Twill version matrix is not stated in the provided overview, so review the package composer.json and the upstream repository before upgrading. Because Twill is the tighter constraint, confirm Twill compatibility first when planning a Laravel upgrade.
- How do I add SEO fields to a Twill module with cwsdigital/twill-metadata?
- Add the package trait or relation to your Twill-managed model, then register the metadata fields in that module's Twill form definition. Editors can then manage page titles, descriptions, and Open Graph tags from the Twill admin UI. Use the package Blade helpers to render the stored metadata in your front-end layout.
- Why are my metadata columns not nullable after upgrading to Laravel 11?
- Version 1.4.1 forces the metadata columns to be nullable for Laravel 11 compatibility, but existing installations may not receive that change if the original migration file was edited in place. Fresh installs get the correct schema automatically, while upgraded databases need a schema diff check. If the columns are still non-nullable, write and review a manual ALTER TABLE migration before deploying.
- What is the repository abstraction change in cwsdigital/twill-metadata v1.4.1?
- The v1.4.1 release changes the repository behaviour to depend on abstractions rather than concrete implementations. That is directionally good for testability and for swapping storage behaviour, but it does not necessarily change the package public API. Verify whether new interfaces need service container bindings and check any code that subclasses or type-hints the concrete repository class before bumping in production.
- How do I render SEO metadata tags in Blade with cwsdigital/twill-metadata?
- The package provides Blade helpers that render the stored metadata as meta tags for your front end. Include those helpers in the head section of your layout so titles, descriptions, and Open Graph tags are output consistently. Check the package README or source for the exact helper names and expected arguments in your installed version.
- Is cwsdigital/twill-metadata safe to use in production?
- The package is a small, focused Twill add-on with low overall technical risk, but two caveats matter for production. Confirm that the Laravel 11 nullable-column fix is applied to your existing database, and verify that the repository abstraction refactor does not break any local subclassing or type hints. Pin to ^1.4, run your test suite plus a metadata read/write smoke test, and promote through staging before production.
- How is cwsdigital/twill-metadata maintained and what are the alternatives?
- The package is maintained by cwsdigital, a small agency, with a modest contributor base and a low-bus-factor risk to consider. Pin to ^1.4 and review each upstream release and Twill or Laravel version change. Alternatives include building custom Twill metadata fields in your application or using a broader SEO package, but this package is a focused option when you already run Twill and want configurable metadata fields with Blade rendering.
Weaver
How can I help you explore Laravel packages today?