DD Live 24: Builderius - How clean is the HTML Output?

Subscribe for more tutorials:

► Support my channel ◄

► Connect with me: ◄

► Recommended Tools (Affiliate Links - Support the Channel!) ◄

► Timestamp ◄
0:00:00 Getting things set up
0:05:40 Outline of the livestream
0:06:06 Improvements to media uploads
0:08:55 Margins, padding, and corner sides are linked by default
0:11:24 Arrow keys to navigate dropdowns in the builder
0:17:24 Selected class persists while switching elements
0:19:20 Sectioning elements now allow text content
0:20:52 Menu builder inserts the complete menu structure by default
0:22:35 Boolean HTML attributes now render correctly
0:25:47 Clean HTML output
0:28:27 Global and local styles are saved in separate external stylesheets
0:31:26 Edit text directly on canvas
0:36:20 Accessibility talk - items can both be cool and accessible
0:41:24 Intermission to fix my YouTube overlay chat
0:43:16 Answering Facebook questions
0:43:49 Smart viewport syncing for nested elements - suggestions by Israel
0:48:21 What's the best place to report bugs?
0:49:07 Why show header and footer in the builder's navigator panel (questions by Vijay)
0:51:42 What if the main landmark element is accidentally deleted?
0:54:23 The elements inserter should be rearranged logically
0:56:05 How to bulk import classes and variables
0:57:02 Reordering the favourites element section
1:01:36 What is the purpose of the ".builderiusContent" container (Comments by Marius)?
1:07:21 How to add inline elements like spans
1:09:40 Why the increased specificity for local styles?
1:14:15 Further question about adding inline elements
1:16:54 More options in the navigator contextual menu
1:19:22 First attempt - Inserting metabox fields using dynamic tags
1:22:59 Second attempt - Inserting metabox fields using dynamic tags
1:28:27 Rant - Devs should listen to users and provide timely feedback
1:31:35 The padding on the section element
1:33:24 Showing of the new HTML syntax for dialogues
1:42:52 Chatting about modern HTML and CSS
1:47:21 Some public announcements

#builderius #livebuild #walkthrough

[goshenweb]

I think what the user is saying regarding accidentally deleting main page content is that it will be great to have a delete alert so users have a chance to confirm they really want to delete that inner container, as it is not as easy as you showed to recreated a whole page once accidentally deleted. That main page content is what houses all the inner content of the page. The other option is to save Releases more frequently so you can easily rollback.

[snipkin]

Thank you, David, for your detailed look at the changelog for the 1.05 beta version of Builderius. I agree with the suggestions you make for further improvements. I am enjoying using and learning more about Builderius.

[Marius_Meyer]

Re content wrapper (1:01:36):

I think the ai summary left out some important context and broke my point down so far that it doesn't make much sense anymore. Admittedly, I didn't explain my example well either and perhaps should have chosen a different one to follow my points more easily. However, I can assure you that in some cases there will be conflicts with the content container. Now, during the beta phase, it would be easy to take a different route, which they obviously don't want to do. That's perfectly fine, as these will be rare edge cases (need to emphasize this again) where problems will arise. But they will. On the other hand, there are also scenarios where this container will be a benefit. It's a good example for compromising on minor things in a page builder. Not a big deal.

White labeling is nothing a builder can fully provide. That's not even my point here. There will always be some references to the tool you are using. But that doesn't mean I'm appreciating the ugly and non-editable auto-generated local classes (which now only shows up when being used, as you demoed, which is a great improvement). As you also pointed out, the container class could also sit in the body, but the container wrapper has another dedicated purpose according to the developers.

Builderius has a bright future ahead and I can recommend anyone to check it out, especially to receive even more design control and achieve even more clean code compared to other builders. They also have some unique features worth trying out. But there's a bit patience required, it'll still take some time. Eventually they're getting there.