In many respects the Paragraphs module appears to be a fork of Field Collection. Functionally, the difference between the modules lies in how their respective field widgets operate. The Field Collection widget allows users to embed multiple instances of a single field collection bundle in a node, while Paragraphs allows users to select a different bundle for each instance they embed using the Paragraphs widget. Both of these methods are extremely valuable and I now find myself combining field collections and paragraphs on the same node.

Perhaps this is overly simplistic, but it seems the use case for Paragraphs could be solved if Field Collection had an alternate widget, permitting users to select multiple Field Collection bundles instead of just multiple instances of the same bundle. Would this work and is there any will to do this on the Field Collection side of things? Merging Paragraphs into Field Collection would greatly expand the use cases Field Collection solves, while reducing unnecessary code redundancy for those of us using both modules. Paragraphs is a relative newcomer, but I expect its use to grow significantly as word gets out and it would be nice to consolidate development efforts moving forward.

Comments

jmuzz’s picture

I agree and it could happen some day.

Current status: I have contributed some patches to paragraphs and entity reference revisions (Drupal 8 versions) and am waiting for the maintainers to review.