Likelihood to Recommend
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
with a pre-designed theme might sound better to you, but if you have the budget and the time, always go with Drupal
Read full review
A colleague here being another business. Magnolia is on its way to being a 'good' product but the 6.2 implementation simply isn't there yet (6.2.26 as of this writing). The admincentral UI could use a complete overhaul to be better streamlined for devs and content editors (the two who actually use it).
Read full review Pros 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. Read full review Use of YAML to define content models with code. Versatility of defining actions for custom handlers. Reloading classes when code is modified in a local dev environment is nice. While it doesn't seem to work when changes extend beyond the method body (i.e., adding methods), it remediates the pain of long startup times. Read full review Cons 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 Read full review As a developer the learning curve is long, you can start developing relatively quickly but getting to know the platform in depth takes time. Having a history of modifications not only at the page level but also at the Content Apps level would be very useful. Read full review Likelihood to Renew
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.
Read full review
We have invested a lot of time and energy into tailoring a solution that works for the company.
We think the new features in v6.2 will help us get to the next level
We also don't have the resources to rebuild a website platform from scratch even if we wanted to
Read full review Usability
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.
Read full review
I see two main pains: 1. A new user need training to be able even to start using the platform, the onboarding is difficult 2. The platform needs a server with a relevant amount of memory to run properly, the dependency on the memory is really high
Read full review Reliability and Availability
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).
Read full review Performance
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.
Read full review
I gave [it] 7/10 only because of the loading time of pages. Otherwise, I think it deserves an 8. Normally this is not an issue per [se] but considering the rating matrix and as I have been asked to honestly write about it. Yes, the page loading times could be improved.
Read full review Support Rating
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.
Read full review
You always get an answer based on your SLA. But you always get a solution. That's the successfactor in this case. To often i was frustrated about people in a company without even a clue what there product is about or how to solve a problem. Magnolia's Support Team does a very good job and try to help you in most of the cases
Read full review In-Person Training
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.
Read full review Online Training
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.
Read full review Implementation Rating
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%
Read full review Alternatives Considered
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.
Read full review
Prior to using Magnolia as an enterprise CMS solution, different teams leveraged different website platforms including
, and others. While these other platforms may be slightly more user friendly to the content editor, they don't offer nearly the same amount of customization and digital best practices out of the box that are customizable by web development teams like Magnolia does. The other solutions may work better for a quicker/simpler web implementation without technical resources but don't have the depth and breadth of capability and functionality that Magnolia has and fall flat.
Read full review Scalability
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.
Read full review Return on Investment 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. Read full review Magnolia has brought about positive impacts. For instance, we need not outsource web design and marketing services because thanks to this software, we can handle most work inhouse The software is affordable with no compromises on capabilities and therefore it is gives us value for money. The templates makes the whole process easy Read full review ScreenShots