With Drupal CMS, and eventually site templates, there is a clear starting point for new Drupal users. This makes the standard profile in Drupal core less useful, especially the content types.
Similarly, the minimal install profile isn't a good starting point for anyone - the stark theme is too stark to actually use, you'd immediately have to install Claro or Gin and then some other modules, people are more likely to do this with drush than select minimal in the UI.
Meanwhile Umami is also likely to be moved to contrib via 📌 Deprecate and remove the Umami demonstration profile from core, make it a contributed site template Active , this leads towards having a single install profile/recipe to start from in core.
Install profiles can be uninstall as of a few releases ago so we have a clear upgrade path for sites that started on minimal.
Remove the 'page' and 'article' content types from the standard install profile/recipe since content types can be provided by other, optional/contrib recipes now. Deprecate the minimal install profile and mark it obsolete in Drupal 12.
Active
11.0 🔥
other
It is used to alert the product manager core committer(s) that an issue represents a significant new feature, UI change, or change to the "user experience" of Drupal, and their signoff is needed. If an issue significantly affects the usability of Drupal, use Needs usability review instead (see the governance policy draft for more information).
It is used to alert the release manager core committer(s) that an issue significantly affects the overall technical debt or release timeline of Drupal, and their signoff is needed. See the governance policy draft for more information.
Flesh out how this relates to core strategy a bit more.
@Gabor pointed out this is a duplicate of ✨ Add a basic but usable install profile for building a site from scratch Active and I think if we slightly repurpose that issue, that's true, so did that and closing this one.