Magnolia seems to be a popular choice in the Java EE web content management sector. There’s a lot to like about it, including:
- Intuitive, friendly, visually appealing interface
- Good OOTB workflow
- Intuitive, friendly, visually appealing interface
- Uses Java Content Repository standard
- Available commercial support and training
- Intuitive, friendly, visually appealing interface
- Document management
- Auto-versioning
- Did I mention the interface?
Unfortunately my particular requirements include structured/nested content types, content reuse, and other features that lie outside Magnolia’s envelope. It was a sad day indeed when I clicked “Log out” and said goodbye to the familiar lime-green toolbars for the last time.
But if your requirements fit the “simple is beautiful” philosophy behind Magnolia, I suggest very strongly that you try it out. You’ll probably have a working site long before we’re finished with our requirements document.
Recent Comments