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
mit 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,
>>
>&
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 confirme
+2 schrieb Daniele Procida:
>
> On Thu, Sep 8, 2016, Peter Bittner >
> wrote:
>
> >I've started to compile a prototype of a django CMS powered website that
> >implements a simple editorial workflow. At the moment, I've use the board
> >weapons delivered
Hi there,
I've started to compile a prototype of a django CMS powered website that
implements a simple editorial workflow. At the moment, I've use the board
weapons delivered with django CMS and vanilla Django (this is described a
little bit on Google+ [1]). I've set up a demo website to play w
Hi there,
is there any progress in this area? I have the same feeling about
explaining that "all the other parts of the site" behave differently (i.e.
publish changes immediately). From a user perspective all pieces of a
CMS-driven website must work the same, users take this for granted. Zinnia
