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
Adobe Commerce (Magento Commerce)
Score 8.0 out of 10
N/A
Adobe Commerce (Magento Commerce) provides companies with a platform to manage, personalize, and optimize the commerce experience across every touch point and across the customer journey. ACC is built on Magento Commerce Pro and is integrated with Adobe Experience Manager. It was originally developed as an open-source eCommerce content management solution by Varien, Inc. Varien was acquired by eBay in…
Drupal requires less to no coding abilities to spin up sites. Even if someone is preparing to develop sites that require technical know how then Drupal provides role based systems to seperate developers from content writers. Drupal 8 and 9 now have a vast array of plugins. Now …
Drupal is certainly a more complex animal, comparatively. But its power lies in its flexibility, extensibility, and stability. And the API is fantastic. There's really nothing else like it.
We decided to go with Drupal because of the immense community and library of add on modules available within drupal as well as the availability to customize it and finally the vast availability of developers also helped sway our choice to go with Drupal. Drupal had the best …
Drupal has the best community and support system of any other CMS that I have used. Drupal is more flexible from A-Z including installation, building and customizing the CMS. The only other (free) CMS that is close, in my opinion, is Dot Net Nuke.
Drupal is better than all of these other products 10 times over simply because you can do anything that those other products can do and so much more. You'd need a combination of those products to do what Drupal can do all on its own. Each of those products have inherent …
We chose Magento for our e-commerce stores vs. Drupal Commerce because of the ease to set up and the expansive list of features Magento offers. We're glad we partnered with Magento for our clients. Drupal's setup time is too costly to set up for most clients we've talked to and …
Well, I'm definitely biased, I've been working with Drupal for 12+ years, and I can say it's appropriate for any size/scale of a project, whether it's a small catalog website or a huge corporation. If I want to dial it down to a specific use case, Drupal is best what most customers/clients that have high-security standards, and need to have extensive editorial experience and control over their website's architecture. Due to its core design, Drupal can connect with each part of its own and any external third-party resources quite easily. For a less-suited scenario, I might say that if you don't have enough budget to get proper work done, sometimes just using WordPress with a pre-designed theme might sound better to you, but if you have the budget and the time, always go with Drupal
Ultimately, if a company is looking for a solid industry-known E-Commerce system, Magento Commerce does exactly what it's intended to do. The headaches start when your company wants to start getting granular in customizations of the platform to meet specific business needs (which every company eventually has). This becomes a major issue down the road when trying to upgrade said customizations as the core software updates.
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.
Magento Commerce Cloud allows us to develop our own custom solutions for problems that we need solved.
Magento Commerce Cloud can also be integrated with many of the third part vendors that we use. This has made many implementations go very smoothly and tends to be much quicker than developing our own custom solution.
There are many features available right out of the box. Many of them we have not implemented yet, but it is great to have them available to us when we are ready.
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.
The platform is difficult to tune and can be slow. Even with expensive best in class hardware the platform performance can be an issue. Even with caching poor coding can lead to unacceptable performance and user experiences.
The total cost of ownership for the platform can be quite high as a great deal of technical expertise is required to modify, develop, troubleshoot and maintain the platform. The costs of initial development are only a down payment on what a Magento store will cost. For mid size companies with substantial web revenues this can be overcome for smaller businesses the total cost of ownership may be prohibitive.
Security of the platform can be an issue. Magento is often targeted by hackers and much of the security is the responsibility of the store owner.
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.
Magento is well-supported by a big development team at eBay, which not only addresses bug reports very quickly, but also is constantly working on improvements to the platform. The wealth of Magento third party modules ensures that the platform will be up to date with future changes to Payment or ERP systems. Security is always a concern and with the Zend framework as a foundation, Magento has had very few security-related patches since I have started to work with it
It's a great CMS platform and there are a ton of plugins to add some serious functionality, but the security updates are too complex to implement and considering the complexity of the platform, security updates are a must. I don't want my site breached because they make it too difficult to keep it up to date.
Magento offers lots of templates and themes to customize the look and feel of the store, and even optimize it for mobile phones. The have an extensive library of forms and templates.
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 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%
Drupal is community-backed making it more accessible and growing at a faster rate than Sitefinity which is a proprietary product built on .NET. Drupal is PHP-based using some but not all Symphony codebase. Updates for Drupal are frequent and so are feature adds.
Magento scales much better than any of the other software when it comes to very large e-commerce websites. But all the other options are more user-friendly for smaller sites as there is a bit of a learning curve in learning to manage Magento. Customization is better along with WooCommerce and OpenCart as self-hosted solutions vs. BigCommerce and Shopify which are hosted. Magento should be the first choice for large, extensive e-commerce solutions,but for smaller stores, I would recommend the others first.
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.
Drupal has allowed us to build up a library of code and base sites we can reuse to save time which has increased our efficiency and thus had a positive financial impact.
Drupal has allowed us to take on projects we otherwise would not have been able to, having a further impact.
Drupal has allowed us to build great solutions for our clients which give them an excellent ROI.
Magento definitely lets us get a return on our investment. Because we have developers who can customize Magento to our needs, we have been able to create a beautiful and effective website, run promotions, and serve up customized product display pages that are effective and beautifully branded.
Magento has also caused a lot of time to be invested in doing something that seems simple, but without a lot of knowledge, end up taking far more time than could otherwise be better-spent.
We have had to outsource some of our development work due to Magento being developer-focused rather than marketer/merchandiser-focused. I've used other website management software that is comparable to Magento's capabilities but is far easier to use, that even someone like me (with basic HTML/CSS skills) can customize the front-end without requiring a back-end developer to intervene.
