Problem/Motivation
The concept of accessing all dashboards from a singular location presents a key advantage: convenience in discovery, management, and placement in the admin toolbar and navigation menu. But imagine how effective dashboards could be if contribute module maintainers were able to integrate them within the module's ecosystem.
Take Drupal Commerce for instance. It claims the /admin/commerce URL, creating a launchpad for everything related to commerce - from product administration, orders, to shipping methods, and the list goes on. Given that these spheres aren't closely interlinked, /admin/commerce utilizes \Drupal\system\Controller\SystemController::systemAdminMenuBlockPage to display inherited menu links from all sub-sections (or submodules). Now, what if it could convert /admin/commerce into a dynamic dashboard, exhibiting the real-time state of the e-commerce platform? This modification could give merchants a snapshot of their daily tasks - be it new orders awaiting fulfillment, budget goal charts, recently imported products needing content review and publication, amongst others.
And it's not just limited to commerce - the Webform module could showcase form submission statistics and a compilation of active forms. The "Group" could feature a dashboard that displays new group registrations or a list of groups pending verification.
In essence, allowing the definition of the dashboard from within the module will considerably bolster its adoption, creating a user-friendly and interactive experience.
Proposed resolution
TBD
Remaining tasks
TBD
User interface changes
TBD
API changes
TBD
Data model changes
TBD