Plone vs. TYPO3

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.

TYPO3 is great if you need to connect some systems in company to work together: like ecommerce + CRM + ERP + MRP and build an Extranet for partners/dealers where they can order your products, see particular BOM (bill of material), paid/unpaid invoices and use email marketing on top of it. You can do it but keep in mind that you will need a dedicated hosting, well organized admin(s) and some handwritten code. For simple blog TYPO3 is also a good choose, but WP would be better I think.

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.

• open source - do what you want, and even if you dont know how to do it - someone will do it for you
• more secure than others (Joomla, WP, Drupal) - thanks to dedicated Typo3 Security Team
• modularity and diversity - a lot of plugins/extensions
• workflow and user roles - feel free to build a workflow templates ie. for documents routing
• assets management - no matter is it a video, audio or text file, you can REALLY manage it.
• typoscript language - sometimes JS is not enough

Incentivized

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

• compared do Wordpress - far less community support
• when you run a simple blog - it is simple as piece of cake. But if it is a large news site, with many user roles, extensions and permissions - it may be hard to find an admin that will organize and keep that stuff working.
• server resources: so you want performance and speed with all that modules enabled? make sure that you have dedicated server in most cases. WP works much better here.

Incentivized

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.

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

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

• more complex and elastic revoke system (undoing changes for multi-administrator systems) PHP/JS and TypoScript language
• LTS - long ter msupport (bugfixes and updates)
• usage rights and permissions (much more advanced thatn in WP/Joomla)
• separation of design and content (in WP also but here is complex)
• many plugins to integrate with external systems
• several portals may be operated from a single admin/install

Incentivized

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

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

• + 1 platform that handles connections to 11 external systems (CMS, CMR, ERP, MRP, accounting, controlling, email marketing etc.)
• + still lower TCO than commercial systems (Oracle, Microsoft)
• + LTS - long term support - can provide you an updates or bugfixes
• - resource consuming (forget about shared hosting in large projects)

Incentivized