Sorting of paragraphs 02 - alternate solution using cut and paste instead of drag and drop [#2828106]

Problem/Motivation

Sorting of a long list of paragraphs using drag and drop is a tedious task and sometimes prone top failure when the list spans more space than one viewport height.

Proposed resolution

Introduce an alternative sorting mode for paragraphs (and possibly other multivalue fields) that provides functionality to "cut and paste". Paragraphs are selected and then moved by inserting/pasting them at an insertion point between two other paragraphs or at the end/beginning of the list.

Remaining tasks

Create wireframes to show the concept
Create a design for the backend theme thunder_admin
Implement a proof of concept in code
See if this can be a patch for paragraphs or core or needs to be implemented as separate module

Comment	File	Size	Author
#4	2828106_demo.gif	718.51 KB	mtodor
#2	paragraph_sorting_cut_and_paste.png	217.58 KB	pixelmord

Comments

Comment #1

16 November 2016 at 15:01

pixelmord created an issue. See original summary.

Comment #2

pixelmord commented 22 November 2016 at 14:22

Status	File	Size
new	paragraph_sorting_cut_and_paste.png	217.58 KB

Here's an early wireframe that shows the cut and past sorting concept in action.

Comment #3

miro_dietiker

Switzerland

commented 9 December 2016 at 07:48

This is a proposal that introduces a new pattern that is not known in Drupal. At Paragraphs we try to limit these things and stay in alignment with Drupal Core patterns as much as possible.

With the proposals we developed, we think that the UI is getting more compact with multiple steps.
The already committed collapsed summary allows to see a Paragraph as a single line item with still being aware of its contents.
#2738715: Improve Paragraph collapsed/closed summary

With the dedicated drag & drop mode, it is always easily possible do sort items, no matter what is the default UI state (edit, preview).
#2825575: Introduce a Drag & Drop Mode

With the perspectives, the edit forms are reduced to content fields because settings / properties have a separate tab.
#2825557: [META] Introduce edit perspectives

Our approach is to implement these step by step improvements and learn about the change / shift in the experience with real user testing. Then we can decide if further improvements are needed.