#layoutbuilder — Public Fediverse posts

I still think that #LayoutBuilder seems intrinsically antithetical to creating #Accessible #Drupal sites, prioritizing visual layout over semantic structure.

I guess some folks might be taking the time to customize the editing experience to help ensure proper heading structure and such, but overall it feels like slipping back to using HTML tables to position content instead of CSS classes based on the type of content.

I still think that #LayoutBuilder seems intrinsically antithetical to creating #Accessible #Drupal sites, prioritizing visual layout over semantic structure.

I guess some folks might be taking the time to customize the editing experience to help ensure proper heading structure and such, but overall it feels like slipping back to using HTML tables to position content instead of CSS classes based on the type of content.

I still think that #LayoutBuilder seems intrinsically antithetical to creating #Accessible #Drupal sites, prioritizing visual layout over semantic structure.

I guess some folks might be taking the time to customize the editing experience to help ensure proper heading structure and such, but overall it feels like slipping back to using HTML tables to position content instead of CSS classes based on the type of content.

I still think that #LayoutBuilder seems intrinsically antithetical to creating #Accessible #Drupal sites, prioritizing visual layout over semantic structure.

I guess some folks might be taking the time to customize the editing experience to help ensure proper heading structure and such, but overall it feels like slipping back to using HTML tables to position content instead of CSS classes based on the type of content.

Evolving Drupal’s Layout Builder to an Experience Builder. https://buff.ly/3QfI44w

Looks like Dries decided to save Paragraphs from Gutenberg.

Drupal has the details: https://buff.ly/3xTqf52

This better explains the decision and doesn’t rule out integrating Gutenberg.

Still, I am sure this will take years to come to fruition.

#drupal #LayoutBuilder

https://newsletter.mobileatom.net/layout-builder-tobecome-experience-builder/

#Drupal #LayoutBuilder

Evolving Drupal’s Layout Builder to an Experience Builder. https://buff.ly/3QfI44w

Looks like Dries decided to save Paragraphs from Gutenberg.

Drupal has the details: https://buff.ly/3xTqf52

This better explains the decision and doesn’t rule out integrating Gutenberg.

Still, I am sure this will take years to come to fruition.

#drupal #LayoutBuilder

https://newsletter.mobileatom.net/layout-builder-tobecome-experience-builder/

#Drupal #LayoutBuilder

Evolving Drupal’s Layout Builder to an Experience Builder. https://buff.ly/3QfI44w

Looks like Dries decided to save Paragraphs from Gutenberg.

Drupal has the details: https://buff.ly/3xTqf52

This better explains the decision and doesn’t rule out integrating Gutenberg.

Still, I am sure this will take years to come to fruition.

#drupal #LayoutBuilder

https://newsletter.mobileatom.net/layout-builder-tobecome-experience-builder/

#Drupal #LayoutBuilder

Evolving Drupal’s Layout Builder to an Experience Builder. https://buff.ly/3QfI44w

Looks like Dries decided to save Paragraphs from Gutenberg.

Drupal has the details: https://buff.ly/3xTqf52

This better explains the decision and doesn’t rule out integrating Gutenberg.

Still, I am sure this will take years to come to fruition.

#drupal #LayoutBuilder

https://newsletter.mobileatom.net/layout-builder-tobecome-experience-builder/

#Drupal #LayoutBuilder

Evolving Drupal's Layout Builder to an Experience Builder. https://buff.ly/3QfI44w

Looks like Dries decided to save Paragraphs from Gutenberg.

Drupal has the details: https://www.drupal.org/about/core/blog/working-toward-an-experience-builder

This better explains the decision and doesn't rule out integrating Gutenberg.

Still, I am sure this will take years to come to fruition.

#drupal #LayoutBuilder

Evolving Drupal's Layout Builder to an Experience Builder. https://buff.ly/3QfI44w

Looks like Dries decided to save Paragraphs from Gutenberg.

Drupal has the details: https://www.drupal.org/about/core/blog/working-toward-an-experience-builder

This better explains the decision and doesn't rule out integrating Gutenberg.

Still, I am sure this will take years to come to fruition.

#drupal #LayoutBuilder

Evolving Drupal's Layout Builder to an Experience Builder. https://buff.ly/3QfI44w

Looks like Dries decided to save Paragraphs from Gutenberg.

Drupal has the details: https://www.drupal.org/about/core/blog/working-toward-an-experience-builder

This better explains the decision and doesn't rule out integrating Gutenberg.

Still, I am sure this will take years to come to fruition.

#drupal #LayoutBuilder

@mikemccaffrey We routinely create custom layouts and use them within #LayoutBuilder. We also make heavy use of https://www.drupal.org/project/layout_builder_component_attributes and https://www.drupal.org/project/layout_custom_section_classes to add semantic classes to sections and blocks, for theming.

You make a great point, though -- our solution takes a lot of customization, it's not a simple thing for our clients to use. And sometimes we have to add a block just for a header.

@mikemccaffrey We routinely create custom layouts and use them within #LayoutBuilder. We also make heavy use of https://www.drupal.org/project/layout_builder_component_attributes and https://www.drupal.org/project/layout_custom_section_classes to add semantic classes to sections and blocks, for theming.

You make a great point, though -- our solution takes a lot of customization, it's not a simple thing for our clients to use. And sometimes we have to add a block just for a header.

@mikemccaffrey We routinely create custom layouts and use them within #LayoutBuilder. We also make heavy use of https://www.drupal.org/project/layout_builder_component_attributes and https://www.drupal.org/project/layout_custom_section_classes to add semantic classes to sections and blocks, for theming.

You make a great point, though -- our solution takes a lot of customization, it's not a simple thing for our clients to use. And sometimes we have to add a block just for a header.

@mikemccaffrey We routinely create custom layouts and use them within #LayoutBuilder. We also make heavy use of https://www.drupal.org/project/layout_builder_component_attributes and https://www.drupal.org/project/layout_custom_section_classes to add semantic classes to sections and blocks, for theming.

You make a great point, though -- our solution takes a lot of customization, it's not a simple thing for our clients to use. And sometimes we have to add a block just for a header.

I think #LayoutBuilder is a big step back for #Accessibility in #Drupal.

Look at the umami demo: Visually, you can see that these four blocks fit together in a section that contains metadata about the recipe, but there is no way to indicate they are a semantic section and provide an h2 title using the interface.

I think #LayoutBuilder is a big step back for #Accessibility in #Drupal.

Look at the umami demo: Visually, you can see that these four blocks fit together in a section that contains metadata about the recipe, but there is no way to indicate they are a semantic section and provide an h2 title using the interface.

I think #LayoutBuilder is a big step back for #Accessibility in #Drupal.

Look at the umami demo: Visually, you can see that these four blocks fit together in a section that contains metadata about the recipe, but there is no way to indicate they are a semantic section and provide an h2 title using the interface.

I think #LayoutBuilder is a big step back for #Accessibility in #Drupal.

Look at the umami demo: Visually, you can see that these four blocks fit together in a section that contains metadata about the recipe, but there is no way to indicate they are a semantic section and provide an h2 title using the interface.

I think #LayoutBuilder is a big step back for #Accessibility in #Drupal.

Look at the umami demo: Visually, you can see that these four blocks fit together in a section that contains metadata about the recipe, but there is no way to indicate they are a semantic section and provide an h2 title using the interface.

I still do not understand why I would ever use #LayoutBuilder in #Drupal10. It seems like a step back to the old days when we were using html tables to lay out a page, rather than starting with semantic structure and then applying styling.

I still do not understand why I would ever use #LayoutBuilder in #Drupal10. It seems like a step back to the old days when we were using html tables to lay out a page, rather than starting with semantic structure and then applying styling.

I still do not understand why I would ever use #LayoutBuilder in #Drupal10. It seems like a step back to the old days when we were using html tables to lay out a page, rather than starting with semantic structure and then applying styling.

I still do not understand why I would ever use #LayoutBuilder in #Drupal10. It seems like a step back to the old days when we were using html tables to lay out a page, rather than starting with semantic structure and then applying styling.

Explore How Symfony Station was built: an adventurous exploration of layout solutions. It’s an adventure story (aka case study) of how Symfony Station was built and the research behind each decision. It also functions as our about page. 🙂

https://symfonystation.mobileatom.net/How-Symfony-Station-Built

#Symfony #Drupal #LayoutBuilder #Gutenberg

https://newsletter.mobileatom.net/how-symfony-station-was-built/

#Drupal #Gutenberg #LayoutBuilder #symfony

Explore How Symfony Station was built: an adventurous exploration of layout solutions. It’s an adventure story (aka case study) of how Symfony Station was built and the research behind each decision. It also functions as our about page. 🙂

https://symfonystation.mobileatom.net/How-Symfony-Station-Built

#Symfony #Drupal #LayoutBuilder #Gutenberg

https://newsletter.mobileatom.net/how-symfony-station-was-built/

#Drupal #Gutenberg #LayoutBuilder #symfony

Explore How Symfony Station was built: an adventurous exploration of layout solutions. It’s an adventure story (aka case study) of how Symfony Station was built and the research behind each decision. It also functions as our about page. 🙂

https://symfonystation.mobileatom.net/How-Symfony-Station-Built

#Symfony #Drupal #LayoutBuilder #Gutenberg

https://newsletter.mobileatom.net/how-symfony-station-was-built/

#Drupal #Gutenberg #LayoutBuilder #symfony

Explore How Symfony Station was built: an adventurous exploration of layout solutions. It’s an adventure story (aka case study) of how Symfony Station was built and the research behind each decision. It also functions as our about page. 🙂

https://symfonystation.mobileatom.net/How-Symfony-Station-Built

#Symfony #Drupal #LayoutBuilder #Gutenberg

https://newsletter.mobileatom.net/how-symfony-station-was-built/

#Drupal #Gutenberg #LayoutBuilder #symfony

Explore How Symfony Station was built: an adventurous exploration of layout solutions. It's an adventure story (aka case study) of how Symfony Station was built and the research behind each decision. It also functions as our about page. :) https://symfonystation.mobileatom.net/How-Symfony-Station-Built #Symfony #Drupal #LayoutBuilder #Gutenberg

Explore How Symfony Station was built: an adventurous exploration of layout solutions. It's an adventure story (aka case study) of how Symfony Station was built and the research behind each decision. It also functions as our about page. :) https://symfonystation.mobileatom.net/How-Symfony-Station-Built #Symfony #Drupal #LayoutBuilder #Gutenberg

Explore How Symfony Station was built: an adventurous exploration of layout solutions. It's an adventure story (aka case study) of how Symfony Station was built and the research behind each decision. It also functions as our about page. :) https://symfonystation.mobileatom.net/How-Symfony-Station-Built #Symfony #Drupal #LayoutBuilder #Gutenberg

Explore How Symfony Station was built: an adventurous exploration of layout solutions. It's an adventure story (aka case study) of how Symfony Station was built and the research behind each decision. It also functions as our about page. :) https://symfonystation.mobileatom.net/How-Symfony-Station-Built #Symfony #Drupal #LayoutBuilder #Gutenberg

Explore How Symfony Station was built: an adventurous exploration of layout solutions. It's an adventure story (aka case study) of how Symfony Station was built and the research behind each decision. It also functions as our about page. :) https://symfonystation.mobileatom.net/How-Symfony-Station-Built #Symfony #Drupal #LayoutBuilder #Gutenberg

Next problem to solve: using Layout Builder on menu link content entities to make a mega menu. This works great for other menu blocks -- but for some reason a normal custom block added to the layout only shows for admins... #Drupal #LayoutBuilder

Next problem to solve: using Layout Builder on menu link content entities to make a mega menu. This works great for other menu blocks -- but for some reason a normal custom block added to the layout only shows for admins... #Drupal #LayoutBuilder

Next problem to solve: using Layout Builder on menu link content entities to make a mega menu. This works great for other menu blocks -- but for some reason a normal custom block added to the layout only shows for admins... #Drupal #LayoutBuilder