Important! If you'd like to use Plone Mosaic in production, or develop it into a production quality feature for your clients, you really should participate (or sponsor your favorite Plone developer) to the Arnhem Anniversary Sprint this July. @ramon and @agitator will need your help there, and the hosts, Four Digits, are the original developers of the layout editor used in Plone Mosaic.
The third alpha for Plone Mosaic is now released.
While it's still considered to be only a technical preview (not pretty, expect bugs, hidden and missing features, missing focused user story, etc...), it's pretty functional:
Minimal Plone 5 buildout:
[buildout]
extends = https://dist.plone.org/release/5-latest/versions.cfg
parts = instance
[instance]
recipe = plone.recipe.zope2instance
user = admin:admin
eggs =
Plone
plone.app.mosaic
(Or deploy it at Heroku on Plone 5.0b2.)
Minimal Plone 4.3.x buildout:
[buildout]
extends = https://dist.plone.org/release/4-latest/versions.cfg
parts = instance
versions = versions
[instance]
recipe = plone.recipe.zope2instance
user = admin:admin
eggs =
Plone
plone.app.widgets
plone.app.mosaic
[versions]
plone.app.widgets = 1.8.0
Yes, Plone Mosaic 1.0a3 does unofficially support Plone 4.3.x. It only needs the new mockup based widgets. On Plone 5, the Mosaic behaviors are enabled on install for all Dexterity content types. On Plone 4, you need to create a new TTW Dexterity content type with two behaviors (Drafting support and Layout support) to get the Mosaic experience. Yet, expect Plone 4 support to be dropped in the future (not because it could not be supported, but because the support is so easy to break by accident).
Pro tip: Adding collective.dexteritytextindexer into the mix and activating its behavior for your content types would index your mosaic pages' text tiles into searchable text index.
Try it out, have fun, report bugs and join or sponsor the sprints!