Hi there,
we purchased a license last year for our new company homepage. We’re holding off for now because Bricks 2.0 was announced for release in Q1. To future-proof things, we’d really like to wait for the new version - our company sites tend to stay live for several years.
So, our question is: Any updates on the 2.0 release?
There’s no need to wait to create your new website. Components are already available now, and you can find everything else planned in our Road to Bricks 2.0 article:
Thanks for your answer – I guess I misinterpreted the sentence in the article you mentioned, which reads: “With version 2.0 as the perfect milestone, we will introduce a few breaking changes we’ve been holding back on.” I was under the impression that homepages created with 1.x would not be able to be updated to 2.x because of these “breaking changes.” - good to know I’m fine
“Breaking change” does not mean that sites built with 1.x no longer work, but that certain features, styles, etc. may be adapted in 2.0.
This type of change can generally occur in any version (and is mentioned accordingly in the changelog - see 1.5.1 example), so you may have to adapt your sites slightly - but not rebuild them from scratch
are there any updates on Bricks 2.0? “The Road to Bricks 2.0” has been running since September last year with the indication that Bricks 2.0 should be released in the first quarter of 2025. Is there any information on whether it will be delayed until the second quarter or when the beta will be released for testing?
Thanks to the whole Bricks team for your great work!
As we approach the end of Q1, I want to share a quick update on Bricks 2.0’s progress.
We are in the final phase of preparing the 2.0-alpha release, which should be available for manual download and testing from your Bricks account in the first week of April.
A bit behind our original timeline, but considering the scale of the update, this extra time is well spent to ensure this update goes as smoothly as possible.
Here are some of the highlights of Bricks 2.0:
Element Manager: Ability to activate, hide in-builder, or globally disable elements (Bricks-native and all custom elements).
Visual CSS Grid Builder: Visual interface to configure your grid layouts in the builder (move, resize, rename, etc.)
Font Manager (in-builder): Manage all your fonts directly in the builder (upload custom fonts, download Google fonts locally, favorite fonts, etc.)
Icon Manager (in-builder): Create your own icon set (using SVGs) and disable default icon font sets.
Map Query Loop Support & Sync: Configure a query loop on your map. Plus, the ability to sync your map with another query loop on the same page (plus full query filter and pagination support). And fully customizable info boxes via popup templates.
Form Webhooks: Define multiple API endpoints (Zapier, etc.) to send submitted form data to (plus custom file size and rate limits)
Indicator from which breakpoint/class a setting is inherited
Capability Builder: Set up custom capabilities for Bricks and fine-tune through a vast selection of permissions.
WooCommerce product variation swatches
We can’t wait to share this major update with you, and we appreciate everyone’s patience while we finalize this 2.0-alpha release.
Time for a quick post at the start of the week so you know what’s happening.
The code for Bricks 2.0-alpha is finished.
We’re now writing the changelog, recording videos, updating the Academy, and performing final tests. Once that’s done, we’ll upload Bricks 2.0-alpha, and all of you can help test this release
While we’re nearing the finish line, we can’t share a concrete release date. This milestone release has many moving parts; one test gone wrong could set us back more than anticipated.
But I’ll provide another post this week, either announcing the release itself or sharing what’s still in the works.
Since this is an alpha, we expect the final Bricks 2.0 to look and work at least slightly differently from this upcoming alpha.
So I’m thinking of demoing all significant changes in one big release video first—similar to what we did for Bricks 1.11 (https://bricksbuilder.io/release/bricks-1-11/)—and then recording individual feature videos after the final Bricks 2.0 has been released. Do you like this format?
I like this format. Gives us a chance to play around with the alpha and ask relevant questions, maybe even giving you an idea on which individual feature videos to prioritise first.