Theme Commerce
Package docs status
Section titled “Package docs status”This page is generated from public package documentation in capell-4/packages and the package manifest checked into the source repository.
| Field | Value |
|---|---|
| Composer package | capell-app/theme-commerce |
| Package slug | theme-commerce |
| Product group | Capell Themes |
| Tier | premium |
| Bundle | themes |
| Runtime contexts | frontend |
| Capell version | ^4.0 |
| Source repository | capell-app/packages |
| Source path | packages/theme-commerce |
| Docs source | packages/theme-commerce/docs |
| Manifest | capell.json |
Product-led commerce theme for Capell, shipped under the existing commerce theme key.
At A Glance
Section titled “At A Glance”- Package:
capell-app/theme-commerce - Namespace:
Capell\ThemeStudio\Commerce\ - Capell dependencies:
capell-app/core,capell-app/foundation-theme
Why It Helps Your Capell Workflow
Section titled “Why It Helps Your Capell Workflow”- 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.
Best Used With
Section titled “Best Used With”What It Adds
Section titled “What It Adds”- 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.
Why It Matters
Section titled “Why It Matters”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.
Built With
Section titled “Built With”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.
Screens And Workflow
Section titled “Screens And Workflow”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.
Technical Shape
Section titled “Technical Shape”- CommerceThemeServiceProvider registers the Editorial Commerce renderer.
capell.jsondeclaresthemeKey: "commerce"andextends: "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.
Code Map
Section titled “Code Map”| Area | Path | Purpose |
|---|---|---|
| Resources | packages/theme-commerce/resources | Views, translations, assets, and package resources. |
| Tests | packages/theme-commerce/tests | Package-level Pest coverage. |
Data And Persistence
Section titled “Data And Persistence”- This package does not own data.
- It consumes theme runtime settings and core page content.
Install Impact
Section titled “Install Impact”- Adds the Editorial Commerce renderer to theme system.
- No database changes.
- No admin navigation by itself.
- No public routes by itself.
Install And Setup
Section titled “Install And Setup”- Install with
composer require capell-app/theme-commercein 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 usephp artisan. - For screenshots, use a disposable Capell app with the core stack, Layout Builder, Foundation Theme, and only this theme package installed.
Admin And Access
Section titled “Admin And Access”- The package appears through the core Themes resource after install. It does not add a package-owned admin page.
Common Pitfalls
Section titled “Common Pitfalls”- 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
commercepreset; stale settings from another theme can make screenshots misleading. - Do not install a Studio metapackage; this package installs independently.
Testing
Section titled “Testing”Run package tests from the repository root:
vendor/bin/pest packages/theme-commerce/tests --configuration=phpunit.xmlMaintenance Notes
Section titled “Maintenance Notes”- Theme output is public output. Keep admin-only metadata and editor hooks out of rendered markup.