Standard profile should not include Olivero anymore, should provide guidance on how to get started

Changing parent to the 'tasks to deprecate' meta for Olivero.

The 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.

@gábor hojtsy pinged me in Slack to chime in.

From my point of view, I'm fine with not showing Olivero etc. But the screenshots seem the opposite of user friendly.

Right now, we're working with a development-first approach, with seasoned Drupal devs deciding what this welcome page will look like. However, this page will likely be shown to many first-time Drupal users (I know that they're supposed to be reaching for Drupal CMS, but this will happen).

I'd love it if a designer could rework the UI from a first-time user's perspective. That being said, that work could also occur in a followup issue, so the work here doesn't get blocked.

Thoughts from everyone else?

My ideal situation would be that we get project browser into core, so that you get to something like this, but from that you can install Drupal CMS from core, that's been my ideal situation since 2011... #1260214-10: Choose your Drupal. That's hinted at by the new text pointing people to Drupal CMS too.

Then for people that don't want that, they can uninstall project browser (or not check the option to install it in the first place) and go from the nearly blank slate.

We're not going to get to that in this issue obviously, but it might be easier to talk about what to do here if had an idea whether that's the point we want to get to or not, because that then determines how temporary what we do in-between ends up being.

This is changing the UI so tagging 'Usability'.

I very much agree with #15. The text in the Welcome message is pretty much a wall of text. That needs some attention to make it easier to scan and for someone to figure out what to do next. Therefor, also tagging, 'Needs usability review'.

The 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.

I don't think implementing whatever we want is the bottleneck now, we need to make decisions though :)

I agree with this. A properly designed welcome page should be a followup issue.

Followup created #3614228: Create proper welcome page for brand new Drupal installation

Usability review

We discussed this issue at #3612901: Drupal Usability Meeting 2026-07-31. That issue will have a link to a recording of the meeting.

The attendees at the usability meeting were benjifisher, Gábor Hojtsy, mherchel, rkoller, simohell, and the_g_bomb. I am giving them credit on this issue.

We had strong consensus that a one-time message, such as a status message that shows up once after installation, is a bad idea. If the new user

• reloads the page
• navigates away using one of the links on the page and then returns
• explores the Navigation menu
• revisits the page after a coffee break

then the message will be gone.

There are several elements of the suggested text that are not related to status, such as the links to the User Guide and upcoming events. That makes both a status message and the site Status report inappropriate places for this information.

The primary audience for this page is the new user who decided to try Drupal core despite the recommendation to start with Drupal CMS. We want to give another nudge in that direction (and perhaps scare them off with a list of next steps if they are still interested in working with Drupal core). For that purpose, a simple, dedicated page with at least one clear CTA seems like the right choice, not the Status report.

We support the suggestion in Comment #20: make a separate page for this message as part of this issue, then improve the content and design of that page in a follow-up issue.

If you want more feedback from the usability team, a good way to reach out is in the #ux channel in Slack.

The 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.

The 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.

The 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.

Suggesting some edits. Edits are in BOLD below.

Intro paragraph

Current: "The same community now ships two products built on each other. You installed Drupal Core. Here is the difference:"

Suggested: "The same community now ships two products. Drupal CMS is built on Drupal Core. You installed Core. Here is the difference:"

Core card

"Drupal Core is the platform for building custom digital experiences. It gives you strong foundations: content modeling, workflows, multilingual publishing, APIs, accessibility, and security.

CMS card

Label: FASTER START (was: EASIER START)

It gets you to a working site faster: AI-assisted setup, editorial workflows, and content governance built in, helping teams launch and maintain sites without starting from a blank canvas.

There's a weird gap to the right of the columns at large widths

Heading order is incorrect. It skips the h2's

So "Drupal Core" and "Drupal CMS" headings should be h2, and the headings underneath should be H3's

The Drupal icon doesn't properly respond to RTL

Added some code comments for the CSS.

Thanks!

I added an @file docblock to the beginning of the CSS.

Everything looks amazing from my point of view. I only went deep into the CSS, although I skimmed the rest of the code.

It works great, and as expected.

Wow, this has come a long way since I last looked at this. The new welcome page is no longer a wall of text to me. It is still packed with information but I can scan it and find the bits of interest. Thanks.

I made one small suggestion on the MR so the first paragraph has the same subject, a member of the Drupal community.

The 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.