The Alfresco platform, from Hyland, delivers comprehensive cloud-native content services. It is used to intelligently activate processes and content to accelerate the flow of business.
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.
Easy integration with the external APIs Workflows can be invoked via REST call Wonderful swagger documentation for process REST APIs REST, MULE, CAMEL, Google Drive, and Box features are available with Alfresco Process Services The micro-service version deployment should be well documented and needs improvement
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.
Alfresco Process Services and Alfresco Application Development Framework integration makes for best functionality/application of ECM.
Use case alignment - Marketing content and documentation of specific business requirements and user stories being available as reference material/documentation.
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).
As per the current market and the line of products that are available for content and document management system, Alfresco is a very good option compared to other systems in terms of features and cost. Plus the community support is great. Also since the product is open source, it can be extended or understood in a better way.
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.
Alfresco Content Services' UI has never been its strength from the beginning. Therefore, rating it from a usability standpoint, I will not rank it high. However, Alfresco Content Services can easily be integrated with any application and leveraged as a backend CMS or DM system. With the new Angular-based UI approach, it's very much possible to create custom UI on top of it as required.
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
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.
I am not big fan of Alfresco Content Services' support; it works on its own speed and sometimes it becomes challenging to achieve business needs. However, I appreciate regular delivery of security patches and updates
Process was relatively smooth and overall, downtime minimal. MSI was very responsive to our needs and made the transition easier than it otherwise might have been.
All software has some pros and some cons. Alfresco has some good pluses, and suits our environment very well. It fit perfectly in the place that we are working on. That is why we decided to go with this software. Overall, the kind of content management that needs to be done in an organization is what would determine which software to use.
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.
