Problem/Motivation

In order to enable better overview of the elements and the structure of the node using the paragraphs, we want to have an option, preferably in back-end, to leave some paragraphs open even the default display mode is set to "closed". This would lead to better user experience and easier overview in the complex structures.

Proposed resolution

Remaining tasks

User interface changes

API changes

Data model changes

Comments

drobnjak created an issue. See original summary.

miro_dietiker’s picture

miro_dietiker
Location Switzerland
commented
Priority: Normal » Major
Issue tags: +Usability

The question here is, how much nesting is dependent from the widget state.

If we treat children separately, we could always display them open. Or only initially.. but that might be confusing because it can be opened and collapsed at the same time... that would require us to see edit/update (fields) and collapse/expand (hierarchy) as separate concepts.

Now about labels: if a container has only one child field, we don't need to output the child field label (typically "Paragraphs") at all. Instead we could directly output the children.

Promoting because child hierarchy and related experience is super important.

primsi’s picture

primsi commented

I can imagine this use case: the user is creating some complex node and often saves to see the progress of the page (actually previews). But he/she wants to remember the open/closed state of that particular node, because maybe in other nodes the complex part is in some other type.

One way we could accomplish this is to store that information in cookie or local storage. I am not sure if we want to go in this direction at all though ...