Hello Peter thank you very much for the wireframe. My experience with a toolbar restricting the width of the viewport and especially the websites width is in general bad. This also lead us to reconsider the sidebar and overlap it over the content. It's not an option that I'd consider but I can place it in the board meeting.
I'd rather have it on the bottom of the page spanning fullwidth, also considering that a structure can have many nested level and width will be a problem. We could eventually implement switches, such as the developer tools offer. I like the idea of the toolbox but might feel more comfortable adding that to the content itself with hover indications or so, but we'd need some UX tests for that. Cheers Angelo On Wednesday, 21 December 2016 21:10:34 UTC+1, Peter Bittner wrote: > > Hi Angelo, > > I've made a quick wireframe, see attached. It's available for public > editing at https://wireframe.cc/IBlaDw > > A CMS sidebar can solve the issue of the toolbar occupying "too much" > screen real estate. It can easily collapse or slide out (as the toolbar did > in django CMS 2.4, by the way!), and users will feel alright. On large > desktop screens the default placement on the right (or left) comes natural > as most screens are much wider than high, nowadays. Containers inside the > sidebar can have accordions to accommodate several tools. And no toolbar > means 100% of vertical space remains available. The Admin panel can still > float in from the left if needed. > > The toolbox offers all plugins (in a context sensitive way) to drag and > drop them onto the page. The structure below allows for ultimate control > and fine-tuning. With the toolbox and the structure view both available at > the same time there is no context-switching needed, no losing of context > happens while working on the page content. Of course, the sidebar could > optionally detach (into a separate window) or be rearranged or moved to one > of the other 3 edges of the browser window. > > Peter > > > 21 Dec 2016 11:22:51 UTC+1 Angelo Dini wrote: >> >> Hello Peter >> >> yes, this is why we need to enhance the content mode to enable simple >> addition and restructuring of content. Though we will still have the issue >> of losing context. >> >> I'm very open here to recommendations / UX ideas or sample screenshots of >> a possible solution. >> >> The technical requirements there are still that the modes are split >> apart. We can link them with a new "developers view" mode or whatever we >> wanna call it to mimic the developer tools. >> I find myself more splitting the developers tools from the actual window, >> using 2 windows. That might also be worth having a look at. >> >> Cheers >> Angelo >> > -- 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/497dd39c-bf2c-4483-82b4-5c657afe676a%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
