At the moment, if you install core via the UI installer, you can choose install profiles, but not a recipe.
If you install Drupal CMS, then Drupal CMS's installer + https://www.drupal.org/project/recipe_installer_kit → takes over the installer and removes that form. But this is really a workaround for the core installer not supporting this workflow.
Core already has the standard profile as a recipe, and it's possible to install minimal or umami via drush.
So... I think we could remove the install profile selection from the installer, and if you install just core, you would get the standard install profile as a recipe. Eventually we can add project browser to core and you could install a site template/individual recipes directly from core (if we want).
If you have a distribution, you already don't get an install profile choice in the installer, because the existence of a distribution skips that set.
So the only feature this would remove would be installing arbitrary install profiles via the UI that aren't distributions, and it would still be available with drush/quickstart etc.
Active
11.0 🔥
install system
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).
I'm generally +1 for this, because I like anything that streamlines the installer and gets people up and running more quickly.
Re-titling, because pre-selected profiles (pre-filled settings.php, distributions), will still be supported. The only thing we'd be removing here is the form/step for install profile selection.