Here is the third beta of Blocs V5.2.0 with more fixes and improvements.
Most notable improvement is, you can now share screenshots from preview mode for more accurate renders and it will also respect breakpoint, which means you can generate mobile screenshot to share in XS breakpoint.
Anyway, have fun testing and have a great weekend too
Thanks for the update @Norm. It’s great that the user can now unlock the class in the editor, instead of having to go to the library, but if users are able to unlock from the editor shouldn’t they also be able to lock it from there as well?
No problem, I hope the recent changes help with your workflow.
I’ve actually given this some thought this week, right now I feel the user flow of only being able to lock in the Class Manager helps to prevent unwanted locks and confusion over what is locked.
My thought was that users may think you are just locking the class name from being edited or the state (hover, active etc).
But I’m totally open to this idea, I’m sure others will contribute their thoughts too so let’s see what other testers think.
To lock a class you’re obliged to take the tourist route to get there and for unlocking there’s a 4-lane highway laid out. That makes no logic to me. However, my 2 cents do not have any value as I will never use it…
I’ve just tried exporting a screenshot from XS of a web page and it has added a crazy long empty white space (that isn’t present in preview of Blocs) before showing the footer.
Advanced users can now lock classes for dynamically added, styled elements that they programmatically create with JS, when a site is run in a web browser. It’s handy if you use the remove all unused classes and the element doesn’t exist until it’s previewed.
And Bric developers who may include classes the user can subclass in a project. Being able to lock these prevents them from being flagged as not used if the elements are dynamic and are not generated until after export when a site is running.
I believe volt CMS offered this workflow with extra classes at one point.
In order to capture the full height of the webpage Blocs needs to calculate the height which it uses some JS to do, it then adjusts the preview frame height, so no part of the website is hidden in scrollable area.
Something must be throwing off this calculation, do you use any styling that would fix elements to the bottom edge of the screen regardless of height?
Your Bric has a class .my-brics-class that is toggled when a user presses a button within your Brics html content.
You can inform the user this class exists in your Brics docs and they can add it in the Blocs UI and customise it.
Because the class usage only exists in a particular state during use. The user can now lock the class so it’s not flagged as unused when cleaning up a project.