Search by

capell-app / site-discovery

capell-app

Make every published Capell page discoverable — automatic XML sitemaps with index sharding, an HTML sitemap, and the canonical public-URL registry that powers the whole Search & SEO bundle.

v1.0.52 2026-11-10 12:16 UTC

README

What It Does

Site Discovery builds a canonical public-URL registry plus XML and HTML sitemap output from published, indexable Capell content.

  • Price and availability: Check current availability and price on the Capell Marketplace listing.
  • Licence: Check the licence terms on the Capell Marketplace listing.
  • Requires: PHP ^8.4, capell-app/admin ^1.0.66, capell-app/core ^1.0.76, capell-app/discovery-foundation ^1.0, capell-app/frontend ^1.0.
  • Install: composer require capell-app/site-discovery.

Admins can inspect which public URLs are indexable and covered by generated outputs. Search engines and other crawlers receive current sitemap routes as content changes.

Who It Is For

For developers: URL and discovery-output contracts let packages contribute public records while shared Actions handle deduplication, indexability, sitemap quality, and change notifications.

For teams: Teams can see whether published pages are being offered to crawlers and correct missing or hidden URLs before discovery suffers.

Quick Start

  1. Install the package: composer require capell-app/site-discovery.
  2. Open the package admin surface at /admin/pages and confirm Site Discovery is available.

Configure

  • Configuration files: config/capell-site-discovery.php.
  • Commands: php artisan capell:xml-sitemap.

Limits And Pitfalls

  • Install the required Capell packages at the versions in composer.json: capell-app/admin ^1.0.66, capell-app/core ^1.0.76, capell-app/discovery-foundation ^1.0, capell-app/frontend ^1.0.
  • Review middleware, throttling, signatures, and public-output safety in routes/web.php before exposing routes.
  • Keep the host Laravel scheduler running so package-registered schedules can execute: capell:xml-sitemap --incremental (manifest declared).
  • Keep public Blade and cached HTML free of authoring markers, model IDs, permissions, signed editor URLs, and lazy database queries.
  • Custom write integrations must preserve invalidation for site-discovery cache tags.

Screens And Workflow

Page resource sitemap action

Site resource sitemap action

  • Page resource sitemap action (admin).
  • Site resource sitemap action (admin).
  • Sitemap generation tool (admin).
  • Public HTML sitemap page (frontend).
  • Generated XML sitemap output (frontend).
  • Public URL Registry repair queue (admin).
  • Public URL Registry row details (admin).
  • Page resource sitemap action with admin sidebar menu open (admin).

Install Impact

  • Required packages: capell-app/admin, capell-app/core, capell-app/discovery-foundation, capell-app/frontend.
  • Admin navigation: declares admin-page: PublicUrlRegistryPageContribution; each Filament page or resource controls its own navigation visibility.
  • Admin/editor extensions: none declared.
  • Permissions: View:PublicUrlRegistryPage.
  • Public routes: loads routes/web.php; registers SiteDiscoveryFrontendRoutesContribution.
  • Database changes: no package migrations declared.
  • Config: config/capell-site-discovery.php.
  • Settings: no package settings declared.
  • Queues or schedules: scheduled commands capell:xml-sitemap --incremental (manifest declared); queue jobs RebuildAllSitemapsJob, RebuildSiteSitemapJob, RegenerateSiteSitemapIncrementallyJob.
  • Cache tags: site-discovery.
  • Commands: capell:xml-sitemap.

Troubleshooting

Symptom Likely cause Check Fix
Package surface is missing after install Provider or manifest is not loaded Confirm capell.json, package composer.json, and provider registration Reinstall the package, refresh Composer autoload, and clear host caches
Route returns unexpected output Route cache, middleware, or signed URL setup does not match the package route file Check the route files listed in Technical Shape Clear route cache and verify middleware before exposing public routes
Background work does not run Queue worker or declared schedule is not active Check the jobs and scheduled commands listed in Technical Shape Start the queue worker or host scheduler, then run the focused command or package test
Public output leaks unexpected state Render data, cache variation, or authoring boundary has regressed Check public Blade, cache tags, and public-output safety tests Move data loading out of Blade and rerun the package public-output tests

Upgrading

No manual steps between minor versions.

Read CHANGELOG.md before upgrading.

Next Steps