Active users
1,284
Orders
312
Revenue
$38.5k
Open tickets
17
Revenue overview
Last 12 monthsTraffic sources
Recent orders
View all| Order | Customer | Date | Status | Total |
|---|---|---|---|---|
| #3102 | Ana Popescu | 17.07.2026 | Paid | €1,250.00 |
| #3101 | Bogdan Ionescu | 17.07.2026 | Pending | €860.00 |
| #3100 | Carmen Georgescu | 16.07.2026 | Paid | €2,300.00 |
| #3099 | Dan Dumitrescu | 16.07.2026 | Failed | €415.00 |
The rules — the dashboard composition
- Composition, top to bottom: stat row (4-up, stat cards, data from task.php) → charts row (8/4: the main trend + one breakdown, g.chart — theme comes from the tokens automatically) → recent activity (4–5 rows with a "View all" header action linking the real list page — a small full-bleed table is acceptable HERE as the small-table exception; anything bigger or interactive is a lister block).
- A dashboard SHOWS, it does not manage — row actions, editing and bulk operations live on the list pages; every block links where the work happens.
- Pick 3–5 stats that matter, not everything you can count; the change badge direction is about the METRIC's health (down can be good — see Open tickets).
- Charts get fixed heights (320px here) so the row does not jump while loading.