Problem/Motivation

Media is stable. Let's showcase its capabilities in the Umami demo!

Proposed resolution

Consider each of the types of media supported in Drupal core for use in Umami in their respective sub-issues.

Remaining tasks

* Decide what Media features we should implement.
* Decide where this feature would improve the demo.

User interface changes

None in this parent issue.

CommentFileSizeAuthor
article-now.png32.87 KBckrina
article-media.png64.25 KBckrina

Comments

ckrina created an issue. See original summary.

ckrina’s picture

ckrina
she/her
Primary language Catalan
Location Barcelona
commented
Title: Consider showcasing MEdia module in Umami Demo Profile » Consider showcasing Media module in Umami Demo Profile
eli-t’s picture

eli-t
he/him
Primary language English
Location Manchester
commented

I think we should definitely move to media, thanks @ckrina for this.

I'm not convinced we should implement a fallback here though. We don't AFAIK have fallback behaviours for any other core modules on which we rely (open to being wrong about this). So some questions.

  1. What makes media so special we should implement some fallback here?
  2. This could cause users to think that there is some magic in core that lets media automatically fallback to file fields. This is a dangerous perception - how do we counter that?
  3. If we do implement a fallback here, are there other modules we are already dependent on that also require fallback?
  4. What should the policy be going forward with respect to fallback behaviours?
eli-t’s picture

eli-t
he/him
Primary language English
Location Manchester
commented
Related issues: +#2936841: Remove images from demo_umami profile and download upon installation instead

We should also consider the abilities Media gives us over just swapping out the file image fields for media image fields. For instance, should we consider including audio/video instructions for some of the recipes? If we do I'd strongly suggest we don't make it mandatory, as that is too high a barrier to impose on adding new recipes. If we do want to add audio/video and we have the capability to generate audio/video of sufficient standard, I imagine we will have to download it at install time as has been proposed for the recipe images. Therefore linking #2936841: Remove images from demo_umami profile and download upon installation instead

eli-t’s picture

eli-t
he/him
Primary language English
Location Manchester
commented
Title: Consider showcasing Media module in Umami Demo Profile » [META] Showcasing Media module in Umami Demo Profile
Issue summary: View changes

Version: 8.6.x-dev » 8.7.x-dev

Drupal 8.6.0-alpha1 will be released the week of July 16, 2018, which means new developments and disruptive changes should now be targeted against the 8.7.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.7.x-dev » 8.8.x-dev

Drupal 8.7.0-alpha1 will be released the week of March 11, 2019, which means new developments and disruptive changes should now be targeted against the 8.8.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

webchick’s picture

webchick
she/they
Primary language English
Location Vancouver 🇨🇦
commented
Related issues: +#3086965: Allow embedding media in CKEditor in Umami, +#2954378: Use Media images in Umami demo

I was testing #2954378: Use Media images in Umami demo (which worked GREAT, btw!) to assist with testing #3081587: Multilingual content is shown double in the media library view and noticed a missing feature, which is that as of 8.8 we now have the ability to embed media within CKEditor. It would be really cool if Umami showed off this capability. I spun off an issue to discuss it at #3086965: Allow embedding media in CKEditor in Umami.

Version: 8.8.x-dev » 8.9.x-dev

Drupal 8.8.0-alpha1 will be released the week of October 14th, 2019, which means new developments and disruptive changes should now be targeted against the 8.9.x-dev branch. (Any changes to 8.9.x will also be committed to 9.0.x in preparation for Drupal 9’s release, but some changes like significant feature additions will be deferred to 9.1.x.). For more information see the Drupal 8 and 9 minor version schedule and the Allowed changes during the Drupal 8 and 9 release cycles.

Version: 8.9.x-dev » 9.1.x-dev

Drupal 8.9.0-beta1 was released on March 20, 2020. 8.9.x is the final, long-term support (LTS) minor release of Drupal 8, which means new developments and disruptive changes should now be targeted against the 9.1.x-dev branch. For more information see the Drupal 8 and 9 minor version schedule and the Allowed changes during the Drupal 8 and 9 release cycles.

Version: 9.1.x-dev » 9.2.x-dev

Drupal 9.1.0-alpha1 will be released the week of October 19, 2020, which means new developments and disruptive changes should now be targeted for the 9.2.x-dev branch. For more information see the Drupal 9 minor version schedule and the Allowed changes during the Drupal 9 release cycle.

Version: 9.2.x-dev » 9.3.x-dev

Drupal 9.2.0-alpha1 will be released the week of May 3, 2021, which means new developments and disruptive changes should now be targeted for the 9.3.x-dev branch. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

Version: 9.3.x-dev » 9.4.x-dev

Drupal 9.3.0-rc1 was released on November 26, 2021, which means new developments and disruptive changes should now be targeted for the 9.4.x-dev branch. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

Version: 9.4.x-dev » 9.5.x-dev

Drupal 9.4.0-alpha1 was released on May 6, 2022, which means new developments and disruptive changes should now be targeted for the 9.5.x-dev branch. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

Version: 9.5.x-dev » 10.1.x-dev

Drupal 9.5.0-beta2 and Drupal 10.0.0-beta2 were released on September 29, 2022, which means new developments and disruptive changes should now be targeted for the 10.1.x-dev branch. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

Version: 10.1.x-dev » 11.x-dev

Drupal core is moving towards using a “main” branch. As an interim step, a new 11.x branch has been opened, as Drupal.org infrastructure cannot currently fully support a branch named main. New developments and disruptive changes should now be targeted for the 11.x branch, which currently accepts only minor-version allowed changes. For more information, see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

Version: 11.x-dev » main

Drupal core is now using the main branch as the primary development branch. New developments and disruptive changes should now be targeted to the main branch.

Read more in the announcement.