Introducing The Dashboard Initiative | Penyaskito Blog

@penyaskito This is a great initiative! Is there any interest in broadening it to providing content dashboards for *anyone* who logs in to a site, not just admins or content managers?

Intranets and other sites with restricted/personalized content requiring a login could all benefit from giving users the ability to configure a home screen with information most useful for them.

@DaleTrexel @penyaskito I assumed it would be for anyone. At a previous job we rebuilt panels_dashboard for our SaaS. Dashboards as page variants customizable per user for students, teachers, and school faculty. I'm really excited about this.
@DaleTrexel @penyaskito I am assuming scoping and story generation is easier when picking two common personas. Anything else should come easily

@mglaman @penyaskito No arguments there: I think this could be a very useful general purpose dashboard tool first, which then could be further configured to focus on content/administrative tasks.

The article, issue linked from it, and Drupal core goals justification are all heavily focused on using dashboards for Drupal tasks, so I wanted to raise awareness for using dashboards from a content consumption perspective as well.

@mglaman @penyaskito This seems a case where it would be easier to build a general tool from the start than to take something designed specifically for admins & content managers and try to add on broader functionality later.

@DaleTrexel @penyaskito I don't know if it'd be easier. Sometimes being more constrained makes delivery easier and allows for feedback. Building something more generic leads to bike shedding on approach and lack of delivery in a large open source project like Drupal.

But it should have some kind of off-ramp plan for customization documented.