I am hopeful that Divi, will become a super complete Web Builder, surpassing Bricks, Elementor, which are having HUGE updates and which I feel Divi is currently lacking. I pray for it.
Once Divi is at the point where Bricks is right now, it will be outdated again. Considering Divi 5 RC being postponed for ~1 year now, there won't be any features such as Flexbox or CSS Grid before 2025 (or even 2026). Let alone Query Loops, Class Management or CSS Framework-Integrations. I was hoping for Divi 5 to be great, but all the release delays made me switch to Bricks and I can't be happier now.
Appreciated but when we will got it?! Also hope to make dynamic columns sizes and numbers, RTL support, can add PHP codes, custom loop, carousel, module support get all custom taxonomies and custom posts, multiple pagination types like numbers, load on scroll instead of now . Meet the Google speed requirements , if Divi is conflicted with code or plugin display it to help to debug
Don't forget : there will be zero new functionality on launch. Nick is wary of giving timelines, cos last time, many people got upset at how much later things turned out. Best thing is to ignore Divi5 till it's here.
Love Divi! I've been working with Divi every day for several years and love my job. I'm really looking forward to the Divi 5 update. Thank you, ET, for always working hard on progress!
😀 Exciting times, Nick & Team! 💡 One suggestion, if I may - a small issue with Divi4&5. 😵💫 When moving a large element (image, row) downwards, via drag&drop, the screen 'jumps' to fill the space, which is somewhat disorienting. ☑ A smoother UX would be for the vacated space to remain in place, greyed-out, until placement of the relocated element. 💜 Thanks, and keep up the great work! 🙏
The divi4 framework load on "individual" per-page-need on divi5 is remarkable! This will make any new content/pages load fast and the migration effortless as developers can take their time to convert old divi4 plugins to divi5.
Nick is wary of giving timelines, cos last time, many people got upset at how much later things turned out. Best thing is to ignore Divi5 till it's here.
Thank you very much ET for D5 but I have a small question: Is D5 going to support a way to cascade place rows in to columns? This would help tremendously to create unique layouts when building new webpages from scratch using the Divi Editor 🤓
*PLEASE* ADD HOTKEYS TO THE BUILDER SO WE CAN CLONE/ DELETE SECTIONS WITH KEYBOARD AS WELL!!! LIKE IN ELEMENTOR ITS CTRL+D TO DUPLICATE VERY HANDY !!! STILL AMAZING JOB GUYS !!!
I hope with this new update that I will no longer have to go into Divi Support and enable the :Safe Mode" due to the fact that layouts etc load very slowly. I love Divi and hope that everything is much faster.
@@buildyear86 ... don't think there's been anything official, just a few comments that flexbox should be coming sometime in the future. But on launch, divi-5 will not have it, or any other new features. They will come later.
Okay! Thank you for getting back to me, was wondering about this. I think i'll wait a little bit. Wpuld be great if ET would share smt about that. Cheers, looking forward to 5!
@@buildyear86 Nick explicitly stated Flexbox in the last Divi 5 update video after launch. Likely it will be the first thing they work on. I tried to copy the link but Yt won't let me.
From this video, I really like the direction and approach you are taking with all of this. Have not yet had time to try the actual demo yet, but hoping to make time soon and start building it into some projects that will need to update later this year. Functionality with ACF, Divi Machine, gravity forms and Rank Math are top priorities for me. The Events Calendar as well for some of my older projects too.
What happens when we run into client sites with plugins from years ago that were never updated? It sounds like Divi 5 will have an "automatic" legacy mode that loads the Divi 4 assets for these situations, but how does it affect things like JavaScript and CSS for those old components? How much of a performance impact is there when loading the Divi 4 assets and the Divi 5 ones?
If they are so old, why update them at all? Personally, I would keep them as they are. Impossible to state the impacts, cos of the 100k+ plugins and customisations.
@@photomaldivesthat's my current thinking, but I'm unsure how compatible Divi 5 will be. Also, there's always the risk of security issues, but outdated plugins are certainly as vulnerable as outdated themes. It will likely be a case by case thing depending on whether I can find newer plugins to replace existing functionality on these sites, but unless the clients are going to pay for it, then they will need to wait until a new website is built.
