Skip to main content
Capell home
Live demo
Released

Discovery Core

Give search and sitemap features the same list of public URLs.

Version
1.0.35
Released
10 November 2026
Licence
Free

Price Free

Check access and installation

Check your application before checkout

Outcome

What it solves

The problem

Developers building discovery features can end up duplicating public URL matching logic.

What your site gets

A site has shared discovery primitives available to packages that contribute public URLs.

Questions buyers ask

What information can packages contribute?
First-party packages can contribute scoped, indexable URLs to the shared registry.
Does this provide a discovery screen?
No admin or frontend surface is declared for this shared package.
How does matching remain consistent?
The package supplies deterministic text-matching primitives for discovery features.
Usage

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.

Included

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.

Licence Free
Install now
Review site impact

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.

Add this free package to your account, then review compatibility and site impact before installing it.

Open the Capell demo

This listing has no page of its own in the demo. Open the demo to see Capell running.

Installation impact

Before you install

Review the impact below before running the commands in a covered Capell application, starting with a non-production environment. Required dependencies are listed above.

Admin and public surfaces
Surface impact is not declared in this listing. Ask the publisher which administration and public screens or routes it adds.
Data and migrations
The manifest declares no package migrations. This does not establish that installation or runtime operations make no data changes. Uses package-local configuration and Capell metadata needed to enable the feature.
Background work
A complete jobs and scheduler assessment is not available here. Confirm background processing and worker requirements with the publisher.
Access controls
Access-control changes are not described here. Confirm the required roles and grants with the publisher.
Removal and retained data
A verified uninstall and retained-data assessment is not available here. Removing the Composer package does not establish that its data is deleted. Confirm cleanup, retention and dependencies with the publisher before removal.
  1. 01

    Require the package

    composer require capell-app/discovery-foundation
  2. 02

    Install the extension

    php artisan capell:extension-install capell-app/discovery-foundation
Release and review evidence
Maintenance

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.35 Nov 10, 2026
Recent activity
23 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.

Changelog

Release notes and maintenance evidence

Version history

Showing the 10 most recent of 23 approved releases
  1. v1.0.35
    Nov 10, 2026
    Release notes

    Full Changelog: https://github.com/capell-app/discovery-foundation/compare/v1.0.34...v1.0.35

  2. v1.0.34
    Nov 2, 2026
  3. v1.0.33
    Oct 28, 2026
  4. v1.0.32
    Oct 20, 2026
  5. v1.0.31
    Oct 17, 2026
  6. v1.0.30
    Oct 9, 2026
  7. v1.0.29
    Oct 9, 2026
  8. v1.0.28
    Oct 8, 2026
  9. v1.0.27
    Oct 8, 2026
  10. v1.0.26
    Oct 7, 2026
View all Discovery Core releases on GitHub (opens in a new tab)

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?

There is no self-service refund button. Email [email protected] within 14 days of purchase with the account email, the order or receipt reference, the package and your reason. Capell reviews the recorded purchase and, where approved, submits the refund through Lemon Squeezy. Read the Refund Policy

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.