Ryne, Yes, basically reusable content blocks that can be edited from the admin. I have reviewed most of them and FunkyBob's flatblocks, tinycontent and fluent-blocks seem to be the most cleanly implemented. The last two at least are pretty solid, with tinycontent being possibly the best if all you want to achieve is use admin editable content 'bits' in your templates. fluent-blocks is more intrincate, with plugin support for different types of blocks and it seems more geared towards being a Fluent CMS add-on rather than an app you can use as-is in your other projects, although that works just fine, but I don't see an easy way to plug it into the Mezzanine content framework. Field injection as it is, still remains a sort of ugly hack.
On Tuesday, August 11, 2015 at 6:45:24 PM UTC+3, Ryne Everett wrote: > > I've been curious about this as well, though I'm not sure I correctly > understand what these packages are supposed to do. Is the idea to make > certain html templates editable via the admin? > > On Tue, Aug 11, 2015 at 11:19 AM, <[email protected] <javascript:>> > wrote: > >> I noticed mezzanine-blocks is greatly limited and I'm not a fan of its >> design patterns. There is no official/built-in support for content blocks. >> Has anyone worked with fluent-blocks or tinycontent in a Mezzanine site? >> Will there be ever upstream support for these things? >> >> Thank you! >> >> -- >> You received this message because you are subscribed to the Google Groups >> "Mezzanine Users" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to [email protected] <javascript:>. >> For more options, visit https://groups.google.com/d/optout. >> > > -- You received this message because you are subscribed to the Google Groups "Mezzanine Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
