Drupal is a free, open-source content management system written in PHP that competes primarily with Joomla and Plone. The standard release of Drupal, known as Drupal core, contains basic features such as account and menu management, RSS feeds, page layout customization, and system administration.
N/A
Optimizely Content Management System
Score 8.6 out of 10
N/A
Optimizely Content Management System (CMS) is purpose-built for marketers, and fully composable for developers. The CMS supports the end-to-end content lifecycle, helping users to deliver on-brand, high-impact digital experiences that 'wow' audiences.
When selected, Drupal was the tool that had enough power to create a robust intranet while not being too overly complicated. It allowed for custom integrations that were developed from IT, and it was able to handle the mass amount of users we needed, many of whom are not overly …
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 …
Episerver outranks these products in most cases. There are some functions in each product that you would love in Episerver but when you sum it up Episerver is the greatest :)
Optimizely CMS is part of a more composable suite when it comes to DXPs. With that, some other systems like Sitecore Experience Platform are monoliths, which makes the development and maintenance of those products fairly complex (this includes system architecture). In our …
Optimizely Content Management System doesn't invent complexity. It just sticks to common patterns and recommendations from Microsoft. This makes it extremely easy to learn and onboard new developers, and it makes it easier to upgrade and maintain.
EpiServer competes with both Drupal and WordPress, hands-down, in terms of both efficiency as well as usability. I would say EpiServer is actually a lot easier to use than Drupal was for me personally. EpiServer wasn't confusing like Drupal, and had an easier learning curve.
Features
Drupal
Optimizely Content Management System
Security
Comparison of Security features of Product A and Product B
Drupal
7.8
72 Ratings
5% below category average
Optimizely Content Management System
8.5
167 Ratings
3% above category average
Role-based user permissions
7.872 Ratings
8.5167 Ratings
Platform & Infrastructure
Comparison of Platform & Infrastructure features of Product A and Product B
Drupal
7.2
67 Ratings
7% below category average
Optimizely Content Management System
7.9
164 Ratings
2% above category average
API
6.562 Ratings
8.0157 Ratings
Internationalization / multi-language
7.858 Ratings
7.9125 Ratings
Web Content Creation
Comparison of Web Content Creation features of Product A and Product B
Drupal
6.2
76 Ratings
23% below category average
Optimizely Content Management System
7.8
192 Ratings
0% above category average
WYSIWYG editor
5.769 Ratings
7.7176 Ratings
Code quality / cleanliness
7.973 Ratings
8.2164 Ratings
Admin section
6.276 Ratings
8.1176 Ratings
Page templates
5.575 Ratings
8.2170 Ratings
Library of website themes
5.466 Ratings
7.496 Ratings
Mobile optimization / responsive design
6.370 Ratings
7.9174 Ratings
Publishing workflow
6.674 Ratings
8.2170 Ratings
Form generator
5.970 Ratings
6.7129 Ratings
Web Content Management
Comparison of Web Content Management features of Product A and Product B
Overall, I would give my rating of Drupal a 7/10 because there is an easy user experience for those without a website background but there is some technology work required to build more website capabilities that aren't as user-friendly. Drupal is specifically well suited to update content (like changing Relationship Manager cards when there is employee turnover), post announcements (putting up a holiday banner to let our customers know the dates we will be closed over Thanksgiving, Christmas, etc., and creating a sophisticated website hierarchy of pages (for our firm, several dropdowns depending on if you're looking for personal banking, business banking, investment banking, about us, etc.).
If you want to build a website quickly there are plenty of ways to do so with some great examples and plenty of support both from the company and in the forums. if you want to build a more complex structure you can but be ready to spend the time to build exactly what you need as a solid foundation goes a massive way before building out content and making those choices early and sticking with them helps
It has excellent security features and consistent updates.
It allows for extensive customization with the integrated themes and core code, especially when you first install it. This allows our dev team to get creative with marketing initiatives.
There is a large online community of Drupal users that consistently help answer any questions and issues
I think the user interface for content admins is very good and very competitive. And compared to other providers, the technology that CMS in particular has. So the way it integrated the net ecosystem is very well because it follows the MBC pattern. So basically it just allows really simple implementations for what would normally be complex components on any other sort of vendor that's out there.
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.
Magento did have some nice tools for creating product groups or carousels for promotion. Opti seems to be lacking in that.
A blog - maybe this is available and we don't have it installed, but a searchable blog would be very appreciated.
Structured Data/MicroData - maybe it's our install, but this seems to be missing
Meta data: we have access to limited types and need to make a request from IT, it would be nice to be able to access more to adjust for SEO needs.
When in a folder on the BLOCKS tab, it would be wonderful to hit the MEDIA tab and stay in that same folder.
I have some less technical people that will make folders with spaces - which Opti handles, but it would be great if it wouldn't accept a space or gave an error message not to use them.
I think I know why the extra code is added to urls and image links, but it causes issues when taking things from our testing site to the live site. For example, I need to copy the Navigation from Inspect Element on testing to put it in production. I have learned to work around it, but it's not my favorite.
The time and money invested into this platform were too great to discontinue it at this point. I'm sure it will be in use for a while. We have also spent time training many employees how to use it. All of these things add up to quite an investment in the product. Lastly, it basically fulfills what we need our intranet site to do.
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.
As a team, we found Drupal to be highly customizable and flexible, allowing our development team to go to great lengths to develop desired functionalities. It can be used as a solution for all types of web projects. It comes with a robust admin interface that provides greater flexibility once the user gets acquainted with the system.
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.
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).
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.
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.
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
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%
Drupal can be more complex to learn, but it offers a much wider range of applications. Drupal’s front and backend can be customized from design to functionality to allow for a wide range of uses. If someone wants to create something more complex than a simple site or blog, Drupal can be an amazing asset to have at hand.
Optimizely Content Management System is much more feature rich, and less complex that the other CMS platforms we have used. Optimizely Content Management System is more intuitive in how the content is structured and how easy it is to pull blocks of content to create the layout of a page.
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.
