Optimizely Content Management System vs. Plone

Very much if a business is doing a rebrand, for example, or a digital transformation, the DXP product is super competitive. The managed services that provided around the infrastructure and all of the moving parts really, really works well. It just makes life as a developer very easy when ultimately you just have to do the code and deploy it out and don't worry about the environment infrastructure. I think it's really, really well and fits in really well with that. Areas where it's not so great in my experience, I would say, well, I've already mentioned kind of the CMS to SaaS product, but also just in general it feels like we're going through a bit of a transition period with the documentation at the moment. So when new features are rolled out or the product catalog expands, the documentation isn't always the best or streamlined. That can make life as a developer a little bit work at the times.

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.

• Folder structure - I was on Magento 1.x & 2.x for 10 years, which had no folder structure for blocks or images - it was very difficult to find things. We couldn't keep anything straight without it.
• The fact that it knows what block or image is being used and links to where it's being used is pure gold. It prevents deletion of needed elements.
• I like that I can drag a block or image somewhere new and it doesn't break anything.
• Our search of blocks and images is now working, that's very helpful.

Incentivized

• Rock-solid technology stack. The python/Zope/Plone stack is as solid as anything else out there.
• Highly customizable TTW, if needed, via the Zope Management Interface, or Diazo XSL-transform theme design.
• Good support from core developers, lots of solid add-ons which address just about any needs.
• Amazingly customizable workflow, permissions and security management.

Incentivized

• promo types, several have been released that do not work as they are advertised/labeled which has caused us to make custom promos for just about all of them where we've actually fixed the functionality. The OOB types are completely unreliable
• promo exclusions/sorting -- this is very buggy, and some of this would normally be "out of the box" like no two order discounts should ever be able to stack. This gets incredibly difficult to manage when you have 75 active promos at a time.
• asset management - replacement files with same name aren't recognized even when the first version is deleted, this creates a mess in asset folders - nothing can be successfully deleted from epi asset library
• html automatic edits -- issues when typing in either content page links or asset links, epi always adds random characters to the end (?"Epieditmode=false,6789" for example, which doesn't break content, but does make it more difficult for the team to use non-epi html tools to build or edit
• auto dimensions on images -- when adding an image in the html, you have the address exactly, but any other way causes the editor to put width and height dims on the code, making the image warp in mobile, this is adding steps to undo the automatic edits, they are completely unhelpful
• blogs - we are running a blog in Opti that is compeltely manual, every "related article" and every "articles about x topic" block is hard coded, there is nothing dynamic in the content library which is frustrating, and creates a huge time suck for articles across the site, every time there is a new one, that's 10+ manual page updates

Incentivized

• Bullets and formatting sometimes make it difficult to add text to an existing paragraph. The 'code' button is useful in those cases, but only to those who know html.
• Sometimes the pages don't save correctly and you use information.
• Uploading and displaying images is a bit too much work.

Since I work on the implementation side of things, and do not directly own licensing for Ektron CMS, I have to base this rating off of how I think it will be received or presented to customers looking to start a new site deployment. I try to remain CMS agnostic, though my specialty is with the .NET and Microsoft stack. Because of the experience I have working with Ektron, I tend to be more forgiving with the shortcomings as I am familiar with how to work around them or past them from experience. Being familiar with the community available also helps, as you become familiar with the best approaches to find solutions to your issues. Each product has it's ups and downs and all of them are only going to be as good as the company or development team implementing them can make them. This is EXTREMELY important to remember when choosing a CMS, as it can make or break your expensive investment.

Plone has been used for more than ten years and it already has an interesting roadmap for its future. I do not know any other open source CMS with the same story of continuous evolution and security track. Interesting new features are added at each release and new modules are created continuously

From our editors perspective they find the CMS system easy and to clear to use. Our developers find it very easy to design on and appreciate the level of service support available. It's also always evolving and getting better every year. We find this investment reassuring and encourages us to try keep pace and see how we can continue to push the envelope and continue to improve all aspect of our websites and online touch points.

Incentivized

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.

Unplanned outages or errors are fairly rare in our instance. And when there are issues, they're usually fixed fairly quickly

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.

I attended multiple trainings/tutorials early in the process. The vendor-supplied content about Optimizely was engaging for users/attendees (I often analyze training content, compliance programs, governance plans), which helps our OCM people by having good "word of mouth" about the product long before a rollout ever happens. I actually when the user-focused portion of the Optimizely Academy twice in 2022 to ensure I had a grasp on operability and to be able to support the training and OCM efforts

Incentivized

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

Ektron is one of the best solution for .Net platform. Over the years have improved the performance issues that the previous versions had. My only complain is right now you can't do Page builder pages if you choose to have a MVC architecture

Well organized, professional training with good materials and instructions

I was not fully involved.

Incentivized

Optimizely Content Management System takes the best bit of previous platforms and simplifies them without removing the more advanced features but not making the necessary to get things going. allowing for any user to jump in and start working is a massive help but empowering power users to take advantage of all its features.

Incentivized

Plone is much harder to learn then Wordpress. Development in Wordpress is learnt in day's, where development in Plone really takes years to get to the full depth. That said, once you're able to develop in Plone, is it a rock solid system, with readable code. In my experience Wordpress websites need to be updated so often, and the code feels bad organised. I have been building Wordpress websites, choosing Wordpress only when the client has almost no money. But I can never deliver the quality I want to deliver when using Wordpress. Plone does offer the possibility to deliver professional websites. As for Joomla, in the past I have done some Joomla development, but the whole CMS-paradigm could not settle in my brain. Being a web developer for over 15 years now, Joomla always felt contra-intuitive. Let alone the task of teaching this to my clients. Plone is now my only choice. It gives me a fast development-cycle, a user-friendly CMS and a rock stable and very secure system.

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

• Flexibility with design that allows us to work towards our mission of 'Tennis Opened Up'
• Speed of deploying content, meaning users can really on us for the most up-to-date content on tennis in Britain
• Ability to have different logged-in areas for different user groups, allowing us to create more bespoke and personalised experiences

Incentivized

• We thought that tapping into the user/content management tooling of Plone would be a good and useful thing, however it turned out to be a major pain to tie into those parts of Plone.
• I wish we would have built the extra functionality completely outside Plone and found a way to integrate it. It would have been much easier.