Well, it's simple, if you ask this question on the Magnolia User List the answer is MAGNOLIA :-)

Ok, that was the emotional part.

I worked with both, but I also want to admit that since my last OpenCMS projects a lot might have changed.

If you want to do a serious evaluation, you first have to define a list of comparable subjects (not only technical ones, though) and compare them against each other. E.g.
- Maintenance
- Re-usability of development features in the next project
- Performance
- User acceptance
- Development process (how fast can you develop AND do major changes)
- Time to Market
- Content Storage Concepts
- Future technologies/integration
and a lot more

The next thing is to define a small prototype and
- Develop with both systems
- Have users manage pages/content
- Test performance
- Modify the prototype with major changes and see with which system you can react faster to market changes
and more

If you do a fair and equal test, you will realize quite soon that Magnolia is a lot easier and flexible to handle and extend/scale. But you will also notice that OpenCMS will have more "out-of-the-box" features. The other major difference are the storage concepts. While OpenCMS uses the classic RDBMS, Magnolia is focusing completely on the far more flexible Content Repository.

If you are ready to deal with a fairly new content persistence concept (Content Repository, hierarchical content structure) and you don't mind having to develop some features (which you easily can re-use in further projects), then you will most likely stick to Magnolia.

The big positive benefits of Magnolia over OpenCMS are:
- Content Repository API allows you to add/remove content elements dynamically, without having to deal with database design. There are no dependencies (like i.e. the ER has) - Way more flexible, because you can decide on the data source during or even after development (e.g. change from the "File System" to a RDBMS model) - Due to the hierarchical content model you can extend your project at any time, which allows you to do "Parallel Development" (develop on multiple parts at the same time, without dealing with dependencies) - Content and Layout/Functionality are separate, which allows you to redesign the Web site without needing to touch the content - User friendly, native, content contribution. Authors only need to know how to use the browser. They have dialogs to add content elements and when closing them they see the results immediately on the Web page. - Content contribution can run through workflows, delegating content responsibility to the authors/editors and off the back of developers (having to write tons of content validation code). - Easy and fast search functionality (just think how cumbersome it is to search a content element in a database...)

Unfortunately the beauty of Magnolia is only experienced when you work with it. You will really love the "Content Repository API base on Java Technology" aka JCR. It's so flexible and easy to use and no worries about where the content is!

Cheers
Giancarlo


On May 6, 2008, at 10:53 AM, rainer wrote:


Better dont ask this on Magnolia list ;)

I dont know openCMS - so i wont say anything...

cu
rainer


smartfog wrote:

Good morning, everyone. I have to start a big job and I do not know what to choose, or if openCMS Magnolia. It 'a strategic choice, because then
the CMS will be used again in other jobs and the head violas that I
evaluate them. In my opinion, are equivalent, but objectively I am not an expert in this field. There is someone at ease and with experience I know
recommend for the better?

:jumping:


--
View this message in context: 
http://www.nabble.com/OpenCMS-vs-Magnolia.-Which-is-the-best--tp17082283p17088778.html
Sent from the Magnolia - User mailing list archive at Nabble.com.


----------------------------------------------------------------
for list details see
http://documentation.magnolia.info/
----------------------------------------------------------------



----------------------------------------------------------------
for list details see
http://documentation.magnolia.info/
----------------------------------------------------------------

Reply via email to