Skip to content

Theme Commerce

This page is generated from public package documentation in capell-4/packages and the package manifest checked into the source repository.

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

Product-led commerce theme for Capell, shipped under the existing commerce theme key.

  • Package: capell-app/theme-commerce
  • Namespace: Capell\ThemeStudio\Commerce\
  • Capell dependencies: capell-app/core, capell-app/foundation-theme
  • Provides Editorial Commerce renderer views for catalog and retail sites built on Capell.
  • Helps owners launch product-led pages with product finding, collections, product grids, comparison, catalog, proof, and resource surfaces.
  • Gives developers a focused theme package that reuses Foundation Theme conventions instead of hard-coding product layouts into content.
  • Editorial Commerce commerce theme for Capell.
  • Public views for navigation, hero, product finder, collections, product grid, comparison, catalog, proof, blog teaser, CTA, and footer sections.
  • Catalog and blog teaser renderers receive optional Shopify Commerce and Blog availability from the service provider, then render enhanced or neutral panels without querying from Blade.

For developers: Adds a renderer package that uses Foundation Theme runtime contracts while leaving content models unchanged.

For teams: Provides a commerce-oriented visual option for product sites managed through the normal Theme admin page and install flow.

This package makes its Composer dependencies visible because they are part of the value proposition, not just plumbing. When an upstream package has a public repository, its linked preview card points readers back to the maintainers so their work gets proper credit.

Capell packages used here

Open-source packages used here

  • No extra third-party Composer package beyond the Capell package stack is required here.

Screenshots are generated from docs/screenshots.json during package deployment.

  • Theme admin list showing Editorial Commerce.
  • Frontend page rendered with Editorial Commerce theme.
  • Theme preview URL output.
  • CommerceThemeServiceProvider registers the Editorial Commerce renderer.
  • capell.json declares themeKey: "commerce" and extends: "capell-app/foundation-theme".
  • Uses Foundation Theme runtime data and standard section keys, while rendering its own page and section Blade views.
  • Ships Blade resources for the page wrapper, product discovery sections, catalog panel, comparison, proof, blog teaser, CTA, and footer views.
  • No migrations, config, routes, models, admin navigation, or package-owned settings are present.
  • Public theme output must stay free of package identifiers, signed admin URLs, Filament/editor markers, and other authoring metadata.
AreaPathPurpose
Resourcespackages/theme-commerce/resourcesViews, translations, assets, and package resources.
Testspackages/theme-commerce/testsPackage-level Pest coverage.
  • This package does not own data.
  • It consumes theme runtime settings and core page content.
  • Adds the Editorial Commerce renderer to theme system.
  • No database changes.
  • No admin navigation by itself.
  • No public routes by itself.
  • Install with composer require capell-app/theme-commerce in the host Capell application.
  • Seed the Editorial Commerce preview pages with php artisan capell:theme-commerce-demo --url=https://demo.test --sites=Demo --languages=en --force.
  • The Extensions installer demo checkbox and full Capell demo install use the same manifest demo command path.
  • In this repository, verify package changes with vendor/bin/pest; do not use php artisan.
  • For screenshots, use a disposable Capell app with the core stack, Layout Builder, Foundation Theme, and only this theme package installed.
  • The package appears through the core Themes resource after install. It does not add a package-owned admin page.
  • Install Layout Builder before Foundation Theme in the disposable harness.
  • Install Foundation Theme before using this renderer.
  • Build both frontend and Filament assets before browser capture.
  • Keep Theme Studio settings aligned with the commerce preset; stale settings from another theme can make screenshots misleading.
  • Do not install a Studio metapackage; this package installs independently.

Run package tests from the repository root:

Terminal window
vendor/bin/pest packages/theme-commerce/tests --configuration=phpunit.xml
  • Theme output is public output. Keep admin-only metadata and editor hooks out of rendered markup.