Consider a tighter (and optional) integration with paragraphs_library

Problem/Motivation

When both the Paragraphs Entity Embed module and the Paragraphs Library submodule are installed, it can be confusing for site editors to distinguish between a Paragraphs Library Item and an Embedded Paragraph. For instance, after creating an embedded paragraph and realizing that they can reuse them elsewhere, a site editor is introduced to the notion that an embedded paragraph may be reused. Likewise, after creating a paragraphs library item (or promoting an existing paragraph) and referencing it in a From Library paragraph in a paragraph entity reference field, a site editor is introduced to the notion that a paragraphs library item may be reused. It stands to reason that having both of these very useful tools enabled at the same time may create a bit of confusion, as each use case creates its own “inventory” of reusable paragraphs, but they are completely separate from one another.

One may even integrate these further by making the From Library paragraph available in the list of “embeddable” paragraphs, which would mean a paragraphs library item can be embedded (by way of an embedded From Library paragraph). This enhances the usability, but it has some drawbacks:

1. It requires extra steps to embed a paragraphs library item: I can’t just embed the paragraphs library item, I have to embed a From Library paragraph that references the paragraphs library item.
2. It is a one-way street: I cannot reference embedded paragraphs from a From Library paragraph, nor can I promote an embedded paragraph to the paragraphs library.
3. One may argue that this asymmetric integration causes more confusion: It is easy to see how a content editor may become frustrated to find out that if they want to reuse any of their embedded paragraphs from a a paragraphs reference field, their only recourse is to recreate it in the paragraphs library and then replace the embedded paragraph with a From Library paragraph that references the paragraphs library replacement.

I’m not sure what a proper solution would look like. I haven’t really thought through the implications of providing some kind of integration between these two tools. I’m working on site for which I am enabling both functionalities and I quickly realized that the paradigms introduced by each one have just enough overlap to feel (from a UX perspective) like they should be able to integrate better.

I’m creating this issue to get the conversation started and see what ideas might come from the maintainers of this module and the community.

Proposed resolution

TBD

Remaining tasks

TBD

User interface changes

TBD

API changes

TBD

Data model changes

TBD