Appreciate you coming on Bridge Builders, Brian! Good insights here, as well! I think the most important bit is 'what end-client are we building for'. Would love to hear/chat more about the different types and the requirements for each.

Thanks for this. Really enjoyed the behind the scenes look. I could see myself using your starter theme on some smaller projects, for sure. Also, couldn't agree more with your closing thoughts

Thanks for going on the stream and making this video. I understand your point about wanting to give clients a visual editing experience. You’re building sites for very different people than I do. My clients want to add FAQs, manage reviews, update product prices. Working in the backend with custom fields perfect for them. Kevin’s point about using custom field for the verticals is right if those verticals are going to be referenced somewhere else on the site. Otherwise you’ll need to hunt down wherever they’ve been used and update manually… like a chump 🙃. Which I’ve done plenty of that in my life.

Brian, appreciate you sharing this additional under the hood look. Will definitely be checking out your theme. I am interested in this idea of 'Curated Blocks/experiences" as I've been navigating my way around custom blocks with that overarching intention of end-user (editor) experience. In something like Bricks, client editing is made easier only by additional dependency on a 3rd party plugin on top of Bricks - powerful experience for devs and their end users alike, though the 'cons' of multiple layers of dependencies don't escape me.

Your closing remarks are spot on. We seem to get so passionate about what we (devs) think the best way to do something is and we love it when our peers agree. Human nature...everyone wants to belong to a clan. The thing is, we get paid to build stuff for people that will never be in our clan. More often than not the people we're building for don't give a flying f*#k how we build it as long as it meets their goals. Goals is where we have to start and work back from. Pick your tools based on the task at hand. Not because of some external influence.

A great summary Brian - thanks for making this video - incredibly helpful 🙏

13:00 -- Just to clarify: I didn't propose creating the CPT for the client's benefit. It was created for proper data architecture, maintainability, easier templating, easier looping, easier SEO defaults, easier URL manipulation, etc. CPTs are mandatory, imo, for these reasons. I've argued for a long time now that throwing everything in pages as if its some sort of drunk drawer for all your data is really bad practice. I only said the client could edit it easier because it's a CPT with custom fields when you asked about clients' ability to edit it.

Great content Brian. Consider extending this in two ways: 1. even though ths may not be suitable example for a cpt loop, there certainly are times where cpt loop is the right approach. How would you solve the problem then? 2. you speak about curated editing experience, but show mostly how to add items to the editor, I would love to se various ways you can remove things from the editor, and especially based on user roles / caps, and or context

Awesome video, will definitely use this theme!

I used to craft site like that, custom theme, custom code etc. I really like the idea to only use guttenberg to edit the code, but after few years I felt that my kind of clients really don't need that work, they just need the WordPress like pure CMS. They open an option page, change the info, save and that it's ok for them. Normally when they need to create a new page they asks to me even when I made a block for that. All time consumed to code was normally waste of time. For that reason I started using Bricks to keep thing more flexible when needed, to keep my projects more standarized and easy to change and only allow to client edit thing that they really need. I like to have dependecy on bricks ? No. I like to serve forms to client edit a few contents? No. I like to have different ways to edit content? Really not. But it's works to me and my clients. It's fast, it's cheap and we can focus on the business instead the code. But that works to my kind of clients, what works for me would not works for other person. It's just different.

About the CPT, my approach is: That information need an individual page e.g. /team/jorge? Then I use CPT. That information will be used in two or more places e.g. telephones, social media, address etc? Then I use an option page. If not the case it's just a content and dont need to worrie.

Thank you, Brian. Great content, very educative with relaxed explanation. I agree with your thoughts, especially on the last one. Talking about client experience, this the reason why I use Block Theme. And I can imagine what clients think when using CPT/ACF just to edit a couple cards. Most of end-users/clients don't like using WordPress because too many things going on the dashboard.

Overall Bridge was great, thx 4 all participants! Personally was more interested in Gutenberg part both cause GB is more Terra Incognita for the most and also `cause im not expected somehing new from Bricks bridge side (I very like Bricks core made on in couple sites and glad to have LTD from it). Also the ACSS is some kind very good but can't bring for me more than VSCode, also but the Frames IMO could be awesome thing tho (i tried many Bicks template libraries and all of them at the moment was not such things I could use in practice). So back to the Gutenbertg - its more hardcore tool by design, and im glad to see the appearance of more hardcore materials on it, thank you!

Thanks for the video. It did reinforced my belief in Kevin's philosophy regarding Dynamic page build approach.. purely from a marketing perspective "consider a Yoga studio promoting different events on a month to month basis or lets say seasonal...it would be so easy to manage the verticals and ton of flexibility both for the client and for the wordpress agevy or a freelancer.....I personally use Generatepress and generate blocks pro and ACF pro and i still get lot of value from kevin, Kyle and jerimy ... although they have different philosophical takes

Hey Brian, just trying to use your starter theme I downloaded from Git, but keep getting an error. I know I need to run "npm run start" but that fails because of "Error: Unknown option '--webpack-src-dir=src/blocks' " Any instructions to get it running?

Off topic as I just started watching... is that the WordPress Accessibility Day shirt?! 🙌

Brian, you're a true gent, with an open mind and an advocate for true best practices and real developer workflows. You have my utmost admiration and respect. I learn something every time I watch one of your videos. Wish I could say the same for Kevin. Im curious how you enjoy creating blocks in the theme vs a standalone plugin using wp-scripts. Im also curious if you have ever experimented with WP Rig? Finally, do you anticipate a v2 or competitor to wp-scripts on something like Vite or Bun emerging in the future?

Hey Brian would you recommend building native blocks as whole sections that way your clients will have really great user experience?

I wholeheartedly agree with everything you said in the video, especially regarding custom post types versus just creating content with blocks. Many often overcomplicate things. Since I'm also in the process of building a starter theme/design system (which will be released soon!), I find it really valuable to hear your opinions and the reasoning behind certain decisions. At 14:10, the pre-curated block style variations on the images are also the way I would have gone. The current issue with block styles is that only one is selectable. (Any updates on your plugin, by the way?)

Hi Brian, I would like to avoid using page builders and stick with Gutenberg. The only issue I find is Gutenberg is missing some good dynamic data (query) post archive blocks. What do you recommend as a good lightweight solution? Thanks.

Amazing walk-through as usual! If this were a client's project, would you create a child theme of your starter theme? From my understanding, FSE themes don't require child themes. Do I understand that correctly? Also, when is the Brian Coords block theme course coming out?

Thanks for the two videos. Gutenberg was a lot better than I expected. I agree with your choice to not make the verticals dynamic in this case, but at the same time, this kind of dynamic workflow is bread & butter for most even marginally more complex websites, and despite the work on the block bindings API I feel that in this area as well as with respect to the curation aspect of the editor, there's still a lot of conceptual work left that will inform the work going into the UI. Something that bugs me everytime - you write those verticals block styles for "core/image". But I'd really love it for those block styles only to appear when core/image is used *inside* of a specific pattern or a named block. Because you don't need them on any other core/image block and the UI gets confusing quickly if they are. Are you aware of any way to do that (yet)?

You mentioned the concept of 'locking down' the theme so that clients can't mess up their websites. Could you explain this a bit further? I understand the concept of clicking the padlocks on a selection of blocks but does it go further than this? Can't the client just unlock the blocks themselves? Curious to know more. Really insightful stuff!

Why such fuzz about which tool and which way of building websites is better? It all comes down to the project and how you, as a developer, and your client wants to handle the website. For me, building "isolated" elements and website parts was a pain in the butt. For example, I built a 18 page website with WP Bakery with no standards, no classes and going back to add or edit stuff sounds like a nightmare. This led me to search for a better and more efficient way to build websites with templates and reusable data. And I found CPT's and query loops was the best way to do this. The power of dynamic data and templating is unfathomable for maintainability. As I said, it all comes down to the project, if and how data is reused across the website and if and how you and perhaps, your clients, want to manage them. For simple brochure websites, yes, I would consider core WP and FSE. Fast, simple and away you go. But for anything more complex I would use tools like Bricks, CPT's and query loops. Creating scalable and maintainable websites is how I approach web development. Others may take another approach. Both are fine. All is fine guys. Peace!

I used Bricks builder last week and struggled to resize slider width for 2 hours. Grids are almost useless. At last gave up.

Can we please stop with this lie that current Gutenberg is save for average clients to edit pages: every client of mine that has ever changed anything on a page through Gutenberg has messed up the design. Even standard Bricks has more client control options than Core.

Kevin Geary is salesman. He doesn't do websites for clients. He sells a product and a community. He's not running an agency or makin g big project for clients. I watch his stream and he said his agency on pause. Someone that dos not even do the job is trying to push opinion no how it should be done. I mean no disrespect him but you can not tell people how should be done if your not doin it yourself.