Currently developers can create fragments which have editable elements and configuration. This Story takes the adaptability of fragments to the next level by allowing developers to specify that a certain area of the fragment can act as a "drop zone" in which page authors can drop fragments while editing the page.
Page authors, after adding a fragment with the drop zone will be able to add further fragments as well as layout components (sections, rows) within the drop zone.
This capability is specially useful for creating certain types of fragments such as accordions or tabbed sections. It can potentially be used to create special types of layouts.
It must be possible to have multiple drop zones per fragment, including having drop zones within for loops as long as each of them has a different id.
This story can also be thought as a generalization of the current concept of layouts within Section Builder.
One potential way in which fragment devs could inject the drop zone is:
|Test Scenarios||Test Strategy||Kind of test||Is it covered by FrontEnd ? (JS-Unit)||Is it covered by BackEnd ? (unit or integration)||Could it be covered by POSHI?|
|Can create a fragment with a Drop Zone area||Smoke||Manual||No||No||Yes|
|Can create a fragment with multiple Drop Zone areas||Sanity||Manual||No||No||Yes|
|Can save a composition containing a fragment that has a Drop Zone area as fragment||Sanity||Manual||No||No||Yes|
|Add a fragment entry with a Drop Zone to the a page
|Delete a fragment entry with a Drop Zone from the a page||Regression||Automation||No||Yes,
|Update configuration values of a fragment entry with a Drop Zone on the a page||Regression||Automation||No||Yes,
|Duplicate a fragment entry with a Drop Zone into the a page||Regression||Automation||No||Yes,
|Check FragmentEntryProcessorDropZone for Edit mode||Regression||Automation||No||Yes,