The Paragraphs field widget *can* be pretty.

I need to help to solve my problem, my first time using drupal
I use Drupal version 7, to build a store but there was a problem :

Strict warning: Declaration of ec_customer_views_handler_argument_user_uid::query() should be compatible with views_handler_argument_numeric::query($group_by = false) in include_once() (line 8 of /home/tagalaya/public_html/betago/sites/all/modules/ecommerce/ec_customer/views/ec_customer_views_handler_argument_user_uid.inc).

thanks

Imagine something seamless, though. Suppose that, e.g., the pull quote looked like a pull quote on the editing page, as rendered by the active theme. The gray background wasn't there, just the standard background color of the theme. The editing widgets (the move arrow and the edit and remove buttons) didn't show. Same for all of the other paragraphs. The editing page would look like a seamless version of the display page.

When the mouse moves over the pull quote, the editing widgets for the pull quote would appear, along with separators for other paragraphs, to support drag reordering of paragraphs.

If the user clicks Edit, switch to the normal editing display for that para. Not in a modal, though. For a writer, the meaning of content in one para depends on the content in other paras. E.g., someone is writing a Drupal tutorial, and decides to write about a call to the database service. Then thinks, "In the section above, where I explain about getting references to services from the dependency injection container, I should add an example for the database service." The writer scrolls up, makes the change, maybe needs to jump back and forth a few times to get the wording exactly right. The writer's work would be more fluid if the s/he didn't have to jump in and out of modal windows.

Implementation? The editing page would need a display view for each para. The code for that already exists; has to, so the para can be shown to site visitors. A JS wrapper would show the display view for each para. No CK. On mouseover, overlay the arrow widgets and buttons. On Edit click, switch to edit view for that para, with CK when relevant (there could be multiple CK instances on the page; CK supports that). When the writer saves the para, there would be an AJAX call, returning the rendered version.

This work might be worth it, to get the most awesomely awesome editing experience.