Drupal vs. Kibo eCommerce

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

Mozu is currently not suited for use at any company, small or large. The bugs and lack of features and integrations make it too difficult to use.

• 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

• Single admin tool for multiple sites is a huge plus. Eliminates much duplication of labor and a shared code base is also much simpler.
• Native responsive design in the latest version is great.
• Dynamic product categories is a big win.

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

• Prebuilt Integration - There is not currently a large number of preexisting integrations, but custom integrations are fairly quick
• Time to Deploy - Don't get me wrong, We have deployed in the timeline we expected, but if you are trying to get something off the ground fast, Kibo might not be right for you. It is a robust platform that take some time to get up and running.
• Complicated Shipping - if you have a complicated shipped process, you might want to look for a tool to help, Kibo does not have very robust out of the box shipping capabilities.

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.

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

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

One positive note is that I have always been able to get someone on the phone in support whenever I have called, even at 1 AM. Getting someone on the phone is only half the battle though. In the first few months of using Mozu it often seemed that support didn’t know anymore about Mozu than we did. This has slowly started to change, but as a daily user you are likely to be on par with support in terms of knowing what to do when you encounter a problem. The support phone number is really most useful for having them put in a support ticket for you rather than typing it all out yourself and emailing it. It is very rare that the support reps are actually empowered to solve the problem at hand. Unless the issue you are having is user error, they will just take your information and pass it on the proper department. Your request or problem will then be ignored for months on end. Some day, it might actually get fixed but you are unlikely to be notified that this has happened. Most of these issues are assigned an internal ID that they use for tracking. Support is more than happy to pass this ID along, but it is useless. There is no way to actually see where the issue lies in the endless queue of similar issues.

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

At the time of our implementation Mozu did not have any processes or procedures set up around going live. We basically were forced to just wing it and hope for the best

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

We had a custom, in-house ecommerce website before moving to Kibo. It was brittle, slow, and wasn't going to scale nearly well enough or fast enough to keep up with our requirements

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

• Kibo has always delivered rapid & exceptional support to our organization
• Kibo has been cost-competitive when considering other vendors
• The platform continues to add value without requiring substantial additional investments