Drupal vs. Optimizely Content Management System

We developed a corporate website using Drupal, which features a large number of static pages and several dynamic functions, including a contact us form, location finder, and job posting. We utilized Drupal with some customization to achieve the desired functionalities. We have also worked on e-commerce sites using Drupal, and there is a scope for improvements, specifically in cataloging.

Incentivized

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

• Content Types... these are amazing. Whereas a more simplistic CMS like Wordpress will basically allow you to make posts and build pages, Drupal 8 gives you the ability to define different types of content that behave differently, and are served up differently in different areas of the website.
• Extensibility... it scales, ohhhh does it scale. They've really figured out server-side caching, and it makes all the difference. Once a page has been cached, it's available instantly to all users worldwide; and when coupled with AWS, global redundancy and localization mean that no matter where you're accessing the site, it always loads fast and crisp.
• Workflows... you have the ability to define very specific roles and/or user-based editorial workflows, allowing for as many touchpoints and reviews between content creation and publication as you'll require.

Incentivized

• 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

• Security and new release notifications are a hassle as they happen too often
• Allowing them to write PHP modules is a big advantage, but sometimes integrating them is a small challenge due to the version the developer is working on.
• Steep learning curve, but worth it

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

I really like Drupal, and besides the one major issue with not being able to update from version 6 to version 7 and I am happy to continuing using it. Hopefully as time goes on they will make it easier to upgrade or provide better tools for mid-level web designers like myself to build out new sites without the help of expensive 3rd party's.

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.

It has a very steep learning curve. When starting with Drupal, the functionality and setup have to be learned, which is complex in comparison to tools like WordPress. Drupal is more powerful and can create a wider range of applications, but it definitely has a learning curve. I would recommend it to anyone who wants to make a dynamic web application bigger than the scale of a WordPress blog.

Incentivized

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

Drupal itself does not tend to have bugs that cause sporadic outages. When deployed on a well-configured LAMP stack, deployment and maintenance problems are minimal, and in general no exotic tuning or configuration is required. For highest uptime, putting a caching proxy like Varnish in front of Drupal (or a CDN that supports dynamic applications).

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

Drupal page loads can be slow, as a great many database calls may be required to generate a page. It is highly recommended to use caching systems, both built-in and external to lessen such database loads and improve performance. I haven't had any problems with behind-the-scenes integrations with external systems.

Incentivized

As noted earlier, the support of the community can be rather variable, with some modules attracting more attraction and action in their issue queues, but overall, the development community for Drupal is second to none. It probably the single greatest aspect of being involved in this open-source project.

Incentivized

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

I was part of the team that conducted the training. Our training was fine, but we could have been better informed on Drupal before we started providing it. If we did not have answers to tough questions, we had more technical staff we could consult with. We did provide hands-on practice time for the learners, which I would always recommend. That is where the best learning occurred.

The on-line training was not as ideal as the face-to-face training. It was done remotely and only allowed for the trainers to present information to the learners and demonstrate the platform online. There was not a good way to allow for the learners to practice, ask questions and have them answered all in the same session.

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

Plan ahead as much you can. You really need to know how to build what you want with the modules available to you, or that you might need to code yourself, in order to make the best use of Drupal. I recommend you analyze the most technically difficult workflows and other aspects of your implementation, and try building some test versions of those first. Get feedback from stakeholders early and often, because you can easily find yourself in a situation where your implementation does 90% of what you want, but, due to something you didn't plan for, foresee, or know about, there's no feasible way to get past the last 10%

Incentivized

I was not fully involved.

Incentivized

Drupal's capabilities outpace WordPress by miles. Drupal is more customizable, scales better for larger companies and has advanced content types. If you own a small business or work at a startup company, I would recommend WordPress but if your firm is trying to scale and you have more than 50 employees I would recommend Drupal.

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

Drupal is well known to be scalable, although it requires solid knowledge of MySQL best practices, caching mechanisms, and other server-level best practices. I have never personally dealt with an especially large site, so I can speak well to the issues associated with Drupal scaling.

Incentivized

• Drupal helped us launch a creative, marketing- and product-focused website with custom coding integrations tailored to our goals.
• Drupal allows us to rely on secure and consistently updated core code.
• Drupal's code taxing on the server does start to get a bit heavy as you go along with customizations, so at some point, we decided to stop. We want to ensure our Google Page Score remains high, including paying close attention to page load speed.

Incentivized

• 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