Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.Problem/Motivation
Umami has a complex layout for the Recipe content type. So far, it has been addressed with custom markup in the twig file.
The requirements for a core theme to support the potential for fields to be moved around by a user via the manage display settings for the recipe content type were discussed. Some potential issues:
- But it has been discarded so far because the Field Layout module is experimental.
- We may not be able to produce styling that will always look great given the repositioning of a field.
- The module could be disabled while the user is testing Drupal.
Attached is a screenshot of a prototype layout that supports this approach for recipe content type. This issue covers work on theming out the recipe content type's layout using this method ready for review.
Proposed resolution
It would be great to have addressed the integration with Field Layout when it becomes stable to be able to showcase it.
One approach discussed was to have a simple and one-column alternative design as a fallback if the module is disabled.
Remaining tasks
To define.
User interface changes
To define.
| Comment | File | Size | Author |
|---|---|---|---|
| manage-display-layout.png | 137.99 KB | ckrina | |
| full-recipe.jpg | 1.51 MB | ckrina | |
| recipe-layout.png | 992.86 KB | ckrina |
Comments
Comment #2
ckrinaComment #3
Eli-T@ckrina with respect to
I don't think we should worry about that when it comes to adding new capabilities to Umami. There are already a large number of modules which if uninstalled will cause Umami to 'break' in some way. We shouldn't shy away from using new stable additions to core where appropriate in case people go and turn them off. In fact, if they do go and turn them off, they will see the resultant changes and learn from them!
Comment #4
ckrinaMy developer side agrees with you, but if I'm trying to place myself in a Drupal evaluator position I'd expect Drupal to not "break" with something like this. Of course we can't assure Drupal will work with each combination of modules, but I think this one is really isolated and """"easily"""" solvable.
Comment #5
markconroy CreditAttribution: markconroy as a volunteer and at Annertech commentedComment #6
mariohernandez CreditAttribution: mariohernandez as a volunteer and commented@ckrina I think if we build the recipe page using the component based approach we can help things from breaking if fields get moved around. Let me know if this is something I can help with.
Comment #7
Eli-TComment #8
Eli-TNote that with respect to the discussion in #3 and #4, now we have #2952888, we can mandate the user is prevented from disabling specific modules if we so desire.
This is just for info, I'm not saying we should or shouldn't do that at this point - will raise a separate issue to discuss how/if we exploit that.
Comment #9
Eli-TComment #10
markconroy CreditAttribution: markconroy as a volunteer and at Annertech commentedI'm setting this as postponed.
I don't see it as a feature we are going to work on in order to get Umami unhidden.
I'm very happy for us to work on this straightaway then, as I do think it's a feature we should support, so the only reason it is being postponed is so we can focus as must as possible on the items that help us get unhidden.
I am attaching the 'Umami new feature' tag to this item.
Comment #12
Eli-TFollowing discussion with @tedbow at DrupalEurope, it appears Field Layout's capabilities for laying out content are duplicated by Layout Builder. Layout Builder is going to be the more supported option, with Field Layout being potentially deprecated or being targeted specifically at layout of fields in edit forms rather than display. That by itself does not seem something to prioritise demonstrating in Umami, so closing this ticket.