Years ago I tried WP. I developed a site locally, which I wanted to migrate online. Then I realised, that the url from my local installation is stored directly in the database. WTF? A system, that is so widespread and popular stores it url into the database? Ok, I learned, that there a bunch of plugins, where you can change this. But other (normal) cms has mostly a config file, where you define the url. WP is something like a primitive blogging tool, wich needs a lot of plugins, to get some useful functions.

I’m using WebStudio now.

Hi Paul, I'd like to know how to restrict posts based on your role as a brick builder. I only trust you.

Very nice, but that video inset is really badly placed here. Could we not do completely without it for full dev screen shots?

At the end of the video, you change the title and the button appearances within their common CSS classes. Therefore, it would have changed in exactly the same way even if it weren’t a "component" but just a regular template where every element has its own CSS class. I still don’t fully understand what real advantage components have over using templates with CSS classes.

I agree with almost everything. Gutenberg is a distraction - it should have remained a plugin. Improving the core should be the priority. I made my first contribution to WP core by improving performance, simplifying code, and removing legacy issues from PHP 5.2. It passed all unit tests, and there was no downside to including it in the core. So why isn’t it there anymore? Well, I presume there isn’t enough qualified manpower in the WP core team to review and implement it - they’re too distracted by FSE. Knowing this, do you think I’m motivated to contribute more? Nope! There are so many things that could help develop a better and faster WP - like a constant WP_REQUEST_TYPE so developers can decide what part of their code to include for specific requests (AJAX, back-end, front-end). Features like SQLite support with a storage folder, and a simple Redis function to access it without relying on object cache plugins, would help a lot and I could go on and on... Refocusing on the long-term priorities of WP is crucial - but even more important is whether our well-considered and refined ideas, as a community, are taken into account when important decisions are made.

The components are great. Although they look basic, but I think in many cases, we can use them in addition to ACF like for custom fields like a link, so this expands the possible usecases in our workflow. I hope Bricks team make it even better with more elements, nested components, or as Kevin said with presets, so we can define presets of a component and select a preset after adding a component. Really happy about using bricksbuilder as my main tool in wordpress web design projects.

I just moved to JS frameworks, such As react and everything that goes with it and it was a huge learning curve and a massive step up but I honestly can’t look back. Wordpress actually really sucks. I like how I was able to build things relatively fast But it is just this clunky, slow, political inconsistent, sometimes even really unreliable trash that I’m so glad to put behind me I just I’m sad that I wasted six years of my life, learning WordPress.

Are there any size limits on the wpvivid?

Excellent job!!!

I was so frustrated with using ACF especially with Elementor. This video is a revelation, thank you so much

My favorite 4 wordpressers!

Gutenberg is boring and not easy to use.

I love to hear the connecting with family/less time working. ❤ I can't understand for the life of me why anyone would spend more time working than time with those they love? What's the income for, if not to use it within your circle? And what's the point of the income, if you lose the time to spend with your circle? I always think of the fisherman living his best life. Business guy tries to talk him into expanding so he can eventually have time to himself. Fisherman says, I'm doing that now. 🙂

I use the free version for a hacked website (Bricks...) and it doesn't do anything. It's way too expensive and the free version just shows you, that your site is hacked, but doesn't offer any help to clean it. You can't even review the files and scripts that are malicious. It's pretty much useless.

Open source is important when you want to migrate a site to a new server. I get about 20 clients every year who are leaving their designer and want to host with me. If their site isn’t open source then we can’t migrate their site. Besides that, I agree open source is not that big a deal. As for Wordpress, Gutenberg was the final straw. Huge step backward. I absolutely hate Gutenberg. My company strictly uses Elementor. I have tried Wix and Squarespace and haven’t been impressed. I think there is room for “the next” builder. And I can’t wait.

🔧 What are Global Classes? Reusable Code: Global classes are reusable pieces of code in your website's stylesheet that define styles for elements across your entire site. Style Templates: They act like style templates for consistent design. For instance, a class called button can define styles like background color and text size. 🕒 Benefits of Using Global Classes Consistency: Define styles once, apply them everywhere, ensuring a consistent design across the site. Easier Updates: Change the style in one place, and it reflects everywhere the class is used. Time-Saving: Reduces the need to rewrite styles for different elements. 🎨 Practical Example of Global Classes Creating a Class: To create a global class, select an element, click to create a class, and style it (e.g., btnPrimary). Real-Time Updates: Changing the style of btnPrimary updates all buttons using that class instantly. 🔄 Instance Overrides CSS Specificity: If you want to change styles for a specific instance (like making one button larger), simply deselect the global class to override it. 📦 BEM Naming Convention BEM Methodology: Use BEM (Block Element Modifier) naming for better organization. For example, a card can have classes like CardHeading for its heading. Standardization: This helps maintain a standardized naming system for team collaboration. 🛠️ Utility Classes Single Function Classes: Utility classes (like Shadow SM) apply specific styles, such as drop shadows, across different elements. Methodical Use: While useful, be cautious of overusing utility classes to avoid clutter. 📋 Managing Global Classes Classes and Variables Manager: Bricks Builder includes a Classes and Variables Manager for organizing, renaming, or deleting classes. Export/Import Options: You can easily export classes for use in different projects. 💡 Key Benefits Recap Consistency: Ensures a uniform design across all pages. Efficiency: Allows for quick adjustments site-wide. Flexibility: Facilitates testing and implementing design changes effortlessly. 🔗 Further Learning CSS Variables: For enhanced flexibility, consider learning about CSS variables alongside global classes.

🔍 Introduction to Components in Bricks Builder The video presents a first look at the beta release of the component feature in Bricks Builder 1.2. Important note: Do not use this beta feature on live sites due to potential bugs and inconsistencies. 🧩 What are Components? Components provide a hybrid approach to templates, allowing for dynamic updates from a central location. Unlike traditional templates, components enable multiple instances to reflect changes site-wide. ⚙️ Creating and Managing Components Demonstration involves converting a call to action card into a component. Users can save components with options for naming, organizing, and adding descriptions. The interface changes to indicate the component's status, with purple sections denoting components. 🔄 Editing Components Users can edit individual components and see changes reflected in all instances. The video showcases the ability to update text and other properties, demonstrating real-time synchronization across instances. 🛠️ Customizing Component Properties Components can have editable properties such as text, images, and icons. Users can create properties that allow customization while maintaining the overall design. Example: Changing text content and images while keeping the component's structure intact. 🌐 Global Changes and Flexibility Changes made to the component's design (like color and typography) reflect across all instances. This feature enhances flexibility, allowing for custom content alongside global design updates. 💬 User Feedback and Future Enhancements The creator seeks viewer feedback on the components feature, asking for opinions on its utility and potential improvements. The video mentions the need for more property types in future updates. 📊 Conclusion The component feature introduces a more flexible and powerful way to manage designs in Bricks Builder compared to traditional templates.

Nice video. Two things, I don't know anyone who likes fse and I know just as many or more who hate Gutenberg as clunky , unintuitive, and just a headache. Gutenberg alone has been the dealbreak for many and a real boon for WordPress competitors who gained new users. Of course there are Elementor, Beaver Builder, etc., and every so-called Guru tells us not to use them, just suffer with Gutenturd.

Is it possible to add an ’empty’ box in the wordpress backend for indivudual custom code to be added? ie - for schema to be added on Woocommerce product category ‘pages’

This was/is an excellent more personal talk. Really enjoyed listening in. So many good points about how to create value while you teach. Thank you both for your great contributions - luckily you are still sharing your knowledge.

i am working for years now only on my own wordpress site to present my artwork. wordpress was always nice and easy to use, but then came some new editor, blocks and gutenberg and what ever, and i must say since then i hate wordpress. these stupid blocks drive me crazy, so yesterday i returned to the twenty seventeen theme 😅 just to get a site that works and is understandable for me. my paintings i present in a linked PDF, to avoid to work with wordpress. i think a lot of "hobby web designer" will leave wordpress because it has become so difficult and too complex for them. in germany we call that "verschlimmbessern", make something good worse and worse because the developers have to come up with some new stuff from time to time, right?

Nice one fellas!

Thank you for this video, Paul.

I think what needs to be done is have a base engine that includes the core engine , with out of the box support fo creating custom fields same as Acf, and based on that you can create pages, posts or any other content type you need, how you display the content is based on a different section that you create the layouts and designs, seo, multi language settings should be part of the core , i need to write my thoughts and see how i can come up with a complete software solution to use

Is this feature similar to gutenbricks? The thing is i have been eying WordPress ,Bricks, and Acf to use as platform for clients but how is it possible to simplify providing the site after it is ready for customers but without having them learn how to use bricks to simply open a new page simply to choose a layout, insert their desired blocks update the text, image or any other information and publish

I am trying to do this but when I click on admin for the staging site i can't access. When I click on the URL for staging site I get a message saying major error on this site?

Ive missed that accent

I only use Gutenberg for writing and don't really mess with any design aspects. Design is handled through Bricks. Don't touch FSE.

There are a few issues that really stand out to me as indicators of a larger issues. First, active support for PHP 8.2 ends Dec 31, 2025 with security support through the end of 2026. WP 6.7 supports PHP 8.0, 8.1, 8.2 as "compatible with exceptions." For PHP 8.3 and 8.4 it has "beta support." WordPress isn't fully compatible with any supported version of PHP. To what degree this matters is debatable but it is still something to be considered. Second, your take on security being "no better or worse than most other platforms out there," is false. Exploit security issues aside, basic security measures like brute force attack mitigation or simplified 2FA aren't employed. Anything with email needs a plugin to send properly. The presented solution? Install Jetpack. The default logins have no built-in method to change the logo, let alone anything else on the page. I am currently working though how to respect the WP backend infrastructure while employing modern technologies and methodologies. The solution seems to be either forward-thinking or build around outdated infrastructure while hoping the core will be modernized. From someone who is regularly in the code, WP feels like it is about 30% modernized with REST and a simple editor UI with FSE and Gutenberg. Everything else is utilizing systems based on 10-15 year old way of viewing the internet. I am currently working on a few plugins that help remedy some of these issues but I keep discovering I learn a modern methodology and have to look back 5 years to match WP's current code.

There are a few issues that really stand out to me as indicators of a larger issues. First, active support for PHP 8.2 ends Dec 31, 2025 with security support through the end of 2026. WP 6.7 supports PHP 8.0, 8.1, 8.2 as "compatible with exceptions." For PHP 8.3 and 8.4 it has "beta support." WordPress isn't fully compatible with any supported version of PHP. To what degree this matters is debatable but it is still something to be considered. Second, your take on security being "no better or worse than most other platforms out there," is false. Exploit security issues aside, basic security measures like brute force attack mitigation or simplified 2FA aren't employed. Anything with email needs a plugin to send properly. The presented solution? Install Jetpack. The default logins have no built-in method to change the logo, let alone anything else on the page. I am currently working though how to respect the WP backend infrastructure while employing modern technologies and methodologies. The solution seems to be either forward-thinking or build around outdated infrastructure while hoping the core will be modernized. From someone who is regularly in the code, WP feels like it is about 30% modernized with REST and a simple editor UI with FSE and Gutenberg. Everything else is utilizing systems based on 10-15 year old way of viewing the internet. I am currently working on a few plugins that help remedy some of these issues but I keep discovering I learn a modern methodology and have to look back 5 years to match WP's current code.

This is going to be really great, especially as it matures. The "con" for me, at least right now, is analyzing when to use components versus another method. Certainly, the benefits of creating a suite of buttons, CTAs, and cards are huge!

My two favorites, by far.

I don't think your take on "open source vs closed source" is valid. You mention the fact that the CLIENT doesn't care whether the project is built using open or closed source software, but that's not really the right question to ask. Yes, the client doesn't care if it's open source or not. Most of the time, the client is basically just paying for the end-result - a website that does what it's supposed to. You're right that most of the time the client doesn't care whether it's open source or not (or even know the difference). Open Source vs Closed Source DOES matter for the developer and maintainer of that website, however, and for the business that has to get the customer to pay for it. I can host Wordpress sites for my customers for very cheap, because I don't have to pay anything for the underlying software. If I were to use a close source SaaS software to build it, I would have either charge the customer more, or eat the cost of that software. And because SaaS platforms are owned by money-grubbing companies that will gladly double the price overnight if some MBA decided it's a good financial decision to do so, it's very risk for me, as the owner of an MSP, to build customer sites on SaaS. Then there's the fact that SaaS web platforms aren't as extensible as Wordpress, if they're extensible at all.

Greate video. Maybe you could make a comparison between the template and components in the future :)

Great video, great components, it is more flexible than Template element.

Awesome!!!!!

Sorry I really don’t like Elementor. I think the “hard to use” comment comes from the fact that so many people hire developers that install so much crap or add BUCKETS of hardcoded shit in various dark corners all over the place so users can’t understand why their changes don’t work or they can’t change things at all. Not to mention all of the WordPress legacy crap like Widgets, Shortcodes, and the Customizer. Every existing site I have ever taken over has been a dogs breakfast of widgets, shortcodes, plugins, code injection plugins, CSS saved at the page level with some shitty builder, or at the module level on 50 different pages, with hard coded post id css selectors, and then more code in the customized, and even more code I a child theme. Not to mention a slider plugin with its own separate UI. A form plugin with its own UI. An event plugin. A popup plugin. Etc. etc. etc. Basically WordPress and its Editor are great but people tack so much convoluted crap in top of it… almost every single time… that it”s like sabotage. If I build a simple marketing site for someone with a set of intelligent responsive defaults in theme.json and a nice collection of pre-built block templates and block patterns with virtually no plugins other than Gravity Forms and maybe ACF for globals etc… it’s a great, simple, intuitive, consistent, lean, fast, and secure site. I build sites now with almost no code… just a blank “theme” with theme.json and a nice collection of patterns and such. The only BIG downside of blocks right now I’d say it the lack of breakpoint specific options and controls… fluid sizing and intelligent defaults only get you so far. If a client wants to hide something on mobile for instance of have 4 cols on desktop, 3 on laptop, 2 on tablet, etc… they’re out of luck as the default Wordpress blocks just have a single built in breakpoint.

I wonder if this will eventually replace Brixies, Bricksmaven, Frames, type of libraries.....

Platforms like Shopify, offer so much nowadays, so many integrations, so many ways of creating your own thing…. You really don’t care if it ends up being more expensive, or more limited. The peace of mind they bring and the ease of use, makes everything else worth it.

I would like them to make the edit mode more distinct by using purple exclusively for edit-mode interfaces. Keep the structure panel's purple elements but differentiate the instance appearance from edit mode. Implement a dedicated exit button instead of relying on stage selection for exiting components. Add a full-width purple bar across edit panels only when in edit mode. I keep exiting unintentional…

Maybe add a small video showing the end result (the real estate site), always helps to convince people

It looks great. But I wonder about one thing. So far I've managed to do it this way: I've created a Template and in it the entire structure of the element, e.g. "Call to Action", then on the desired subpage I've added a bricks Element (Template) in the editor where I've selected a given template from the list. It worked dynamically - changes made to the template changed everywhere on every page. So my question is, what's the difference in how components work and using a template with nesting in the editor. Thanks for the help.

We need Variants! And the overall "Create Property" and then connect it it's cumbersome. Once an istance is insterted as an istance every aspect should be editable without having to define what should and shouldn't, also its styling. I don't know about limitations but the ux of this is meh. Very disappointing.

This is similar to how Framer implemented their components. I am curious to see how we can use it for loops.

The current user experience feels a bit confusing and often requires too much back-and-forth navigation. I like the idea of keeping the Structure panel fixed to the content you’re currently editing. It would also be nice if the main component at the top were placed below in some sort of dropdown menu. The functionality is as expected, and I’m sure more property connections will be introduced over time.

This is encouraging, a bit confusing but promising. Cwicly did this first and well kzbin.info/www/bejne/j4vVhINuqr2fd6c. I think Thomas and the Bricks team should get inspiration for some of their features from Figma and popular UX design software which pioneered the concept of components.

I think it's great. It's basically like Gutenberg Blocks but inside Bricks, or the opposite of GutenBricks. I can see letting a client / site owner into Bricks, restricted to only using Component Instances, so they can select from various Components I built, add multiple instances to a page, then edit only the instances via properties.

Starts at 5:24

This is a great analysis. I've been WordPress since 2015 as a blogger, and since 2018 as a developer. I've used Elementor and Gutenberg and I totally agree with everything you have said here. I do love the Gutenberg blocks when it comes to blogging. It's a billion times better than the old clunky and limited WYSIWYG editor but as a site builder, it seems like a bad attempt at recreating Elementor. WordPress is playing catch up instead of doing their own thing. They should add features that allow other developers rely more on WordPress, not compete with them directly and with the latest WPEngine and Matt drama, I hope things go back to normal and we see great features being added.