Explain differences in other contributed dashboard modules

Good idea, @thejimbirch.

First, I agree it would be good to mention these other modules on the project page and I started a list in the description of this module. We have had some discussions with maintainers of other dashboard modules (e.g., https://www.drupal.org/project/dashboards → ) and we are definitely open to working together. That said, some of those modules take a different technical approach, so directly incorporating features might be more difficult.

Second, this module grew out of a core idea 🌱 Enhance user experience with customizable dashboards Active and is being built and maintained in a way that might make it a candidate for Drupal core, in addition to Drupal CMS (Starshot). Those modules that you mentioned provide functionality that goes beyond what we might include in core, such as Bootstap or Matomo integration.

I probably should also mention that (at this point) we are working closely with the Drupal Starshot leadership team. They are defining the scope of work 📌 [META] Track 11: Dashboard page for post installation and login Active and we are working to implement it. My guess is that those other dashboard implementations have different requirements.

While I agree on the usual approach of adding a comparison, my only concern is dashboard_s_.

Our plan when we were proposing this for core is that that one would extend this one when this would make it into core, including an upgrade path.

I don't see a point on promoting alternatives that depend on a given theme or are pieces of a distribution. Those probably should/will build on top of this module themselves.

Just throwing in another - https://www.drupal.org/project/content_planner → has a pretty slick dashboard template as a part of it.

I'd include the most popular dashboard module as well https://www.drupal.org/project/workbench →