Frontend Optimizer
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/frontend-optimizer |
| Package slug | frontend-optimizer |
| Product group | Capell Foundation |
| Tier | premium |
| Bundle | foundation |
| Runtime contexts | admin, frontend |
| Capell version | ^4.0 |
| Source repository | capell-app/packages |
| Source path | packages/frontend-optimizer |
| Docs source | packages/frontend-optimizer/docs |
| Manifest | capell.json |
Profile-based CSS and JavaScript delivery for public Capell pages.
At A Glance
Section titled “At A Glance”- Package:
capell-app/frontend-optimizer - Namespace:
Capell\FrontendOptimizer\ - Surfaces: frontend Blade directive, queue, database
- Service providers:
packages/frontend-optimizer/src/Providers/FrontendOptimizerServiceProvider.php - Capell dependencies:
capell-app/core,capell-app/frontend - Third-party dependencies:
lorisleiva/laravel-actions,spatie/laravel-data,spatie/laravel-package-tools,symfony/process
Why It Helps Your Capell Workflow
Section titled “Why It Helps Your Capell Workflow”- Provides profile-based CSS and JavaScript delivery so Capell frontend performance can improve without rewriting themes.
- Helps owners keep pages lean as optional packages add assets, widgets, and render profiles.
- Gives developers manifest, critical CSS, and render-profile surfaces for package-aware asset loading.
Best Used With
Section titled “Best Used With”What It Adds
Section titled “What It Adds”- Profile-based CSS and JavaScript delivery for public Capell pages.
@frontendOptimizerAssets(...)Blade directive for rendering resolved profile assets.- Render profile storage and critical CSS generation support.
- No direct Filament admin surface or public route.
Code Map
Section titled “Code Map”| Area | Path | Purpose |
|---|---|---|
| Actions | packages/frontend-optimizer/src/Actions | Domain operations. Test these directly where possible. |
| Data | packages/frontend-optimizer/src/Data | Structured payloads, form state, view models, and integration data. |
| Enums | packages/frontend-optimizer/src/Enums | Persisted states and Filament option values. |
| Models | packages/frontend-optimizer/src/Models | Eloquent records owned by the package. |
| Jobs | packages/frontend-optimizer/src/Jobs | Queued work and async side effects. |
| Providers | packages/frontend-optimizer/src/Providers | Registration, extension hooks, routes, migrations, and resources. |
| Resources | packages/frontend-optimizer/resources | Views, translations, assets, and package resources. |
| Config | packages/frontend-optimizer/config | Package configuration and publishable config. |
| Database | packages/frontend-optimizer/database | Migrations, seeders, and settings migrations. |
| Tests | packages/frontend-optimizer/tests | Package-level Pest coverage. |
Runtime Surface
Section titled “Runtime Surface”- Blade directive:
@frontendOptimizerAssets(...). - Jobs:
GenerateCriticalCssJob. - Critical CSS generation uses the configured process runner; keep failures visible in optimization run records rather than hiding them in Blade output.
Data And Persistence
Section titled “Data And Persistence”- Models:
FrontendOptimizationRun,FrontendRenderProfile. - Migrations:
2026_05_10_190851_01_create_frontend_optimizer_tables.php. - Config:
packages/frontend-optimizer/config/capell-frontend-optimizer.php. - Data objects live in
src/Data/; use them for payloads, form state, and view models.
Extension Points
Section titled “Extension Points”- Contracts:
CriticalCssGenerator. - Register Capell extension points, routes, migrations, settings, render hooks, and resources from service providers.
Install And Setup
Section titled “Install And Setup”- Install with
composer require capell-app/frontend-optimizerin the host Capell application. - Run migrations through the host application package install flow.
- In this repository, verify package changes with
vendor/bin/pest; do not usephp artisan.
Testing
Section titled “Testing”Run package tests from the repository root:
vendor/bin/pest packages/frontend-optimizer/tests --configuration=phpunit.xmlMaintenance Notes
Section titled “Maintenance Notes”- Put behaviour changes in
src/Actions/; UI classes, commands, and controllers should call actions instead of owning domain logic. - Use package
Dataclasses at boundaries instead of passing anonymous arrays between layers. - Use backed enums for persisted values and enum labels for Filament options.