Tags
Tags give Capell one shared, multilingual, multi-site taxonomy for articles, pages, events, and other package records.
What Tags helps you do
Active Capell Membership access covers the curated Released catalogue and lets the account opt into Beta extensions after reviewing their risk.
Workflow screenshots
8 capturesTags give Capell one shared, multilingual, multi-site taxonomy for articles, pages, events, and other package records.
Editors organise content from a managed tag list with reusable inputs instead of fixed one-off categories.
Packages can opt supported models into the same tagging model without rebuilding relationship and form logic.
Use it when content needs flexible organisation that stays consistent across the site.
Review the documentation and screenshots on this page before enabling it on a production Capell site.
What changes on your site
Review the admin, public, data, scheduled, and command surfaces Tags adds when enabled.
- Taxonomy
- Tags
Install after you have checked the fit.
Confirm version compatibility, support, data access, migrations, retained data, and removal steps first. Then install the Composer package from the account that owns access.
-
01
Require the package
composer require capell-app/tags -
02
Register the extension
php artisan capell:extension:enable tags -
03
Clear schema cache
php artisan capell:admin:clear-schemas-cache
Evaluator scenarios
What to inspect in Tags
Switch the evaluation lens to see how different roles should assess this package before installing it.
'More like this' keeps finding real content — what to verify
Tag a set of related and unrelated pages, then inspect the related-content ranking. Items sharing more tags should rank higher, and taxonomy cleanup should change the recommendations predictably.
Read more Show less
Expected evidence: The related-content lookup counts shared tags across different content types and returns the closest matches, with no custom SQL of theirs to rot. Because everyone tags from one managed set, those connections hold up as the site grows instead of quietly decaying.
Choose a lighter option when: On a site of a few pages, discovery barely matters and this earns little. When content is small and site owners are happy linking things by hand, manual related links are perfectly fine.
Release and download evidence
- Total downloads
- 0
- Last downloaded
- No downloads yet
Version history
0 releasesNo package release history is published yet. Check the source and documentation before installing.
Before checkout
Know who owns access and what happens next
Payment, customer account ownership, site activation, and package access are separate steps. The checkout reference lets support trace a problem without moving the licence to another account.
Who processes the payment and taxes?
Lemon Squeezy hosts paid marketplace checkout and issues the tax receipt. Capell does not collect card details; it activates the matching marketplace licence after payment is confirmed.
Which account owns the licence?
The signed-in customer account that completes checkout owns the licence, receipt, support history, and future install access. Use the intended organisation account before paying.
How does the site receive package access?
The install flow connects the licence to the requesting site. Paid and private packages then use authenticated Composer access from the customer account that owns the licence.
What happens if checkout is cancelled or expires?
No licence is created until Lemon Squeezy confirms payment. After a cancellation or expired quote, return to the same marketplace listing and start a fresh checkout so price and package details are recalculated.
What should I do if access does not appear?
Keep the checkout reference from the page or receipt and contact support before trying another account. Support can trace the payment, customer account, licence, and connected site from that reference.
No approved reviews yet. Reviews from eligible customers appear here after moderation.
