Jadu CMS vs. Plone

Jadu CMS is not currently geared toward the academic side, but more of the business/government types of organizations. Things can be tweaked to suit your needs, but sometimes there are limitations. The programmers are very helpful in assisting with that.

If you have some in house programmers, and you can get developer training, they will be able to program their own custom widgets to use on your website. We did not have programmers but managed to create a few simple widgets.

There's also a marketplace to look for other widgets that you could use on your site.

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.

• Reliability. The LAMP-powered server/software rarely has any problems and can handle hundreds of concurrent users without issue. It was developed with scalability in mind.
• Ease of Use. Our users find the backend GUI very easy to use. The layout is intuitive and follows the same format throughout the entire control panel.
• Powerful. Even if it doesn't do something you would like it to out of the box, the code is well formatted and easy to customize.

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 custom HTML editor can be frustrating
• Does not provide advanced controls and looks as well as some competitors
• Menus to add media content are litigious and require many clicks

• 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 decided not to give it a 10 because I don't know what else is out there in terms of CMS products, and there's a bias when you've only been exposed to one product. At my current job, I used Jadu sparingly but it's easy to get reacquainted with the software and the look and feel of the CMS

We have critical systems running on Plone so will need it in the future.

Free to use since its Open source, so we don't have to worry about licence costs.

We know how to use and develop Plone and it has no limits.

For the common user, Jadu is very easy to use and to understand. For the more complex user/administrator, there's a lot of power to be harnessed in HTML editing, creating widgets, editing styles, creating workflows, and other advanced features Jadu can work up for the customer.

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.

The new user interface in Plone 6 is even better, it is super fast, has lots of different blocks for enhancing the page, has flexible layout system and is easy to extend with more features.

Our Plone sites are very robust. We have critical systems on Plone and we have been running sites on Plone for over 20 years with very little unexpected downtime.

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.

There are not too many Plone companies in the world. But the ones who are, are high level professionals

I have been participating Plone training and the trainers have always been professional. Materials were good and the instructions clear

Well organized, professional training with good materials and instructions

Jadu is miles behind these and many other CMSs. The others are much more up to date with their code and ease of use. The ability to customize other CMSs is much easier and the code structure actually makes sense. Jadu was selected because it had a portal out of the box.

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

Plone has no limits. We have massive sites and can run them just fine

• More modern design compared to our old website software solution.
• Much easier to navigate and find content, as well as searching.
• More reliable and efficient in terms of server resources.

Incentivized

• The impact Plone has had at the University of Oshkosh is as follows: this software allows student workers to learn about IT departments and CMS's in a user-friendly way. It gives many students great jobs that look great on their resumes.
• Since there are great training manuals for Plone, there is increased employee efficient in the workplace. Training doesn't take long, and if there's ever a question, the Plone manual is a great tool to refer to.
• If an employee using Plone quits, its easy to find someone to replace them with quick training and great resources.