Skip to main content
edited tags
Link
avpaderno
  • 97.9k
  • 15
  • 164
  • 284
added brief comparison
Source Link
arjan
  • 1.5k
  • 12
  • 29

Bean, Boxes and Fieldable Panels Panes all provide similar functionality. I have trouble understanding what exactly the differences between them are.

What are their advantages/disadvantages compared to each other? Are they geared towards different use cases?

I want to use some kind of blocks in Panels to add custom content - content editors also need to be able to add content, in that sense the blocks I need are not pure configuration. But I also use Features...

Edit: I'll add what seem to be the main differences

Boxes

  • Largest userbase (~ 11500)
  • Treats blocks as configuration (i.e. the content ends up in your features)
  • Modules offering integration

Beans

  • Has recently become popular, ~1000 installs
  • Treats blocks as content, but allows exportability of their configuration via machine name (e.g. via Bean Panels)
  • Modules offering integration

Fieldable Panels Panes

  • Smallest userbase (~ 400)
  • From the author of Panels/Views/etc.
  • Panes cannot be used as regular blocks in theme regions like beans or boxes (I assume)
  • I wonder what the advantages over Bean mentioned here are ("offers additional features that makes it easier to empower content admins to lay out certain pages")

Bean, Boxes and Fieldable Panels Panes all provide similar functionality. I have trouble understanding what exactly the differences between them are.

What are their advantages/disadvantages compared to each other? Are they geared towards different use cases?

I want to use some kind of blocks in Panels to add custom content - content editors also need to be able to add content, in that sense the blocks I need are not pure configuration. But I also use Features...

Bean, Boxes and Fieldable Panels Panes all provide similar functionality. I have trouble understanding what exactly the differences between them are.

What are their advantages/disadvantages compared to each other? Are they geared towards different use cases?

I want to use some kind of blocks in Panels to add custom content - content editors also need to be able to add content, in that sense the blocks I need are not pure configuration. But I also use Features...

Edit: I'll add what seem to be the main differences

Boxes

  • Largest userbase (~ 11500)
  • Treats blocks as configuration (i.e. the content ends up in your features)
  • Modules offering integration

Beans

  • Has recently become popular, ~1000 installs
  • Treats blocks as content, but allows exportability of their configuration via machine name (e.g. via Bean Panels)
  • Modules offering integration

Fieldable Panels Panes

  • Smallest userbase (~ 400)
  • From the author of Panels/Views/etc.
  • Panes cannot be used as regular blocks in theme regions like beans or boxes (I assume)
  • I wonder what the advantages over Bean mentioned here are ("offers additional features that makes it easier to empower content admins to lay out certain pages")
better wording
Source Link
arjan
  • 1.5k
  • 12
  • 29

Bean, Boxes and Fieldable Panels Panes all provide similar functionality. I have trouble understanding what exactly the differences between them are.

What are thetheir advantages/disadvantages of each compared to theeach other solutions? Are they geared towards different use cases?

I want to use some kind of blocks in Panels to add custom content - content editors also need to be able to add content, in that sense the blocks I need are not pure configuration. But I also use Features...

Bean, Boxes and Fieldable Panels Panes all provide similar functionality. I have trouble understanding what exactly the differences between them are.

What are the advantages/disadvantages of each compared to the other solutions? Are they geared towards different use cases?

I want to use some kind of blocks in Panels to add custom content - content editors also need to be able to add content, in that sense the blocks I need are not pure configuration. But I also use Features...

Bean, Boxes and Fieldable Panels Panes all provide similar functionality. I have trouble understanding what exactly the differences between them are.

What are their advantages/disadvantages compared to each other? Are they geared towards different use cases?

I want to use some kind of blocks in Panels to add custom content - content editors also need to be able to add content, in that sense the blocks I need are not pure configuration. But I also use Features...

Tweeted twitter.com/#!/StackDrupal/status/233973902248910849
Source Link
arjan
  • 1.5k
  • 12
  • 29
Loading