Hi Elisabeth
I have the same experience, and editors prefer the forms edit mode in about 99% of all cases. It is simply more effective to work that way (it is faster to load and gives a better overview). I believe the new visual builder might change this since it will have a bit of both. This, however, is still up to us when designing and implementing the page types and templates with or without the usual On-Page editor or Visual Builder. If things are complex, e.g. having logical switches in a page type to empower the editor there is really no place in an On-Page editor for that out of the box. We surely can expose such settings on the template (only visible when in edit mode), but usually don't. Maybe we should?
I agree. All properties is the most common and default view. I real life, On-Page editing is something that is replaced by the practice of:
I agree that visual builder will introduce the new "experience" of pre-visualize content rendered at same time content is edited. But my concern is regarding limited "screen space" that makes all previsualization looks like mobile chanels. I suggested Optimizely to automatically hide the page-tree and right pannel when editors are using Visual Builder, in order to gain more pre-visualization space.
Hi,
As a Content Advisor, I've noticed most experienced web editors working in Optimizely CMS use the All Properties Editor by default.
What's your observation on this? How do your editors use On-Page vs. All Properties editing?
My hypothesis: they entered the On-Page editing a couple of times. but anyway needed to go All Properties to apply all the changes required. So they quit trying and now use All Properties all the time so they don't have to think about "are all of this task's needs doable from the On-Page"?
Another question: how do you train editorial team when handing over a newly developed CMS, regarding On-Page vs All Properties?
I'm really curious about this, as I am 100% guilty of using All Props. I'm hungry for ideas to switch to On-Page and help other editors with that too.
Thanks,
Ela