Skip to content

Theme Submissions

This page is generated from package source documentation in the Capell packages repository and the checked-in manifest. Source documentation is not distribution status. Before running a Composer command, verify that the exact package and compatible 1.x release are available through public Packagist or the authenticated marketplace account.

FieldValue
Composer packagecapell-app/theme-submissions
Package slugtheme-submissions
Product groupCapell Themes
Tierpremium
Bundlethemes
Runtime contextsfrontend
Capell version^1.0
Source repositorycapell-app/packages
Source pathpackages/theme-submissions
Docs sourcepackages/theme-submissions/docs
Manifestcapell.json

Theme Submissions is an Available, No schema impact Capell theme in the Capell Themes product group. It ships as capell-app/theme-submissions and extends these surfaces: frontend.

Theme Submissions adds gallery, facet, activity, and winners-ledger presentation for awards and open-call entries. Submission data remains in Capell; the theme controls how it is displayed.

When selected, visitors can browse a varied submission grid, narrow entries by metadata, and review winners in a structured ledger.

Evidence: src/SubmissionsThemeServiceProvider.php, resources/views/sections/card-shuffle-grid.blade.php, resources/views/sections/metadata-facet-wall.blade.php, resources/views/sections/winners-ledger-table.blade.php, resources/views/sections/submission-pulse.blade.php, tests/Feature/SignatureWidgetsRenderTest.php, tests/Unit/PublicOutputSafetyTest.php.

Status details:

  • Status: Available
  • Tier: premium
  • Bundle: themes
  • Composer package: capell-app/theme-submissions
  • Namespace: Capell\ThemeSubmissions
  • Theme key: submissions

For developers: The package combines a typed theme definition with a deterministic shuffle Action for repeatable gallery ordering.

For teams: Program teams can give active entries, browse filters, and final winners distinct public views while keeping one editorial source of truth.

Evidence: src/SubmissionsThemeServiceProvider.php, src/Actions/ComputeDeterministicShuffleOrderAction.php, tests/Unit/ComputeDeterministicShuffleOrderActionTest.php, resources/views/sections/card-shuffle-grid.blade.php, resources/views/sections/metadata-facet-wall.blade.php, resources/views/sections/winners-ledger-table.blade.php.

Screenshot contract: docs/screenshots.json.

Submissions Homepage Submissions Homepage Submissions Landing page Submissions Landing page

Desktop, tablet, and mobile variants remain defined in the screenshot contract; this list groups them by workflow.

  • Submissions Homepage (frontend, required).
  • Submissions Landing page (frontend, required).
  • Submissions Project archive (frontend, required).
  • Submissions Search results (frontend, required).
  • Submissions Contact form (frontend, optional).
  • Submissions Page Not Found (frontend, optional).
  • Submissions Call To Action (frontend, optional).
  • Service providers: Capell\ThemeSubmissions\SubmissionsThemeServiceProvider.
  • Actions: ComputeDeterministicShuffleOrderAction, InstallSubmissionsThemeDemoAction.
  • Command signatures: capell:theme-submissions-demo.
  • Console command classes: DemoCommand.
  • Manifest contributions: admin-page: Capell\ThemeSubmissions\Manifest\ThemeManagementPageContribution.
  • Health checks: Capell\ThemeSubmissions\Health\ThemeSubmissionsHealthCheck.
  • Blade views: packages/theme-submissions/resources/views/page.blade.php, packages/theme-submissions/resources/views/sections/card-shuffle-grid--compact.blade.php, packages/theme-submissions/resources/views/sections/card-shuffle-grid.blade.php, packages/theme-submissions/resources/views/sections/content-listing.blade.php, packages/theme-submissions/resources/views/sections/cta.blade.php, packages/theme-submissions/resources/views/sections/featured-today-banner--split.blade.php, packages/theme-submissions/resources/views/sections/featured-today-banner.blade.php, packages/theme-submissions/resources/views/sections/footer.blade.php, packages/theme-submissions/resources/views/sections/hero.blade.php, packages/theme-submissions/resources/views/sections/infinite-scroll-depth-pressure--rows.blade.php, packages/theme-submissions/resources/views/sections/infinite-scroll-depth-pressure.blade.php, packages/theme-submissions/resources/views/sections/metadata-facet-wall--dense.blade.php, and 13 more.
  • Cache tags: theme-submissions.

This theme has no schema impact. It relies on core Capell site, page, locale, and theme records instead of declaring package-owned tables.

  • Required packages: capell-app/core, capell-app/theme-foundation, capell-app/frontend.
  • Admin navigation: declares admin-page: ThemeManagementPageContribution; each Filament page or resource controls its own navigation visibility.
  • Admin/editor extensions: none declared.
  • Permissions: none declared in capell.json.
  • Public routes: none declared.
  • Database changes: no package migrations declared.
  • Config: no package config files.
  • Settings: no package settings declared.
  • Queues or schedules: none declared.
  • Cache tags: theme-submissions.
  • Commands: capell:theme-submissions-demo.
  • Keep required Capell packages on compatible v4 releases: capell-app/core, capell-app/theme-foundation, capell-app/frontend.
  • 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 theme-submissions cache tags.
SymptomLikely causeCheckFix
Package surface is missing after installProvider or manifest is not loadedConfirm capell.json, package composer.json, and provider registrationReinstall the package, refresh Composer autoload, and clear host caches
Public output leaks unexpected stateRender data, cache variation, or authoring boundary has regressedCheck public Blade, cache tags, and public-output safety testsMove data loading out of Blade and rerun the package public-output tests
  1. Install the package: composer require capell-app/theme-submissions.
  2. No package-specific setup command or migrations are declared.
  3. Open the Submissions Homepage and confirm the public output renders without admin state.