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: Adjust the design of welcome page and icon 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.

Should we use an in-brand drop icon in the main menu? The current drop is not actually following our brand guidelines. Also, can we get rid of the left border with border-radius? It looks AI generated.

Looking at the content, linking to https://www.drupal.org/project/project_theme is pretty unhelpful for picking a layout tool. I think the steps themself make sense, but we need to have a better place where we send users to for this.

I'm fine with merging this so long as we have the proper follow-ups created. Number 1 & 3 being the highest priority.

Looks very Claro-y now!

I'm going to push some CSS tweaks to make it work with Claro (like it already does) and also default_admin (when it exists) - including dark mode.

Added CSS tweaks that 1) Keep Claro looking the same, and 2) Support the new default_admin theme and its dark mode.

Love the work here with the messaging panels! I think this is a cool way to introduce people to the concepts we're trying to communicate with the split between Core and CMS.

My core concerns here are:

1. Verbosity: it is a fair bit of verbiage to communicate the ideas expressed here. With the Core / CMS shift happening fairly rapidly, I would be concerned that this messaging would get stale or decoupled from whatever the latest news is and would require frequent updates to keep it up to date. Is it possible to reduce the verbiage and / or externalize these ideas to a page on drupal.org?
2. Audience: who exactly is this for? A person who is installing Core kinda has to go out of their way in order find core, download it, set it up, and get it configured properly. Hence: it's a system for professional users who already know what they're about. How valuable is a landing page like this to those users?
3. Message: in a follow up to the above, by assuming that the audience is inexperienced and needing to be told what CMS and Core are, the mere presence of this messaging does kind of imply that the user probably messed up and installed the wrong thing.

I don't hate the idea of explaining: hey, you just installed this thing, here's what it is, good job, but the current state kinda feels like it's for the wrong group of folks.

I agree with you on point 1, and kind of on point 3.

That being said, we could iterate on this all day, and it still wouldn't be perfect. We should do that in a followup #3614228: Adjust the design of welcome page and icon for brand new Drupal installation.

What we have here is decent and significantly better than sending people to /user with a status message, which is what currently happens.

Yes agreed we should go ahead here and work on the page more in #3614228: Adjust the design of welcome page and icon for brand new Drupal installation. I think experienced users will just ignore this, which they already do for the existing welcome message, so for me it's OK if it's introductory.

Logo

Please remove the Drupal gray logo (top-right), as it looks like an after-taught. We already display a smaller logo in the navigation bar.

If you still want to display a large Drupal logo, put it in the title bar, floated to the right.

Welcome to Drupal Core [logo]

Theme

Based on what I see, once installed, will we be able to install a theme made for Drupal 11 and use it?

For example, after I install Drupal Core and the new Welcome guidance page is shown, going to Appearance and enabling a custom theme will still work?

Impressive on all accounts!

We are rapidly running out of time

When are alphas planned for 11.5.x and 12.0.x? Do we have a ticket to track the upcoming Drupal Core 12.0.x alpha release?

Looking good! Tests passing. All feedback addressed.

Gave this a manual run through and it looks great! I wasn't expecting to see the 'uninstall the standard profile' link but that's a nice touch as a different way to get rid of the page.

One question that came up for me is what happens when standard profile is a recipe and can't ship code, but I think in that case we can have a 'welcome' module or something that can be uninstalled that does the same thing. We can tackle that as part of deprecating install profiles which still has quite a few steps to go.

Not qualified to review the CSS here but people who are have done so, everything else looks fine and this is all @internal code so we can shift things around over time.

This was something I mentioned offhand in an in-person meeting at DrupalCon Vienna and it is absolutely wild to see it come to fruition less than a year later.

I think it will be a bit of a surprise for experienced users who install standard still sometimes (even if only to see what it looks like), but it should hopefully make things a lot more coherent for newer users who don't remember how it all looked like with Bartik and Garland etc.

Committed/pushed to main, thanks!

Will need a backport MR for 11.5 - part of me wonders if we shouldn't make this 12.x only though although there's no technical reason not to backport it to 11.5

Tagging for release highlights. I considered whether it needs a change record, and I don't think it really does because it only impacts new sites that install standard.

I suggest not to backport to 11.5 as I consider that change too big.

Also, I always use the Standard install profile on all Drupal installation. Removing that profile and Claro should happen only in Drupal 12, where it is expected to see big changes and removals.

Changing status to fixed.

Not sure if I have an opinion on that, but fwiw, #3572350: Disable the default /node listing view, replace Olivero hardcoded welcome page from /node with welcome message hasn't been backported yet, so might want to finish that first?

Will also conflict heavily with #3618432: Performance tests: Move expected metrics and queries to files, for better diffs and automated updates, but once that is in, further rebases will be much easier, so I'll push that and will try to land in 11.x asap.