On Oct 14, 2006, at 1:00 PM, Shaun Barriball wrote:

Hi all,
Magnolia provides a feature rich interface for managing JCR 170 based
content. Based on a review of RC3 it uses a handful of custom content types
currently including:

* mgnl:content
* mgnl:contentNode
* mgnl:metaData

We have an established more strongly-typed content model we'd like to
manage, potentially using Magnolia.

Has anyone used Magnolia with other custom content types created to model a
particular problem domain e.g.?

 * acme:fooBarPage content type

If not, is it feasible to use Magnolia for custom content types or is the
CMS fundamentally based on the mgnl:* types?

All comments appreciated.

For what its worth, the Enterprise Edition has a module called "data module" that allows to manage arbitrary structured content types (custom node types), using the standard magnolia ways - its pretty neat.


Regards / Grüsse
Boris

--------------------------------------

Dipl. Inform. Boris Kraft
CIO, Partner

Magnolia International Ltd.
Maiengasse 30
CH-4056 Basel

Phone   +41 61 228 9000
Fax     +41 61 228 9001

[EMAIL PROTECTED]
http://www.magnolia.info

--------------------------------------

Magnolia®  - Simple Enterprise Content Management

--------------------------------------




----------------------------------------------------------------
for list details see
http://www.magnolia.info/en/magnolia/developer.html
----------------------------------------------------------------

Reply via email to