Enhancing User Statistics: Building a Dynamic Reference Dashboard
The Challenge
In the devlog-ist/landing project, our statistics dashboard needed a more robust way to present user references. Previously, the view lacked sufficient granularity, failing to distinguish between active, expired, or withdrawn references. We wanted to provide a transparent overview that includes verification statuses and platform-specific badges like LinkedIn.
The Approach
To address this, we implemented a data-driven approach that integrates backend state management directly into our UI components. By injecting reference data into the tenantStatsData() context, we ensured consistency across various layout templates.
Integrating Reference Logic
We centralized the retrieval of references to allow for dynamic widget rendering. This ensures that the statistics page remains responsive to the actual state of user-confirmed data.
public function tenantStatsData(): array
{
return [
'confirmedReferences' => $this->repository->getConfirmed(),
'isVerifiedByLinkedIn' => $this->repository->hasLinkedInAuth(),
'references' => $this->repository->allReferences(),
];
}
This method acts as the source of truth for our Blade templates, allowing us to conditionally render badges and sections based on the returned array.
Component-Based UI Strategy
By leveraging our existing component structure, we introduced dedicated widgets for reference management. These widgets handle the logic of splitting statuses:
- Active: References currently in good standing.
- Expired: References where the
token_expires_attimestamp has passed. - Withdrawn/Canceled: References no longer valid.
We also introduced a visual indicator using Alpine.js and Blade conditionals to highlight verified sources. When a reference is LinkedIn-verified, a specific badge appears alongside the reference count, providing immediate trust signals to the user.
Final Implementation
By unifying the data pipeline, we replaced fragmented status checking with a centralized view logic. This not only improved the maintainability of our statistics page but also enabled consistent internationalization across four languages for our status labels.
Key Insight
Centralizing data retrieval at the controller or component level reduces logic duplication in your view files. By moving the heavy lifting of status calculation to the PHP layer, your templates remain declarative and easy to maintain, while ensuring that the UI accurately reflects the underlying data state.
Generated with Gitvlg.com