Thanks Angelo, for your quick and elaborate answer. > The structure mode is intended for advanced user
For what I know it's not even possible to add a plugin to a placeholder in content mode. All you can do is edit plugins that have been added (by someone) previously. Users that have no access to structure mode cannot add new content. Also, "advanced users" have the right for decent usability, too. Losing context is not something that happens to people with little expertise. It is something that is a proven fact of user research, application design and usability testing. If django CMS doesn't get it right users will go and look for other solutions. We developers have a better time selling django CMS as a solution to clients when it is simply ahead of competition. It would really be nice and helpful to get the user experience right. > we do not want to limit the view space I don't think web developers complain about the Firebug panel (and the like). You can adjust its size, its position, you can even detach it from the main window. Also, if content editors (and web developers) have a large screen they can use the available screen real estate in an effective manner, given some flexibility of the UI. It's really a matter of reusing established patterns. Side panels that collapse or can be folded away exist in tools, mail clients, etc. for years, and we love them. Just imagine that content editors work in a similar way than web developers. Wouldn't that be cool to look at? Wouldn't those people feel empowered? More possibilities, more feedback, more transparency, all at your finger tips without having to do research in the menus, the popup dialogs, etc. Peter Am Montag, 19. Dezember 2016 10:21:42 UTC+1 schrieb Angelo Dini: > > Hallo Peter > > thanks for the feedback and proposition. One trick that helps is switching > context via SHIFT + Space, that will highlight the current _hovered_ > element. The main reasons for two modes are: > - Headless mode, this will be added in the future and will disable content > entirely and allows the CMS to be run headlessly for frontend frameworks or > applications > - Permissions, some people should only be able to "edit" content vs > "restructuring", this way we create separate roles for the CMS > - Legacy, as we had to support IE6/7 back in the days we had limitations > on what was possible through frontend > > We hear you and would like to improve the content mode itself to allow for > simple restructuring or adding content "lite" version. So people could > easily add images, text or so inline. The structure mode is intended for > advanced user that are free to do whatever they want. Even with your > suggestion with an inspector, the experience would still be reserved to > experienced users. In addition to that we do not want to limit the view > space, the toolbar is sometimes already be considered as "distractor" when > editing content. > > These are my thoughts :) > > Cheers > Angelo > > On Sunday, 18 December 2016 17:14:43 UTC+1, Peter Bittner wrote: >> >> Hi all, >> >> I'd like to ask about the reasons for having a Structure _*versus*_ >> Content mode switch. We do front-end editing to avoid losing context with >> what we want to change. Now, when we switch to structure mode all the >> content is hidden---and we lose context. I've seen this impression >> confirmed with unskilled, untrained, first-time, and elderly users. >> >> Structure information is good for precise editing, it should be >> supportive information though. The real state of the page should stay >> visible, so the context remains established. >> >> How about doing editing as with Firebug (Inspect Element, etc. in your >> web browser)? With a structure panel open on one side of web page (and a >> plugin panel / toolbox open on another side of the web page) we could have >> all the information we need for editing visible at the same time. When >> hovering over a plugin or placeholder on either the web page or the >> structure panel the corresponding element on the other could be >> highlighted. Just like web developers love it when analyzing a web site. >> >> Any thoughts on this? >> Peter >> > -- Message URL: https://groups.google.com/d/msg/django-cms-developers/topic-id/message-id Unsubscribe: send a message to django-cms-developers+unsubscr...@googlegroups.com --- You received this message because you are subscribed to the Google Groups "django CMS developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-cms-developers+unsubscr...@googlegroups.com. To view this discussion on the web, visit https://groups.google.com/d/msgid/django-cms-developers/669947bd-650f-49b2-9348-683f09d3925d%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
