Discovery Foundation
Give search and sitemap features the same list of public URLs.
- Version
- 1.0.32
- Released
- 20 October 2026
- Licence
- Free
Price Free
Check access and installationOn this page
-
Price and access
Review the price, licence and availability before deciding what to adopt.
-
Your workflow
Read how the package is used and what your application needs to provide.
-
Capabilities
See which jobs this extension supports and which parts it adds to your site.
-
Project fit
Decide what this removes from your workload and what your application still needs to supply.
-
Installation
Check the setup steps before adding the package to a project.
-
Release evidence
Review the available release, maintenance and package-review information.
Check your application before checkout
Use it in your project
This supporting package collects published, indexable URLs for discovery packages. Install it through the features that need a shared view of what visitors can find.
Picture it on your site
For a sitemap or discovery integration, decide which published URLs belong in the public inventory and evaluate the consuming package that uses it. Check a representative page in each relevant site and language. This supporting layer supplies shared URL knowledge; the visible discovery workflow belongs to the feature installed above it.
No workflow evidence published yet
No workflow screenshots are published. Use the demo or documentation to understand the extension before installing.
Help people find your content
- Register public URLs within their site context.
- Match discovery requests against the shared URL registry.
Is this right for your project?
Help a reader complete a task
Start with the phrases and pages a visitor needs, not a dashboard score. Check that published content is discoverable, that its title and description make sense in context, and that the destination answers the question. Search and SEO tooling can support those tasks, but it does not write the content strategy or guarantee a ranking. Your team still decides what deserves to be published.
Check the public result
Use a known published page and an unpublished comparison to test the supported output. Include a moved URL, an alternative language or an empty result where that applies to your project. Review the actual response or generated document, not only the editor settings. Any external search account, index or crawler has its own setup and refresh behaviour to account for.
Marketplace listings can describe install impact and data access.
This installs as a Composer package. Check its removal guidance and retained-data policy before uninstalling it.
Paid checkout adds access to the purchasing account after payment. Add a free package to your account, then review compatibility and site impact before installing it.
Explore the available extensions on the demo site.
Before you install
Run the commands below in your Capell application. Required dependencies are listed above. After installing a theme, select it for your site in Admin.
-
01
Require the package
composer require capell-app/discovery-foundation -
02
Install the extension
php artisan capell:extension-install capell-app/discovery-foundation
Release and review evidence
Release activity stays visible
These dates come from approved package releases, so you can see the release trail before installing.
- Latest approved release
- v1.0.32 Oct 20, 2026
- Recent activity
- 20 approved releases in the last 12 months
Access follows the account that owns the extension. Review the release trail and verification evidence here before installing.
Release notes and maintenance evidence
- Total downloads
- 0
- Last downloaded
- No downloads yet
Version history
10 releases-
v1.0.32Oct 20, 2026 -
v1.0.31Oct 17, 2026 -
v1.0.30Oct 9, 2026 -
v1.0.29Oct 9, 2026 -
v1.0.28Oct 8, 2026 -
v1.0.27Oct 8, 2026 -
v1.0.26Oct 7, 2026 -
v1.0.25Oct 4, 2026 -
v1.0.24Oct 1, 2026 -
v1.0.23Sep 29, 2026
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 is the seller and hosts paid marketplace checkout. Any VAT due is calculated and added by Lemon Squeezy at checkout, and Lemon Squeezy 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 Capell licence, support history, and future install access. Capell surfaces a link to the tax receipt issued by Lemon Squeezy. 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.
How do I request a refund?
Use the order link on the Lemon Squeezy receipt and request the refund through the Lemon Squeezy order receipt. If the receipt or order link is unavailable, contact Capell support so the payment and access record can be traced.
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.