README

capell-app/core is the platform package for Capell CMS. It owns the shared content model, package registry, install and upgrade orchestration, settings infrastructure, and extension contracts used by Admin, Frontend, Installer, Marketplace, and first-party add-ons.

Use this package when a Laravel app needs Capell's domain records and extension API. It is not an editor UI or public renderer by itself.

Package Boundary

Core owns:

• sites, domains, languages, pages, page URLs, layouts, themes, blueprints, media records, redirects, package state, and upgrade log records
• install, upgrade, rollback, package cache, component cache, doctor, faker, and maker commands
• package manifest validation, package registry state, settings schemas, subscribers, render blocks, maker registration, and model-level contracts
• database migrations and settings migrations for the shared Capell schema

Core does not own:

• the Filament admin panel, resources, dashboard surfaces, and editor workflow; that is capell-app/admin
• public request handling and public HTML rendering; that is capell-app/frontend
• browser installer routes and setup removal; that is capell-app/installer
• catalogue browsing, account linking, domain verification, and install authorization; that is capell-app/marketplace
• visual layout building, frontend authoring, generated HTML cache, SEO, blog, navigation, or migration/recovery features; those live in add-on packages

Install

For a guided full-stack setup, require capell-app/installer and run php artisan capell:install — it brings in core and composer-requires the admin/frontend packages you choose. To use core on its own (headless or manual setups):

composer require capell-app/core
php artisan capell:install

capell:install coordinates the foundation install flow. On an existing Capell app, use:

php artisan capell:upgrade
php artisan capell:doctor

Use php artisan list capell in the host app to confirm the exact command set available after Composer discovery.

Runtime Surfaces

• Provider: Capell\Core\Providers\CapellServiceProvider
• Config: packages/core/config/capell.php, packages/core/config/audit.php, packages/core/config/redirects.php
• Main models: Page, PageUrl, Site, SiteDomain, Language, Layout, Theme, Blueprint, Type, Media, CapellExtension, UpgradeLogEntry
• Main commands: capell:install, capell:upgrade, capell:rollback, capell:doctor, capell:package-cache, capell:package-cache:clear, capell:publish-migrations, capell:delete-migrations, capell:publish-components, capell:make-*
• Test case support: Capell\Core\Testing\ExtensionTestHarness

Type remains present for compatibility while the admin surface is moving toward Blueprint naming. New docs and UI copy should prefer Blueprint unless they are documenting a compatibility API that still uses type terminology.

Extension Points

Use Core extension points instead of patching first-party models or providers:

When adding a Core migration, also append it to packages/core/src/Concerns/HasMigrations.php; otherwise package installs can miss the migration.

Data And Persistence

Core is schema-owning. It creates the tables used by most Capell packages, including page, site, language, layout, theme, blueprint, media, extension, redirect, audit, and upgrade state.

Settings migrations are part of package installation and must be idempotent. Wrap new settings migrations in existence checks so upgrades and fresh installs behave the same way.

Core records are used by public rendering and admin workflows, so avoid adding admin-only assumptions to models, casts, or public serialization paths.

Verification

Run the smallest relevant check first:

vendor/bin/pest packages/core/tests --configuration=phpunit.xml

For shared contract changes, also run the package boundary and manifest tests:

vendor/bin/pest packages/core/tests/Arch packages/core/tests/Unit/Manifest --configuration=phpunit.xml

Before landing broader Core changes, run the repo preflight command:

composer preflight

Troubleshooting

• Missing package surfaces usually mean Composer discovery or the Capell package cache is stale. Run composer dump-autoload, then php artisan capell:package-cache:clear.
• New migrations that work in tests but not on install are usually missing from HasMigrations::getMigrations().
• Missing default page records or Blueprint warnings should be checked with php artisan capell:doctor before changing seed or setup code.
• Do not document moved features as Core behavior. Publishing Studio, generated HTML cache, site discovery, frontend authoring, SEO, blog, navigation, and Migration Assistant workflows are package-owned.

Further Reading