| Your Rating: |
|
Results: |
|
6 | rates |
This is a compilation of answers to "Why do you use Magnolia?"
- Easy clustering. Tried OpenCMS but they just didn't have it, even if their homepage says they do.
- JCR - it is something our client needs so that they can go for some elaborate storage solution / authoring tools in not too distant future.
- Opensource and rather good usability, i.e. only a few rough edges wheras all other CMS I've used so far are really terrible form the usability point of view.
- Easy setup and administration.
- The support of the upcoming JSR-170 spec. (Same as JCR above.)
- The only other free Java-based CMS we've considered is OpenCMS and it lacks both features. OpenCMS has lots of features that we don't need at all in our very small project so this fact is more a disadvantage than a benefit In our case - their rich UI might be too complicated for the client.
- For me the way that paragraphs are implemented is a real advantage for creating templates to define and display dynamic and interactive content. I've been able to create Paragraph templates for Flash that allow my users to create multiple choice questions and other learning interactions in the middle of their instructional content.
In its previous incarnation on JspWiki, this page was last edited on Feb 9, 2007 11:01:00 AM by
- RalfHirning
- PhilRees
- AnupDarvatkar