Developer Hours: How to extend Core WordPress blocks

In this installment of Developer Hours, we explored how to extend core WordPress blocks and why this approach can be preferred over creating a custom block. Extension techniques also allow you to curate the editing experience within WordPress beyond simply adding new functionality.
The session began with a presentation on the fundamentals of block extension. Then, we covered practical examples of adding new features to existing blocks, utilizing hooks for advanced extensions, and modifying block behavior to suit your unique site requirements.
Presentation Resources » docs.google.com/document/d/1D...
---
View this video and others on WordPress.TV: wordpress.tv/2023/11/29/devel...

[@dopetag]

Wow! The learning curve for the block themes is incredibly steep!

[@ashkanahmadi]

I feel very comfortable with React and PHP but the block development seems so convoluted! I've used other page builders and they are much easier to use and build websites than using Gutenberg blocks. I know they are cleaner and faster than any other page builder but it feels ... wrong!

[@visualmodo]

Truly good video!

[@jglasshalfpool4640]

This is so over my head right now. I'm trying to get my head around developing for Wordpress block themes having previously relied on page builders but I start to struggle as soon as I need to do something that isn't there out of the box. For example right now I have two custom post types built in ACF and want to be able to setup a relationship field between them so that on a type one post we can see the related type two posts in a query loop. Setting it all up is super easy, showing the type two custom posts in a query loop on the type one post is easy... and then to add the extra step of being able to leverage that relationship field to only show the type two posts that have been associated with each type one feels like I need to learn at the very least React, PHP and how to build plugins.

[@kadimgultekin]

Great tutorial! This is exactly what I'm looking for. Thanks for everything!

[@carltongordon]

The power of the block editor is so underrated. We will rise

[@Daniel667]

Very very well explained. Thank you!

[@WordPress]

You're welcome.

[@PaweBystrzan]

Whole time I started to use Gutenberg I dream about Native Responsive API for blocks (so any block could have own native breakpoints and options to manipulate in editor rather than theme.json stuff like clamp() for fonts etc.).

[@hujth6]

thanks Nick and Ryan for the helpful content about gutenberg
i need to implement a responsive image like you showed from Aki plugin, and this video helped me better understand how to do so.
one question please, is there alternatives to making a gutenberg plugin with NO build process?
or waht i realy mean is - why use a build process and not a simple and clean workflow?
i know there are good things that comes with a build process, but also some effort and i wonder what is best in aspect of (my) developer colture

[@MrPanzerDragoon]

You need the build process in order to compile the css and js when rendering from different src files.

[@hujth6]

but if i dont need to compile do i need the build process? im trying to avoid over complications in my workflow.
for example, i use plain CSS, and not SCSS or other stuff@@MrPanzerDragoon

[@Shawn-Mosher]

@@hujth6short answer is yes. There is no workaround.

[@a99986]

27:09

[@dapowebdeveloper]

Using plugin to achieve this functionality is a NO for me. I prefer the variation or CSS override approach.

[@lpfan678]

300 lines of code to add a class to a div. What a joke WordPress development has become.