Use waiting time during install to showcase features of Drupal CMS

Created on 24 April 2025, about 1 month ago

Problem/Motivation

I tried Drupal CMS both via https://new.drupal.org/drupal-cms/trial and https://www.drupalforge.org/template/drupal-cms.

In both instances, I had a good 3 to 5 minutes waiting where the progress bar was slowly advancing. If this is done locally via DDEV the process is faster, but still takes a good minute.

We could use that time to give key information to people evaluating the tool about some of its features.

As seen below, there is a lot of whitespace during this waiting time:

Steps to reproduce

Install Drupal CMS... wait...

Proposed resolution

I think that we could add some either gifs or videos showcasing the features of Drupal CMS in that space, or even some text with images that fades in/out.

User interface changes

Add some dynamic content during the install phase.

Example: seconds 7 to 18 on this video https://youtu.be/Dw6_fBZ6D5Y?feature=shared&t=7

Configuration changes

None.

✨ Feature request
Status

Active

Component

User Experience

Created by

πŸ‡ͺπŸ‡ΈSpain fjgarlin

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Comments & Activities

  • Issue created by @fjgarlin
  • πŸ‡ΊπŸ‡ΈUnited States phenaproxima Massachusetts

    Can this wait until Drupal 11.2 is out? The reason I ask is that core changed the extension system so that a batch install like Drupal CMS's should have far fewer container rebuilds, which should result in a significant performance improvement. It won't get down to seconds or anything like that, but it might be a big enough dent that we'll want to reevaluate what to do during this wait.

  • πŸ‡¬πŸ‡§United Kingdom catch

    Agreed with #4, module install time can be reduced by 50% or more in 11.2, standard install goes from about 30-40 batch iterations down to 2. Drupal CMS has a lot more modules to install, so at least the absolute time saving should be greater, if not necessarily the percentage.

    The main waiting time that's not optimized is translation download/import (although @alexpott has been working on that recently) and default content import.

    Also cross-linking ✨ Add a non blocking batch runner Active . It would be theoretically possible to install the base recipe while showing the form with the optional recipe selection, with the submit button greyed out until the base recipe install is complete.

  • πŸ‡¬πŸ‡§United Kingdom catch

    πŸ“Œ RecipeRunner::processInstall() installs modules one by one Active is also relevant here.

  • πŸ‡¦πŸ‡ΊAustralia pameeela

    I'd love to do this, but there is no way we would be able to get it done before 11.2 anyway unfortunately.

    I also could swear there was already an issue for this! But I can't find it.

Production build 0.71.5 2024