Dashboard Reports
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/dashboard-reports |
| Package slug | dashboard-reports |
| Product group | Capell Operations |
| Tier | premium |
| Bundle | operations |
| Runtime contexts | admin |
| Capell version | ^4.0 |
| Source repository | capell-app/packages |
| Source path | packages/dashboard-reports |
| Docs source | packages/dashboard-reports/docs |
| Manifest | capell.json |
What This Plugin Adds
Section titled “What This Plugin Adds”Dashboard Reports is an Available, No schema impact Capell package in the Capell Operations product group. It ships as capell-app/dashboard-reports and extends these surfaces: admin.
Dashboard Reports surfaces editorial health and publishing momentum directly on the Capell admin dashboard, so owners and editors see what needs attention the moment they log in. The Content Health widget flags scheduled, expired, stale, and URL-less pages with one-click deep-links into the page list, while the Publishing Trend chart tracks published-vs-scheduled activity across any date window. All counts respect each user’s site access, and report visibility is toggleable per dashboard. Built on testable Actions and typed Data objects so teams can extend the reporting layer instead of bolting on a bespoke analytics package.
After install, admins get package-owned management or reporting surfaces inside Capell.
Status details:
- Status: Available
- Tier: premium
- Bundle: operations
- Composer package:
capell-app/dashboard-reports - Namespace:
Capell\DashboardReports - Theme key: not applicable
Why It Matters
Section titled “Why It Matters”For developers: The package gives developers package-owned service providers, Actions, Data objects, Filament classes, and Blade views instead of pushing this behaviour into core or application code.
For teams: At-a-glance content-health and publishing-activity widgets for the Capell admin dashboard - spot scheduled, expired, stale, and URL-less pages without opening a single resource.
Screens And Workflow
Section titled “Screens And Workflow”Screenshot contract: docs/screenshots.json.
- Publishing trend dashboard widget (admin, required).
- Content health dashboard widget (admin, required).
- Dashboard report visibility settings (admin, required).
Technical Shape
Section titled “Technical Shape”- Service providers:
Capell\DashboardReports\Providers\DashboardReportsServiceProvider,Capell\DashboardReports\Providers\AdminServiceProvider. - Config files:
packages/dashboard-reports/config/capell-dashboard-reports.php. - Filament classes:
DashboardReportsPageTableExtender,DashboardReportsDashboardSettingsContributor,ContentHealthFilamentWidget,PublishingTrendChartFilamentWidget. - Actions:
BuildDefaultContentHealthAction,BuildPublishingTrendAction,ExportContentHealthCsvAction,ExportPublishingTrendCsvAction,SendDashboardReportDigestAction. - Data objects:
PublishingTrendData,PublishingTrendPointData,ResolvedDashboardReportsSettingsData. - Command signatures:
capell:dashboard-reports:export,capell:dashboard-reports:send-digest. - Console command classes:
ExportDashboardReportCommand,SendDashboardReportDigestCommand. - Manifest contributions:
dashboard-widget: Capell\DashboardReports\Manifest\DashboardReportsDashboardFilamentWidgetsContribution. - Health checks:
Capell\DashboardReports\Health\DashboardReportsHealthCheck. - Blade views:
packages/dashboard-reports/resources/views/widgets/content-health.blade.php.
Data Model
Section titled “Data Model”This package has no schema impact. It does not declare package-owned migrations or required tables.
Docs gap: document extension points here if the package delegates persistence to a host package.
Install Impact
Section titled “Install Impact”- Admin navigation: adds package-owned Filament classes when registered.
- Permissions: none declared in
capell.json. - Public routes: none detected in package route files.
- Database changes: no package migrations declared.
- Settings: no package settings declared.
- Queues or schedules: none detected in standard package paths.
- Cache tags: none declared.
- Commands:
capell:dashboard-reports:export,capell:dashboard-reports:send-digest.
Common Pitfalls
Section titled “Common Pitfalls”- Verify the package is installed before expecting its provider, views, or extension contributions to run.
- Keep
composer.json,composer.local.json,capell.json, docs, screenshots, and tests aligned when the package surface changes.
Troubleshooting
Section titled “Troubleshooting”| Symptom | Likely cause | Check | Fix |
|---|---|---|---|
| Package surface is missing after install | Provider or manifest is not loaded | Confirm capell.json, package composer.json, and provider registration | Reinstall the package, refresh Composer autoload, and clear host caches |
| Background work does not run | Queue worker or scheduled command is not active | Check package jobs, commands, and host scheduler configuration | Start the queue or scheduler, then run the focused command or package test |
Quick Start
Section titled “Quick Start”- Install the package:
composer require capell-app/dashboard-reports. - Run the required setup: no package migrations are declared; clear cached config and routes if the host app uses caches.
- Open the related Capell admin surface and verify Dashboard Reports appears.
Next Steps
Section titled “Next Steps”- Package docs
- Overview
- Screenshot contract
- Marketplace assets
- Capell content language plan
- Capell documentation design system
- Capell and package ERD notes
- Focused tests:
vendor/bin/pest packages/dashboard-reports/tests --configuration=phpunit.xml.