Drupal vs. Optimizely Commerce Connect

If you want to set up a basic Not For Profit (NFP) Membership system and content base, Word Press is easier than Drupal. However, if you have specific needs that require a fair bit of customisation then Drupal is the best CRM available. If the webmaster is confident with PHP and SQL, Drupal allows a lot of creativity.

Incentivized

Our experience may be unique because we opted for an Optimizely team to implement our website/console set-up and connection to our PIM and ERP. The experience may have been different with a 3rd party or it may not have. That said, we have been live with our primary website for almost 2 years and I still do not consider it was ever "done". We have been going back and forth on functionality issues and bugs since launch. I have low confidence that changes made the previous day will 100% be online the next - so my team rechecks the work they did the previous day to ensure everything is online. The addition of a second channel and enhancement requests have compounded the issues. I feel this product would work fine with singular or less complex market SKU offerings.

Incentivized

• Drag and drop functionality is easy to use
• Easy to switch between straight text and HTML content
• Ability to easily have multiple environments so that pages can be built in b/c-stage before they are approved and published
• Solid user experience where it's clear how to navigate the platform

Incentivized

• Episerver has a robust discount engine. This engine, combined with "visitor groups" allow our marketing department to categorize customers and offer a variety of discounts to targeted customers at specific times.
• Episerver has a full-featured, storefront experience that can handle everything you might want for an e-commerce website.
• Episerver offers A/B testing that can be helpful for trying out new content ideas and tracking the results.

Incentivized

• This is not an easy CMS to work with if you don't have a good understanding of website development. It isn't "plug-and-play" like Wordpress or Shopify.
• Over time, doing major updates to the system can be taxing, especially if you aren't well-versed enough in doing system updates in line with your "child" theme and code.
• The CMS can become somewhat cumbersome with server resources if not carefully optimized while you build and customize it to your liking.

Incentivized

• Support. Episerver used to have direct support and access to the tech team to discuss and resolve issues. The new support portal is not enough for developer needs.
• Quality Assurance. We find issues in the Episerver code that should have been resolved in QA before release.
• Sales. Episervers sells the framework as a solution while showing Alloy. While it helps Episerver sell more, it puts the implementation partner into trouble as the client thinks they bought the solution. Episerver does not provide a solution. It provides a framework that you can build a solution on.

Incentivized

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.

Really want to be able to spend more time and resources on rolling out new things with Episerver but at the moment we seem to be fixing alot of issues and pain points with the way our system was setup.

Incentivized

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.

Incentivized

The administrative interface is largely intuitive and relatively easy to use. The complexity of business needs and ability to customize can affect this (i.e. you have to set up and develop with the user in mind), but the basic structure is largely solid. There are some areas of redundancy (such as Commerce Manager overlapping with other administrative areas) that can sometimes cause confusion or offer some functions in one place, whereas other related functions are managed on a completely different page.

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

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

We had an incredible team at Episerver Supporting us with the go live, reviewing our integration, and pushing our integration partner to deliver a quality product

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.

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

Fully understand what is OOTB feature of the platform before proceeding to develop. Then implement a customization of key features once you can prove they are working as OOTB to make them more user friendly and productive for the business. Eg pre order and e gift card

Incentivized

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.

Incentivized

Optimizely Commerce Connect offers a very wide range of features for admin users. There is less a need for an IT specialist or programmer to be involved when changes need to be made.

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

• Given the endless possibilities that Drupal can have, we tend to have great support going on when we get a website launched
• It has become much much faster and easier for us to launch a new project due to reusability
• Configuration management in Drupal helps greatly with CI/CD, saves us costs

• Positive: We have a usable website - better than what we had before and we are seeing a constant increase in adoption.
• Positive: Counter associates are using the website to help customers.
• Negative: Too much time being spent QCing previous work.

Incentivized