Add fences for blocks

Woohooo!!! My dream.

Ah, there's two ways to think abut controlling the wrapper on each block. One would be for blocks added using the "+ Add Block" action link to allow wrappers. (Meh.) The other is to have a way to control the wrapper element on every block no matter which module created it. That's what my +1 is for.

subscribe

I would love this feature too

Would be great!

I've implemented the first iteration of the fences block concept on GitHub (https://github.com/droath/fences_block). I'll be happy to commit this as a patch if the maintainer approves.

Please leave a comment if you have issues either on D.O or Github.

GitHub: https://github.com/droath/fences_block

Whao this sounds great! Are you planning to merge it with fences or as submodule or will it be a separate module?

@droath, we're using fences_block since 2 years now with great success.

@Sam152 [Maintainer]: What do you think, should fences_block be created as separate module, submodule of fences (my favourite) or be included in the main module?

If the maintainer agrees, I think it would be great if you could create a patch against 8.x-2.x for a later 3.x branch and take #1343578: [3.x] Add optional wrapper around field items and fix class structure into consideration. Blocks should have the same settings and markup structure as described there. It's a lot more flexible and cleaner for several use cases.

Thank you!

I'm in favour of smaller and narrowly defined modules where possible. Is there a reason not to spin this out as a new d.o contrib?

Thank you @Sam, well the functionality is very very close to fences and you could discuss if fences (which is not named fences_fields ;) ) should be something like rabbithole which contains fences solutions for different kind of entities. But I think a separate module is OK and just link each other on the module pages.

@droath: Are you still maintaining the module or interested to create a full project? If not I'd like to offer to create it for you and add you as full maintainer. But let's keep that separate from this issue. @Sam152, if you'd also be interested in maintainership I'd of course appreciate that a lot because the modules are very close to each other.

At this stage, I'm only really interested in maintenance fixes for the current feature set and implementation of fences. Especially since now that LB has introduced configurable sections and layout plugins, I see less of a need for configurable markup outside of field templates.

I closed this old issue for the same reason: https://www.drupal.org/project/fences/issues/2683271