Skip to content

Dashboard: register admin page route + sidebar menu (shell) #77573

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
retrofox merged 5 commits into from
Apr 23, 2026
Merged

Dashboard: register admin page route + sidebar menu (shell) #77573

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
5 commits
Select commit Hold shift + click to select a range
469d0ec
add dashboard route and page registration
retrofox Apr 15, 2026
b8803cd
add dashboard-widgets admin page loader
retrofox Apr 15, 2026
8d195eb
wire dashboard-widgets loader behind experiment flag
retrofox Apr 15, 2026
145dab1
wrap dashboard stage in admin-ui Page shell
retrofox Apr 22, 2026
beacfdf
update package-lock for dashboard route deps
retrofox Apr 22, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
23 changes: 23 additions & 0 deletions lib/experimental/dashboard-widgets/load.php
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,23 @@
<?php
/**
* Bootstraps the Dashboard Widgets page in wp-admin.
*
* @package gutenberg
*/

add_action( 'admin_menu', 'gutenberg_register_dashboard_widgets_menu' );

@simison simison Apr 23, 2026

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Later, we could replace the regular route with the experiment, and explore what backwards compatibility should look like.

@retrofox retrofox Apr 23, 2026

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Agreed, that's the direction. This shell is strictly additive so we can iterate behind the flag without touching the classic dashboard.

The BC surface is the interesting piece: wp_add_dashboard_widget(), wp_dashboard_setup, meta box order stored in user meta, etc. We're looking at it as a separate workstream, probably through an automatic bridge that exposes legacy meta boxes as widgets in the new grid. Out of scope for this PR.


/**
* Registers the Dashboard Widgets menu item.
*/
function gutenberg_register_dashboard_widgets_menu() {
add_menu_page(
__( 'Dashboard (Beta)', 'gutenberg' ),
__( 'Dashboard (Beta)', 'gutenberg' ),
'read',
'dashboard-wp-admin',
'gutenberg_dashboard_wp_admin_render_page',
'dashicons-dashboard',
1
);
}
5 changes: 5 additions & 0 deletions lib/load.php
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -226,3 +226,8 @@ function gutenberg_is_experiment_enabled( $name ) {
require __DIR__ . '/experimental/content-types/load.php';
require __DIR__ . '/experimental/content-types/index.php';
}

// Dashboard Widgets (only load when experiment is enabled).
if ( gutenberg_is_experiment_enabled( 'gutenberg-dashboard-widgets' ) ) {
require __DIR__ . '/experimental/dashboard-widgets/load.php';
}
14 changes: 14 additions & 0 deletions package-lock.json
View file
Open in desktop

Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.

3 changes: 2 additions & 1 deletion package.json
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -34,7 +34,8 @@
"font-library",
"options-connectors",
"guidelines",
"taxonomies"
"taxonomies",
"dashboard"
]
},
"config": {
Expand Down
17 changes: 17 additions & 0 deletions routes/dashboard/package.json
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,17 @@
{
"name": "@wordpress/dashboard-route",
"version": "1.0.0",
"private": true,
"route": {
"path": "/",
"page": [
"dashboard"
]
},
"dependencies": {
"@wordpress/admin-ui": "file:../../packages/admin-ui",
"@wordpress/base-styles": "file:../../packages/base-styles",
"@wordpress/element": "file:../../packages/element",
"@wordpress/i18n": "file:../../packages/i18n"
}
}
15 changes: 15 additions & 0 deletions routes/dashboard/stage.tsx
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,15 @@
/**
* WordPress dependencies
*/
import { Page } from '@wordpress/admin-ui';
import { __ } from '@wordpress/i18n';

function Dashboard() {
return (
<Page title={ __( 'Dashboard' ) } headingLevel={ 1 }>

@simison simison Apr 23, 2026

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Not a blocker here, but I'll open a PR to change the default to 1 for pages like these.

If it merges first, we will just need to remove headingLevel and rebase.

@retrofox retrofox Apr 23, 2026

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Makes sense, h1 is the right default for a page component. I'll drop the explicit headingLevel once yours lands.

@simison simison Apr 23, 2026

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

PR: #77617

Yeah or alternatively we merge with headingLevel=1 here and I'll just update mine to remove it, whichever goes first.

<div className="dashboard-widgets" />
</Page>
);
}

export const stage = Dashboard;
Loading