Skip to content

Theme Folio

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-folio
Package slugtheme-folio
Product groupCapell Themes
Tierpremium
Bundlethemes
Runtime contextsfrontend
Capell version^1.0
Catalogue roleextension
Release channelBeta
Source repositorycapell-app/packages
Source pathpackages/theme-folio
Docs sourcepackages/theme-folio/docs
Manifestcapell.json

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

Theme Folio presents finite publications as numbered bound editions with responsive spreads, section navigation, and package-owned integrations for figures, enquiries, bookings, and indexes.

Use Preview Theme Folio on existing content before Apply Theme Folio, which changes the selected site’s public design; reapply its previous theme to restore that selection. Shared Theme Studio settings saves can affect public pages. For fictional demo content, name a disposable target with —sites and review —url and —languages; unscoped setup refuses existing sites, scoped repeats preserve site configuration unless —force deliberately replaces its theme, enabled state, requested site translations and domains, while demo pages, widgets and demo layouts are rewritten on scoped repeats.

Status details:

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

For developers: Typed Folio Actions and Data objects keep edition numbering, section resolution, and public rendering inside the theme package rather than leaking theme logic into Core or the host app.

For teams: Teams can publish an annual review, prospectus, or catalogue with the visual rhythm of a designed book while retaining ordinary web navigation and accessible fallbacks.

Screenshot contract: docs/screenshots.json.

Folio Homepage Folio Homepage Folio Directory Folio Directory

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

  • Folio Homepage (frontend, required evidence).
  • Folio Directory (frontend, required evidence).
  • Folio Detail (frontend, required evidence).
  • Folio Contact (frontend, required evidence).
  • Folio Empty state (frontend, supplementary evidence).
  • Folio Not found (frontend, supplementary evidence).
  • Folio Call to action (frontend, required evidence).
  • Capell\ThemeFolio\FolioThemeServiceProvider
  • Capell\ThemeFolio\Providers\ConsoleServiceProvider
  • BuildFolioBookDataAction
  • InstallFolioThemeDemoAction
  • ResolveFolioSectionDataAction
  • FolioBookData
  • FolioSectionData
  • FolioSpreadData
  • FolioThemePresetData
  • capell:theme-folio-demo
  • FolioDemoCommand
  • admin-page: Capell\ThemeFolio\Manifest\ThemeManagementPageContribution
  • Capell\ThemeFolio\Health\ThemeFolioHealthCheck
  • packages/theme-folio/resources/views/components/folio-book.blade.php
  • packages/theme-folio/resources/views/components/folio-spread.blade.php
  • packages/theme-folio/resources/views/components/integrations/chronicle-journal.blade.php
  • packages/theme-folio/resources/views/components/integrations/chronicle-static.blade.php
  • packages/theme-folio/resources/views/components/integrations/enquiry-bookings.blade.php
  • packages/theme-folio/resources/views/components/integrations/enquiry-form.blade.php
  • packages/theme-folio/resources/views/components/integrations/enquiry-mailto.blade.php
  • packages/theme-folio/resources/views/components/integrations/figure-chart.blade.php
  • packages/theme-folio/resources/views/components/integrations/figure-table-only.blade.php
  • packages/theme-folio/resources/views/components/integrations/index-anchors.blade.php
  • packages/theme-folio/resources/views/components/integrations/index-search.blade.php
  • packages/theme-folio/resources/views/components/integrations/notice.blade.php
  • packages/theme-folio/resources/views/layout/main-content.blade.php
  • packages/theme-folio/resources/views/sections/content-listing--index-register.blade.php
  • packages/theme-folio/resources/views/sections/cta--colophon.blade.php
  • packages/theme-folio/resources/views/sections/hero--cover-plate.blade.php
  • packages/theme-folio/resources/views/widget/partials/colophon-page.blade.php
  • packages/theme-folio/resources/views/widget/partials/cover-plate.blade.php
  • packages/theme-folio/resources/views/widget/partials/index-register.blade.php
  • packages/theme-folio/resources/views/widget/section.blade.php
  • packages/theme-folio/resources/views/widget/sections/colophon-page.blade.php
  • packages/theme-folio/resources/views/widget/sections/content-listing--index-register.blade.php
  • packages/theme-folio/resources/views/widget/sections/contents-leaders.blade.php
  • packages/theme-folio/resources/views/widget/sections/cover-plate.blade.php
  • packages/theme-folio/resources/views/widget/sections/cta--colophon.blade.php
  • packages/theme-folio/resources/views/widget/sections/double-truck--blank-leaf.blade.php
  • packages/theme-folio/resources/views/widget/sections/double-truck--errata.blade.php
  • packages/theme-folio/resources/views/widget/sections/double-truck.blade.php
  • packages/theme-folio/resources/views/widget/sections/figure-table.blade.php
  • packages/theme-folio/resources/views/widget/sections/generic.blade.php
  • packages/theme-folio/resources/views/widget/sections/hero--cover-plate.blade.php
  • packages/theme-folio/resources/views/widget/sections/index-register.blade.php
  • packages/theme-folio/resources/views/widget/sections/marginalia-note.blade.php
  • packages/theme-folio/resources/views/widget/sections/plate-gallery.blade.php
  • packages/theme-folio/resources/views/widget/sections/pull-quote-leaf.blade.php
  • packages/theme-folio/resources/views/widget/sections/timeline-folio.blade.php
  • theme-folio

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, capell-app/layout-builder.
  • Admin navigation: declares admin-page: ThemeManagementPageContribution; each Filament page or resource controls its own navigation visibility.
  • Admin/editor extensions: none declared.
  • Permissions: no package permission declarations or Shield gates detected; host access rules still apply.
  • 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-folio.
  • Commands: capell:theme-folio-demo.
  • Keep required Capell packages on compatible v4 releases: capell-app/core, capell-app/theme-foundation, capell-app/frontend, capell-app/layout-builder.
  • 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-folio 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-folio.
  2. See it working on a disposable site: run php artisan capell:theme-folio-demo --sites="Theme demo". Choose a new site name for your demo; keep customer sites for the Preview → Apply workflow above.
  3. Run php artisan list and verify the package command signatures are registered.

No manual steps between minor versions.