Problem/Motivation
Drupal CMS and its soon to be included site templates superseded Umami. In #3523324: Deprecate and remove the Umami demonstration profile from core, make it a contributed site template we are proposing to move it to contrib and make it a site template there. However many tests are dependent on it. First we need to make it a testing only profile in core, so that we can still use it for that while that is possibly refactored.
Steps to reproduce
Proposed resolution
Make Umami a testing profile, don't show it to users.
Remaining tasks
User interface changes
Introduced terminology
API changes
Data model changes
Release notes snippet
Issue fork drupal-3526560
Show commands
Start within a Git clone of the project using the version control instructions.
Or, if you do not have SSH keys set up on git.drupalcode.org:
- 3526560-make-umami-a
changes, plain diff MR !12238
Comments
Comment #5
finnsky commentedI don't know what to say!
Comment #6
markconroy commentedMy first Drupal core maintainer project, sorry to see you go, but your time is up!
Comment #7
kjay commentedIt was amazing to have the opportunity to work with the community on Umami. It was always meant to help push Drupal toward a better out-of-the-box experience, so it’s encouraging to see that vision carried forward in Drupal CMS.
Onwards and upwards.
Comment #8
catchBetween this and #3159848: [Policy] Merge the minimal and standard install profiles into a starting point recipe it will be possible to install core from the UI without profile selection. I'm retitling for the actual scope here - seems like a good interim step until we have a contrib version. Part of moving to a test profile will probably involve disentangling the content /config from the theme.
Comment #10
godotislateCommitted 03eb694 and pushed to main. Thanks!
Comment #13
penyaskitoDoes this needs a change record? My guess is not, given it was forever experimental, but didn't see any reference in the issue.
Comment #14
gábor hojtsyI added https://www.drupal.org/node/3587286 hope that helps :)
Comment #15
quietone commentedCorrect branch on the change record.
Comment #16
gábor hojtsyComment #17
gábor hojtsyShould this be backported to Drupal 11? Even 11.4?
Comment #18
markconroy commentedI have no problem with this being backported.