Backend editing is cluttered with many fields that are not in primary focus of the user interest.
We need to find better ways to focus on the primary content fields.
Paragraphs arre adding many fields when adding layout aware controls.
We want to introduce a perspective switcher and at least separate between the Content and Layout perspective.
The perspective switcher will only be visible if fields are assigned to both perspectives.
#2828506: Introduce a plugin system for paragraphs types
#2829671: Implement edit perspectives with tabs when editing
#2829981: Add IsApplicable method for the plugins
| Comment | File | Size | Author |
|---|---|---|---|
| #7 | Screenshot from 2016-11-18 08-56-59.png | 33.47 KB | drobnjak |
| #6 | Screenshot from 2016-11-18 01-09-46.png | 71.42 KB | drobnjak |
Comments
Comment #2
miro_dietikerThe layout perspective will need many settings showing up without real need to create them as real fields.
Still, IMHO we should use the "manage form display" to manage the UI of layout, so users can add fields.
For this, we need a plugin system, and we need to be able to enable / disable (and even configure) plugins per paragraph type.
Whatever plugins provide, needs validate/submit handlers, merging into paragraph instance layout setting, and most importantly the UI elements of the plugin should be injectd into manage form display.
We need to define how to do that.
As an example: Classy paragraphs would then become a layout plugin.
Comment #3
miro_dietikerMedia management, including background will be a real field, so Media (usage tracking, ..) can do its job easily.
For a background field, we are not fully sure if it is layout or content perspective.
There are arguments for content, but then settings to apply parallax effects are UX wise disconnected from the background selection.
About the perspective name:
The perspectives will only show up if there is reason to do so (such as an active field).
Following the group like field management, it would also be possible that users could add own perspectives. But unsure if we should allow this. We will start with fixed definitions.
However, the name is open - the non-content perspective will contain layout settings. But It might be named properties or settings or anything else that will proof users can understand it.
Comment #4
johnchqueThis sounds so cool, so the first step might be to add the plugin system. Then we can define how we gonna implement it in the form display form. #2828506: Introduce a plugin system for paragraphs types
Comment #5
miro_dietikerThis issue is missing our summary goal screenshot.
Comment #6
drobnjak commentedScreenshot added.
Comment #7
drobnjak commentedComment #8
johnchqueAdded the first two steps.
Comment #9
johnchqueAdded new step that would improve management.