Fosstodon

Mike McCaffreyI still think that <a href="https://drupal.community/tags/LayoutBuilder" class="mention hashtag" rel="nofollow noopener" target="_blank">#LayoutBuilder</a> seems intrinsically antithetical to creating <a href="https://drupal.community/tags/Accessible" class="mention hashtag" rel="nofollow noopener" target="_blank">#Accessible</a> <a href="https://drupal.community/tags/Drupal" class="mention hashtag" rel="nofollow noopener" target="_blank">#Drupal</a> 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.

Drupal Developer DaysExcited to welcome Panagiotis Moutsopoulos to <a href="https://drupal.community/tags/DrupalDevDays" class="mention hashtag" rel="nofollow noopener" target="_blank">#DrupalDevDays</a> 🥳Join Panagiotis at <a href="https://drupal.community/tags/DDD24" class="mention hashtag" rel="nofollow noopener" target="_blank">#DDD24</a> to explore <a href="https://drupal.community/tags/Drupal" class="mention hashtag" rel="nofollow noopener" target="_blank">#Drupal</a>'s philosophy of using a single module for most cases, presenting problems and their solutions with various core or contrib modules and technologies, including <a href="https://drupal.community/tags/Panels" class="mention hashtag" rel="nofollow noopener" target="_blank">#Panels</a>, <a href="https://drupal.community/tags/Context" class="mention hashtag" rel="nofollow noopener" target="_blank">#Context</a>, <a href="https://drupal.community/tags/DisplaySuite" class="mention hashtag" rel="nofollow noopener" target="_blank">#DisplaySuite</a>, <a href="https://drupal.community/tags/LayoutBuilder" class="mention hashtag" rel="nofollow noopener" target="_blank">#LayoutBuilder</a>, <a href="https://drupal.community/tags/REST" class="mention hashtag" rel="nofollow noopener" target="_blank">#REST</a>, and <a href="https://drupal.community/tags/JSONAPI" class="mention hashtag" rel="nofollow noopener" target="_blank">#JSONAPI</a>.🔗 Learn more about the BoF session at <a href="https://ddd2024.drupalcamp.bg/drupal-dev-days-2024/session/drupals-alternate-realities" rel="nofollow noopener" target="_blank">https://ddd2024.drupalcamp.bg/drupal-dev-days-2024/session/drupals-alternate-realities</a>

S.S.S. PayloadEvolving Drupal’s Layout Builder to an Experience Builder. <a href="https://buff.ly/3QfI44w" rel="nofollow noopener" target="_blank">https://buff.ly/3QfI44w</a>Looks like Dries decided to save Paragraphs from Gutenberg.Drupal has the details: <a href="https://buff.ly/3xTqf52" rel="nofollow noopener" target="_blank">https://buff.ly/3xTqf52</a>This better explains the decision and doesn’t rule out integrating Gutenberg.Still, I am sure this will take years to come to fruition.<a rel="nofollow noopener" class="hashtag u-tag u-category" href="https://newsletter.mobileatom.net/tag/drupal/" target="_blank">#drupal</a> <a rel="nofollow noopener" class="hashtag u-tag u-category" href="https://newsletter.mobileatom.net/tag/layoutbuilder/" target="_blank">#LayoutBuilder</a><a href="https://newsletter.mobileatom.net/layout-builder-tobecome-experience-builder/" class="" rel="nofollow noopener" target="_blank">https://newsletter.mobileatom.net/layout-builder-tobecome-experience-builder/</a><a rel="nofollow noopener" class="hashtag u-tag u-category" href="https://newsletter.mobileatom.net/tag/drupal/" target="_blank">#Drupal</a> <a rel="nofollow noopener" class="hashtag u-tag u-category" href="https://newsletter.mobileatom.net/tag/layoutbuilder/" target="_blank">#LayoutBuilder</a>

Symfony Station 🇺🇦🇨🇦🇧🇷Evolving Drupal's Layout Builder to an Experience Builder. <a href="https://buff.ly/3QfI44w" rel="nofollow noopener" target="_blank">https://buff.ly/3QfI44w</a> Looks like Dries decided to save Paragraphs from Gutenberg. Drupal has the details: <a href="https://www.drupal.org/about/core/blog/working-toward-an-experience-builder" rel="nofollow noopener" target="_blank">https://www.drupal.org/about/core/blog/working-toward-an-experience-builder</a> This better explains the decision and doesn't rule out integrating Gutenberg.Still, I am sure this will take years to come to fruition.<a href="https://drupal.community/tags/drupal" class="mention hashtag" rel="nofollow noopener" target="_blank">#drupal</a> <a href="https://drupal.community/tags/LayoutBuilder" class="mention hashtag" rel="nofollow noopener" target="_blank">#LayoutBuilder</a>

Reuben WalkerEvolving Drupal's Layout Builder to an Experience Builder. <a href="https://buff.ly/3QfI44w" rel="nofollow noopener" translate="no" target="_blank">https://buff.ly/3QfI44w</a> Looks like Dries decided to save Paragraphs from Gutenberg. Drupal has the details: <a href="https://www.drupal.org/about/core/blog/working-toward-an-experience-builder" rel="nofollow noopener" translate="no" target="_blank">https://www.drupal.org/about/core/blog/working-toward-an-experience-builder</a> This better explains the decision and doesn't rule out integrating Gutenberg.Still, I am sure this will take years to come to fruition.<a href="https://me.dm/tags/drupal" class="mention hashtag" rel="nofollow noopener" target="_blank">#drupal</a> <a href="https://me.dm/tags/LayoutBuilder" class="mention hashtag" rel="nofollow noopener" target="_blank">#LayoutBuilder</a>

Freelock<a href="https://drupal.community/@mikemccaffrey" class="u-url mention" rel="nofollow noopener" target="_blank">@mikemccaffrey</a> We routinely create custom layouts and use them within <a href="https://drupal.community/tags/LayoutBuilder" class="mention hashtag" rel="nofollow noopener" target="_blank">#LayoutBuilder</a>. We also make heavy use of <a href="https://www.drupal.org/project/layout_builder_component_attributes" rel="nofollow noopener" target="_blank">https://www.drupal.org/project/layout_builder_component_attributes</a> and <a href="https://www.drupal.org/project/layout_custom_section_classes" rel="nofollow noopener" target="_blank">https://www.drupal.org/project/layout_custom_section_classes</a> 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.

Mike McCaffreyI think <a href="https://drupal.community/tags/LayoutBuilder" class="mention hashtag" rel="nofollow noopener" target="_blank">#LayoutBuilder</a> is a big step back for <a href="https://drupal.community/tags/Accessibility" class="mention hashtag" rel="nofollow noopener" target="_blank">#Accessibility</a> in <a href="https://drupal.community/tags/Drupal" class="mention hashtag" rel="nofollow noopener" target="_blank">#Drupal</a>. 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.

Mike McCaffreyI still do not understand why I would ever use <a href="https://drupal.community/tags/LayoutBuilder" class="mention hashtag" rel="nofollow noopener" target="_blank">#LayoutBuilder</a> in <a href="https://drupal.community/tags/Drupal10" class="mention hashtag" rel="nofollow noopener" target="_blank">#Drupal10</a>. 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.

S.S.S. PayloadExplore 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. 🙂 <a href="https://symfonystation.mobileatom.net/How-Symfony-Station-Built" rel="nofollow noopener" target="_blank">https://symfonystation.mobileatom.net/How-Symfony-Station-Built</a> <a rel="nofollow noopener" class="hashtag u-tag u-category" href="https://newsletter.mobileatom.net/tag/symfony/" target="_blank">#Symfony</a> <a rel="nofollow noopener" class="hashtag u-tag u-category" href="https://newsletter.mobileatom.net/tag/drupal/" target="_blank">#Drupal</a> <a rel="nofollow noopener" class="hashtag u-tag u-category" href="https://newsletter.mobileatom.net/tag/layoutbuilder/" target="_blank">#LayoutBuilder</a> <a rel="nofollow noopener" class="hashtag u-tag u-category" href="https://newsletter.mobileatom.net/tag/gutenberg/" target="_blank">#Gutenberg</a><a href="https://newsletter.mobileatom.net/how-symfony-station-was-built/" rel="nofollow noopener" target="_blank">https://newsletter.mobileatom.net/how-symfony-station-was-built/</a><a rel="nofollow noopener" class="hashtag u-tag u-category" href="https://newsletter.mobileatom.net/tag/drupal/" target="_blank">#Drupal</a> <a rel="nofollow noopener" class="hashtag u-tag u-category" href="https://newsletter.mobileatom.net/tag/gutenberg/" target="_blank">#Gutenberg</a> <a rel="nofollow noopener" class="hashtag u-tag u-category" href="https://newsletter.mobileatom.net/tag/layoutbuilder/" target="_blank">#LayoutBuilder</a> <a rel="nofollow noopener" class="hashtag u-tag u-category" href="https://newsletter.mobileatom.net/tag/symfony/" target="_blank">#symfony</a>

Symfony Station :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. :) <a href="https://symfonystation.mobileatom.net/How-Symfony-Station-Built" rel="nofollow noopener" translate="no" target="_blank">https://symfonystation.mobileatom.net/How-Symfony-Station-Built</a> <a href="https://phpc.social/tags/Symfony" class="mention hashtag" rel="nofollow noopener" target="_blank">#Symfony</a> <a href="https://phpc.social/tags/Drupal" class="mention hashtag" rel="nofollow noopener" target="_blank">#Drupal</a> <a href="https://phpc.social/tags/LayoutBuilder" class="mention hashtag" rel="nofollow noopener" target="_blank">#LayoutBuilder</a> <a href="https://phpc.social/tags/Gutenberg" class="mention hashtag" rel="nofollow noopener" target="_blank">#Gutenberg</a>

Florida☀DrupalCampHave you seen our rad training lineup?<a href="https://drupal.community/tags/Agile" class="mention hashtag" rel="nofollow noopener" target="_blank">#Agile</a>, <a href="https://drupal.community/tags/LayOutBuilder" class="mention hashtag" rel="nofollow noopener" target="_blank">#LayOutBuilder</a>, <a href="https://drupal.community/tags/Figma" class="mention hashtag" rel="nofollow noopener" target="_blank">#Figma</a>, Getting started with <a href="https://drupal.community/tags/Drupal" class="mention hashtag" rel="nofollow noopener" target="_blank">#Drupal</a>, and even some Module Development.Training day is Friday Feb 24 <a href="https://www.fldrupal.camp/trainings" rel="nofollow noopener" target="_blank">https://www.fldrupal.camp/trainings</a> <a href="https://drupal.community/tags/FLDC24" class="mention hashtag" rel="nofollow noopener" target="_blank">#FLDC24</a>

FreelockNext 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... <a href="https://drupal.community/tags/Drupal" class="mention hashtag" rel="nofollow noopener" target="_blank">#Drupal</a> <a href="https://drupal.community/tags/LayoutBuilder" class="mention hashtag" rel="nofollow noopener" target="_blank">#LayoutBuilder</a>

Recent searches

Search options

Administered by:

Server stats:

#LayoutBuilder