I have done EAV on top of MySQL, and it is either complex and scales poorly or you have unsearchable blobs. It looks like they are doing the blob route.
other properties are serialized in a binary blob
EAV on top of SQL is re-inventing the wheel. Likely they would be much better of with MongoDB or some other DB that actually has some amount of support for EAV.
There's a very active list where the creators are always helping out new participants.
There's also a FLOSS cookbook in the works.
It's very unique in the sense that instead of reinventing the wheel, it uses mostly off-the-shelf erlang libraries for it's core (webmachine, a forked version of nitrogen, mochiweb, erlydtl) and also because of the data model (for those who don't know Zotonic uses a EAV[1] model on top of postgresql[2]).
[1]http://en.wikipedia.org/wiki/Entity-attribute-value_model [2]http://zotonic.com/documentation/670/data-model