I notice from this and another video that it's hard for viewers to see the direct benefit of this initiative..and indeed there might not be one for them, if their classic theme and plugin stack already does what they need. But it was worth watching just to hear David get excited at the end 😅
This seems more complicated then needed … isn’t the layout on the Team member already the content layout (embed in index or a template one can use the design with post content). I would rather use the fields in a archive or loop to avoid having two design sources of not needed. I might be overlooking something, but that seems much easier.
@@DavidMcCan Me too, just that renders the layout in the content type itself somewhat redundant. Seems like this was only an experiment... after all. let's see if it makes it to org.
Historic. Could it be? Thanks so much for sharing this!!! Important!
I notice from this and another video that it's hard for viewers to see the direct benefit of this initiative..and indeed there might not be one for them, if their classic theme and plugin stack already does what they need.
But it was worth watching just to hear David get excited at the end 😅
there is not "ui create block bindings" in Gutenberg Exp any more
Yes, it remains to be seen if they even push it as a plugin ... sad as a lot of people got excited about it.
This seems more complicated then needed … isn’t the layout on the Team member already the content layout (embed in index or a template one can use the design with post content). I would rather use the fields in a archive or loop to avoid having two design sources of not needed. I might be overlooking something, but that seems much easier.
I like that you can override the layout and use the blocks in a template.
@@DavidMcCan Me too, just that renders the layout in the content type itself somewhat redundant. Seems like this was only an experiment... after all. let's see if it makes it to org.