Agility vs. Plone

Agility is well suited for companies that want a balance of control and support. For major global site updates, these can be handled by Agility's support team, while minimal changes and updates can be performed autonomously by the company's own staff with ease. For companies that are interested in flexibility to reconstruct site structure or major global facelifts, Agility is less ideal because these changes must be handled and paid for through Agility support.

Incentivized

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.

• Unlimited Content Modules which are extremely helpful for file management .
• Unlimited number of API and Asset Requests
• File management among the CMS is extraordinarily useful as a hosting tool native to our web content

Incentivized

• 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.

• The filing system and search function are often difficult to navigate. Finding a file that I've uploaded isn't always easy to locate in Agility CMS
• The WYSIWYG content manager isn't always intuitive. I often have to go directly into HTML editing to resolve line spacing problems

• 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 am not a part of this decision process at our organization.

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.

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.

Support is always available and responsive when we email, responding right away that they are on the case, even if they are unable to solve the issue right away. Support will usually find the issue of our problem quickly and require minimal hand-holding, direction, or re-explanation from our team. They are knowledgeable about the platform and our instance and are able to run diagnostics with minimal information from us. When issues are resolved they always request confirmation that things are working as expected before closing out our tickets.

Incentivized

A few reasons to go with Agility CMS Product Capabilities Value for money Product functionality and performance Product roadmap Better Pre-sales experience

Incentivized

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

Incentivized

• Helps get contents updated and shared very quickly
• Ability to have team work based on standard templates ensures content presentation is inline with organizational standards
• Lack of DB and templates makes it easier for interns to come onboard and develop contents - this is super cost effective

Incentivized

• 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.