Excellent module is just what I was looking for.

[webspilka]

Hi
I looked yours TODO https://github.com/bummzack/page-blocks/blob/master/TODO.md. I vote with both hands for support fluent translations and get rid of the has_many relation to make blocks reusable

It would be great if there will:

• For one type of unit should be allowed to define multiple templates output
• Add shortcodes to insert blocks directly in the text editor. For example [Block id="5"]
• Add the block type BlockHolder, or something with similar functionality

[bummzack]

Thanks for your feedback.

Fluent translations work.. I've used page-blocks successfully with fluent.
The has_many relation is here to stay. Having many_many blocks imposes many difficulties, especially when it comes to publishing (eg. user publishes Block on one page and then the Block is suddenly published on all other locations where it has been linked). You can use the VirtualBlock to re-use a block on different pages though.

I haven't thought about short-codes... interesting. I wonder why you would need something like this? The goal of content-blocks is to compose your content in blocks and not inside the WYSIWYG-Editor. Imagine if you had a Text-Block and added the same block inside it as Shortcode... ouch!

Can you explain for what use-cases you'd need a BlockHolder?

Providing different templates is not the scope of this project. There are myriads of requirements when it comes to frontend styles/variations. But it should be pretty simple to add this feature via an extension?