- Issue created by @yabikami
- 🇺🇸United States scottsawyer Atlanta
Looking at the other two issues, I agree with the conclusion of the Bootstrap Layout Builder issue. I feel like layouts should be "pure" in that there is no mixing of layout definitions and the content they hold.
Creating layouts is a fairly simple process → , I feel like what you want is a custom layout, and it would be a better idea to create a custom layout than add the layer of complexity that many users may not need (I know I am not interested in this feature). Additionally, it's totally subjective as to the exact feature set that would be desired.
That being said, I am not a maintainer, so maybe this feature is more exciting to someone who is.
- 🇦🇹Austria hudri Austria
I can't see any need for this at all. If you need a title field and/or link field, any user can do this in the GUI. Contrary to the other modules - because this module is based upon paragraphs - you don't even need custom YAML config, it is mouse-clickable within field UI and display modes.
Layouts are not fieldable, Paragraphs are inside Layout so you can't talk about field here.
You can achieve this by creating a heading component. but it can be good if there is a way to add it to the section layout configuration.- 🇦🇹Austria hudri Austria
Layout paragraphs are fieldable. They are normal paragraphs with an additional behavior field which stores the layout informaiton.
Understood, but your solution doesn't conform to layout logic. For example, if you were to add a field for a title, it would end up outside the section container. Consequently, styles like padding and background won't be applied to the title because it won't be a child of the layout section.
The only simplest and viable solution for me at the moment is to create a separate paragraph bundle. If you have any other solutions, I'd appreciate hearing them.Thank you (Merci).
- Status changed to Closed: works as designed
over 1 year ago 3:31pm 30 June 2023 - 🇺🇸United States justin2pin
Thanks for the detailed feature request and all the discussion here. Ultimately this functionality doesn't belong in this module... there are several other ways to handle this using other fully-developed systems in Drupal (custom fields, the theme layer, custom layout plugins, layout templates, etc.).
I'm closing this as "works as designed".