Implementation plans for Drupal core?

If you mean inclusion on Drupal core, it's undetermined if/when that would happen.
If you mean using it as a contrib module, we expect to tag a first beta when the first beta of Drupal CMS is tagged (next week).

We expect to tag a stable version for the first stable Drupal CMS tag (January), or before.

Drupal CMS recipes will be installable stand-alone. But you won't be forced to use that neither.

Automatically closed - issue fixed for 2 weeks with no activity.

For the record, 📌 Merge drupal_cms_dashboard into the starter recipe Active . So the Drupal CMS dashboard won't be an independent recipe.

Unless you want everything in drupal_cms_starter, you will need to manually require the dashboard module and create your own dashboards. It shouldn't be hard to get that config from a drupal_cms installation though if you need that.

We hope dashboard will be widely adopted and recipes will emerge for different usecases.

Hmm, any chance of getting a short write-up/tutorial on how to implement and example, suggested config to use for interested adopters of the new dashboard features in non Drupal-CMS projects? I think that would definitely help with exposing the feature to an initial wider audience and getting engagement (including myself =) ).

@mtfift started working on this at https://www.drupal.org/docs/extending-drupal/contributed-modules/contrib... →

penyaskito → credited mtift → .

Would be great to add a help topic(s) https://www.drupal.org/docs/develop/managing-a-drupalorg-theme-module-or... →

Module sounded interesting.

I had no problem enabling the module, creating a dashboard and configuring it.

But I can't for the life of me find any information about how to actually view / use the dashboard. Hopefully the documentation catches up.

@drasgardian, my understanding is the new Dashboard you configured should be able to replace the standard user account page and be set as the default for users when they log in or click to view their account information.

That said, and without trying it myself yet, I plugged the question into ChatGPT and got the following:

In Drupal, how do you set a new path as the default page for users logging in, or when they click to see their account page? I want to install and use the Dashboard module, but am unsure how to actually have it replace the current user account page.
Reasoned for 1m 40s
You can achieve this in one of two ways:

1. Redirect Users After Login
If you want users to land on your dashboard immediately after they log in (rather than when they click on “My Account”), you can use a contributed module like Login Destination. With this module, you configure a rule so that when a user logs in, they’re redirected to your new dashboard path (for example, /dashboard).

Steps:

Install & Enable Login Destination:
Download and enable the module.

Configure the Redirect:
Go to Configuration > People > Login Destination and add a rule that targets the user login event. Specify /dashboard (or your chosen path) as the destination.

This method ensures users are sent to the dashboard right after logging in.

2. Override the Default User Account Page
If you want to permanently replace the default /user page (the account page) with your dashboard, you’ll need to override Drupal’s route for the user account page. In Drupal 8/9/10, this is best done by creating a custom module that implements a Route Subscriber.

Example Implementation:

Create a Custom Module:
Create a new module (e.g., my_dashboard_override).

Implement a Route Subscriber:
In your module, add a file (e.g., src/Routing/MyDashboardRouteSubscriber.php) with the following code:

<?php

namespace Drupal\my_dashboard_override\Routing;

use Drupal\Core\Routing\RouteSubscriberBase;
use Symfony\Component\Routing\RouteCollection;

class MyDashboardRouteSubscriber extends RouteSubscriberBase {
  /**
   * Alters existing routes.
   *
   * @param \Symfony\Component\Routing\RouteCollection $collection
   *   The route collection.
   */
  protected function alterRoutes(RouteCollection $collection) {
    // Override the default user account page.
    if ($route = $collection->get('entity.user.canonical')) {
      // Replace the controller with the Dashboard module’s controller.
      // (Make sure to adjust this to the actual namespace and method provided by your Dashboard module.)
      $route->setDefault('_controller', '\Drupal\dashboard\Controller\DashboardController::dashboard');
      // Optionally, change the title.
      $route->setDefault('_title', 'Dashboard');
    }
  }
}

Register the Route Subscriber:
Create a my_dashboard_override.services.yml file in your module’s root with this content:

services:
  my_dashboard_override.route_subscriber:
    class: Drupal\my_dashboard_override\Routing\MyDashboardRouteSubscriber
    tags:
      - { name: event_subscriber }

Clear Cache:
After enabling your custom module, clear all caches so that Drupal picks up your route override.

This method replaces the default /user route so that whenever a logged-in user visits their account page, they see the dashboard instead.

Summary
Redirect on Login: Use the Login Destination module to send users to /dashboard right after they log in.
Override the Route: Create a custom module with a Route Subscriber to change the default user account page (entity.user.canonical) to use the Dashboard module’s controller.
Choose the method that best fits your desired user experience. If you want the dashboard to always appear in place of the account page, the route override is the way to go. Otherwise, redirecting on login might be sufficient if you only want to change the post-login behavior.

@drasgardian If you are using the classic toolbar, you will have a link to the dashboard, which sites in /admin/dashboard.
If you are using the new navigation module, there's a known support request for providing an API for adding the link, which was recently (as in 2 days ago) committed to core. Is that your case?

@w01f #12 isn't needed at all, and contains wrong information. Please verify AI provided information before posting on drupal.org and confusing others. If they wanted a chatGPT response, they would ask chatGPT and not in drupal.org issue queues.

@penyaskito absolutely. I went ahead and removed the ChatGPT response suggestions. I'm also eager to use the new dashboard and will await official details on how to correctly implement it.