I just found a new project yesterday which looks like a similar approach: https://drupal.org/project/nestedbox

Please check it out and maybe collaborate your power on one module instead of two by letting them join this existing project.

Thanks!

Comments

drupal a11y’s picture

And maybe you could give some more detailed answers regarding your module in the issue I made for the ""nestedbox"-module here: https://drupal.org/node/2226673

Thanks again.

donquixote’s picture

#2226673: Maybe join forces with "paragraphs"-modul

@jeroen.b You find me on IRC #drupal-contribute quite often..

Nicolas Bouteille’s picture

Hi,

Just wanted to back that the idea behind Paragraphs and [Entity Reference + Inline Entity Reference + Nestedbox] really is great. It clearly is the future of content creation and it actually should have already been there a while ago! I think it's great mori made you two know about each other, brilliant idea! I'm looking forward to see where this collaboration will lead you. And I would actually be really interested in joining forces as soon as I have some money saved and thus some time to contribute back to the community the way you guys do.

Keep up the good work!

And thanks again :)

Nick

jeroen.b’s picture

Thanks mori, I will try the Nested box module soon, looks good.
I like the psr4 approach.

@donquixote I'm at IRC all the time, I'm known as jerbob92 there.

gmclelland’s picture

There's also two other similar modules that might be worth checking out:
https://drupal.org/project/content_nodes
https://drupal.org/sandbox/davereid/1992424 - Inline entity form rendered

donquixote’s picture

gmclelland:
The sandbox module looks useful! I think this is not really an alternative but rather an add-on to throw in the mix together with nestedbox.
I don't think it will work so well with paragraph, since paragraph does not use inline entity form.

The content_nodes looks more like a predecessor of nestedbox and paragraph, I think we can leave that behind..

@mori, jeroen.b:
I think for the future we should advertise one of both as the "recommended solution" (I tend towards paragraph, but I have not done enough evaluation to really make a decision). The other one can be kept alive as an alternative.

The main problem I see with two modules is that paragraph types (e.g. exported with features) cannot be easily reused as nestedbox types. So we would get two distinct ecosystems with a lot of repetition.

donquixote’s picture

Title: Check out new maybe similar project - maybe collaborate » Compare paragraphs with nestedbox + inline entity form

More relevant issue title.

donquixote’s picture

gmclelland’s picture

FYI...Here is another similar project that just popped up. https://www.drupal.org/project/fancy_features and https://www.drupal.org/project/fancy_kickstart

yannickoo’s picture

Thank you Glenn for referencing them :) I have to say that the Fancy Kickstart distribution just demonstrates what you can do with the power of Entity reference, Inline Entity Form, Display Suite and some other sweet modules. The modules we created provide new functionalities for Drupal so that building a flexible content page is more powerful than ever.

The question here is more something like "what are differences between Paragraphs and Inline Entity Form module?".

Nicolas Bouteille’s picture

Please check it out and maybe collaborate your power on one module instead of two by letting them join this existing project.

donquixote’s picture

@yannickoo:

The question here is more something like "what are differences between Paragraphs and Inline Entity Form module?".

Which entity type do you use for embedded content snippets?
I made Nestedbox for the single purpose of having an entity type without any unnecessary side effects or overhead. I considered to use Bean or other things instead, but they all have some stuff we don't need here.

I have seen a client project that uses nodes instead. I think they are doing it for fine-grained access control, which afaik would not be easily available with a custom entity type. But if that is not a requirement, I think nodes are generally more heavy than needed.

JKingsnorth’s picture

Is there any scope for working with the Inline Entity Form project, in terms of sharing functionality/code? Seems there are a few overlaps?

mpotter’s picture

I'm interested in this discussion as well. In Open Atrium we want to add the ability to have related content displayed inline (such as an inline Related Discussion post within a Document or Event node). I like how this Paragraphs module works and am leaning towards using it. On the other hand, we also use the Bootstrap Tour module, which is moving towards an entity-based solution using Inline Entity Form.

Seems like having both Inline Entity Form plus Paragraphs would have duplicate functionality. But I like how easy the Paragraphs module makes the entity creation. And I really like how Paragraphs allows different bundles to be mixed into the same multivalue field.

Looks like Inline Entity Form requires adding code (a subclass) to support it. Could Paragraphs just implement that subclass and let Inline Entity Form handle the rendering somehow?

Would like to hear more pros and cons about the two approaches.

rcross’s picture

i'm also interested here. IEF seems like it could be leveraged much more here

GiorgosK’s picture

One might also want to check out bricks
https://www.drupal.org/project/bricks
that promises to be more than paragraphs and has d8 release
(I did not try it yet but look promising)

delacosta456’s picture

hi have anyone try do add a paragraph from a node view using panel?

This is easily possible with Inline Entity Form .. but i haven't see how to do that with paragraph