Jahia is a Java-based enterprise content management system. It features an integrated user portal, web publishing and content management, document management, collaboration, and multi-channel publishing.
N/A
Plone
Score 9.0 out of 10
N/A
Plone is a free and open source content management system built on top of the Zope application server. Plone can be used for any kind of website, including blogs, internet sites, webshops, and internal websites.
In my experience, Jahia Digital Experience Platform as a CMS platform is excellent when you have a large amount of content that needs to be customized. It is also good for when you have templated content that has minor variations. I would say it is less appropriate when the content has numerous mathematical computations, or a large amount of business logic that comes into play with data processing.
The larger your organization, the more appropriate Plone will be. This is not to say that Plone is a worse choice for small websites, only that the minimum investment for a Plone site is certainly higher than for other platforms. If you already use Plone for your site and are looking for a redesign or an overhaul, I would only advise switching to a different platform such as WordPress or Drupal if your organization is downsizing. For any other situation, Plone is the natural choice for your growth.
Plone is a folder-based system, organising content in a similar way desktop-users are doing for the last two decades. No need to teach non-tech customers some relational-database like paradigm for content management.
Plone is secure. It is the most secure CMS you can get your hands on.
Plone is flexible, and makes fast development easy.
It lacks the ability to manage multiple versions of a page or content in general.
The back office interface sometimes encounters bugs or display problems.
It's difficult to keep pre-production sites up to date in terms of content compared to production, because the time required to import/export sites is very long once the site is rich in content.
Not everything is configurable or editable by Plone, and when you need to adjust or add custom pieces in, you need to deal with Zope. Zope has an ugly, confusing and difficult UI and structure as a backend.
Using 3rd party products is difficult to do - there are a few different ways to get them installed, all of which take a bit of luck to get right.
Building custom products for Plone is not fun. You've got to deal with an archaic framework to tie in that is not well documented (there is documentation about many things, but not great documentation and there are a lot of holes in the documentation).
I would not use Jahia as it proved too complex for our needs and didn't help our over goal of customer satisfaction. Along with the man hours to build and execute, it wasn't worth the hassle
I no longer use Plone because I got an internship in the web development field and my current place of employment uses their own content management system that they created. After getting to know other CMS's and similar software and comparing them to Plone, I would enjoy using Plone again in the future, but there are more complicated software that I'd like to learn as I progress in my field of study.
The interface and ergonomics are designed to facilitate the use of the product. The creation of template is easy which allows to minimize the actions necessary for the provision of content.
Compared to the amount of Plone sites, users and customizations we have in our organization, the amount of support requests and training needed is really small
[I give it this rating because it] was up most of the time. There are so many scheduled reboots that I don't think it would be a good choice for a 95% SLA.
Plone is very intensive in its operations, and if not configured well it can be slow. However it is designed and built with speed in mind and with proper use of coding, templates and caching can perform extremely well under high loads. It is capable of scaling to very high load availability environments with no specific coding requirements.
As I was saying, the support makes sure to be available for any question, or any technical point that we may need to discuss about. Moreover, whenever we have an issue with the platform they get alerted and also send us an email so that we are aware. We had multiple complex topics to work on in the past, but they always have been answering our question
Jahia provides a similar user experience to other CMS I have used in the past - it features a simple interface that makes navigating and learning how to use the platform easy and the ability to copy and paste content saves time and effort when building new pages. The ease in which you can manage the site in different languages is also a big plus!
Drupal: Plone is cheaper, so with Drupal is more complex to reach the required ROI. However, Drupal has a lower learning curve WordPress: For our necessities it has a more expensive learning curve than plone. Joomla, is easier to use. However, it have some issues on security and web content where Plone is much better
As a development company Plone allows us to provide complex web applications in a short amount of time.
Plone is quite robust and reliable so when you customize some parts you do not risk to damage other parts. This is quite positive for a web development framework,
Plone allows our clients to spread their activities among different employees improving the efficiency of content generation and management.
