Problem/Motivation
In #3159848: [Policy] Always install Drupal with Standard on the UI, pared down of use case specific elements (content types, node listing, commenting, theme) we are planning to remove the standard install profile and merge it with minimal to create a starter recipe. One thing that's not in the standard profile but assumes the intent of the standard profile is the default /node listing in node module, which is created as a view. This is present on Drupal sites even if they don't intend to have a simple blog like listing and some people forget to remove it or disable it.
Steps to reproduce
Install with the standard profile before and after this MR :)
Proposed resolution
- Disable the /node default listing. (Removing it would be very tricky due to lots of test dependencies)
- Rename this view from Frontpage to Promoted content.
- Add a controller that's a welcome page and set that as the front page.
- Name the page
welcome-to-drupalso it is not in the way later on even when it is not available anymore. (A more genericwelcomeroute could conflict even with existing sites). - Add text on that page based on Olivero's getting started page that tells you to set a new front page with a link to the config for it.
- Access to that routes depends on whether this path is the front page or not. It should 404 when this is not the front page anymore.. So it practically disappears when the front page is configured.
- Name the page
- Update all the tests to explicitly enable the promoted content view where they need it. Most tests also need a route rebuild so the routes become available.
- Update the Olivero nightwatch tests to test the front page instead of the /node page because the long text now appears on the front page (for testing scrolling).
Remaining tasks
Review!
User interface changes
- New default front page in the standard profile is not a node listing but a welcome page. (Minimal still has
user/loginas the front page) - Promoted content view available as disabled, don't need to disable it if you don't want to use it.
BEFORE:

AFTER:

Introduced terminology
None.
API changes
None.
Data model changes
None.
Release notes snippet
The default node listing page is not the default frontpage of Drupal's standard profile anymore. The view providing this page (and a default RSS feed) is still available but is disabled by default.
LLM disclosure
LLM was used to accelerate the development of this MR, everything was deeply reviewed though.
| Comment | File | Size | Author |
|---|---|---|---|
| #9 | Screenshot 2026-05-14 at 20.53.18.png | 445.06 KB | gábor hojtsy |
| #8 | Screenshot 2026-05-14 at 20.48.07.png | 496.06 KB | gábor hojtsy |
Issue fork drupal-3572350
Show commands
Start within a Git clone of the project using the version control instructions.
Or, if you do not have SSH keys set up on git.drupalcode.org:
Comments
Comment #2
gábor hojtsySummary was based on slack discussion with @catch, so added him to the contribution record :)
Comment #4
gábor hojtsyI should disclose that my contribution on this issue is LLM assisted (and closely reviewed).
Comment #5
gábor hojtsyRetitling new target discussed with @catch, instead of removing the view, making it disabled to start, since that lowers the required test changed significantly. It is still not the default Standard front page anymore in the MR. Will see if we get to a complete MR sooner with this. Fingers crossed.
Comment #6
gábor hojtsyI believe this is now down to a random fail :) Yay! Please review!
Comment #7
gábor hojtsyHeavy issue summary update.
Comment #8
gábor hojtsyComment #9
gábor hojtsyAdding a before screenshot too.
Comment #10
needs-review-queue-bot commentedThe Needs Review Queue Bot tested this issue. It no longer applies to Drupal core. Therefore, this issue status is now "Needs work".
This does not mean that the patch necessarily needs to be re-rolled or the MR rebased. Read the Issue Summary, the issue tags and the latest discussion here to determine what needs to be done.
Consult the Drupal Contributor Guide to find step-by-step guides for working with issues.
Comment #11
gábor hojtsyComment #12
gábor hojtsyComment #13
acbramley commentedLeft some comments
Comment #14
acbramley commentedActioned my own feedback, I used ClaudeAI to refactor the trait.
Comment #15
gábor hojtsy@acbramely: woah, thanks for the refactor, I think this makes it much easier to read and review :) Yay! I think all your changes look great.
Comment #16
gábor hojtsyAdjust parent to implementation issue from policy issue.
Comment #17
dwwNot a super thorough review, but spotted a few things I wanted to open threads about. Not worth NW over any of them.
Comment #18
needs-review-queue-bot commentedThe Needs Review Queue Bot tested this issue. The merge request has merge conflicts and cannot be merged. Therefore, this issue status is now "Needs work".
This does not mean that the patch necessarily needs to be re-rolled or the MR rebased. Read the Issue Summary, the issue tags and the latest discussion here to determine what needs to be done.
Consult the Drupal Contributor Guide to find step-by-step guides for working with issues.
Comment #19
gábor hojtsyRebased, green again! Also resolved all concerns from @phenaproxima.
Comment #20
needs-review-queue-bot commentedThe Needs Review Queue Bot tested this issue. It fails the Drupal core commit checks. Therefore, this issue status is now "Needs work".
This does not mean that the patch necessarily needs to be re-rolled or the MR rebased. Read the Issue Summary, the issue tags and the latest discussion here to determine what needs to be done.
Consult the Drupal Contributor Guide to find step-by-step guides for working with issues.
Comment #21
acbramley commentedFixed attribute