October 12, 2026
The original user experience was a 'welcome screen'. All navigation was performed at the top level menu. A dashboard experience was not in the original design, and at the cost of development at that time, arguably would not have been worth the effort.
Fast forward to today. Some reflections on possible improvements. The dashboard experience is great as it provides an at 'at an glance' experience for users, access to critical information for users, with minimal effort. The issue here is that attempting to consolidate relevant metrics for different users across different roles is an 'one size fits all' approach.
I have put a few cycles into proof of concept related work on dashboard patterns, for which I have imported here.
We can identify the need to establish an dashboard experience for a user under a given role, so the concept of creating 'starter templates' was implemented.
My approach towards supporting this dashboard functionality was an interactive process. Based on past experiences, introducing small sets of functions in an iterative manner is most effective.
Define the requirement for a dashboard with role based templates Define the scope of the concept of a panel Instruct the agent to create an initial panel Identify a list of common components Define role based less complex components in single spec files, define more complex components on an individual by individual basis