Drupal vs. Ion Interactive vs. Magnolia

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

If you want to choose a quick start template and fill in the fields with your content, Ion will be fantastic for you. We've done this with whitepapers and quizzes and it's been great and extremely easy to use. If you have an exact idea of what you want, and a background in web development, you may get frustrated. Ion has some quirks that make it tricky to fully customize - everyone once in a while I really just want to go into the HTML and make some changes, but can't. If you are looking to reuse a piece of content for specific targeting (industry or account-specific), Ion is great. The dynamic substitutions are great and very helpful.

Incentivized

Magnolia is a very capable DXP, that provides client with lots of flexibility in composing its own stack. While the core of the platform is a content management system, the open architecture of Magnolia DXP allows it to connect to any platform, allowing client to extend the capabilities. One scenario would be a centralized content hub - where through a single platform, content authors can choose which channel to distribute what content. For example, long form content for consumers viewing on a laptop, short form content for those using a mobile browser. This allow the client to personalized the experience based on channels. Another scenarios would be leveraging on GenAI - using Magnolia's built-in connector to ChatGPT. If that is not the service that one desire, you can always connect to another AI service such as Google Gemini. With GenAI, connected, content author can use AI as co-pilot to help them scale up their content production.

• 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

• Quick Starts make it so easy to get started.
• Real-time updates are awesome and save a ton of wasteful process.
• The combination of user friendliness for simple things and the flexibility to do more complex things is great.
• Chat support is excellent and deeper-dive support has been super helpful.
• The ability to use these tools in the cloud or embedded has given us tactic flexibility.

Incentivized

• Speed of development - time to delivery from zero to MVP was excellent
• Ease of use - the authoring experience is very easy to build and train
• PAAS/SAAS - the managed service platform removed the traditional overhead of running in-house technologies, meaning we could focus on value add, with less time spent keeping the lights on.

• 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

• Ion University, while stacked with a wealth of information, is difficult to navigate from a troubleshooting perspective. The tutorial videos are all very helpful, but they are also very long. Sometimes I would want to search for how to address a particular issue I was struggling with and it would be a two-minute segment buried in a 45-minute video.
• Again, getting back the self-guidance side of things. I think a lot of the tutorials are set up in a way that makes sense to Ion, but not as much to the end user.
• I think the controls admins use when creating new users could be a bit more straightforward.

Incentivized

• The documentation provides samples that are often out of context, and difficult to know where the provided example code should be implemented. More tutorials providing the full project or step-by-step instructions on how to implement subject material would help greatly. Baeldung is a resource I would consider the gold standard in how this is done in other spaces.
• The use of JCR and Nodes makes object serialization/deserialization painful. Jackson compatibility or similar would be a welcome enhancement to the developer experience. Maybe leveraging code-gen from light modules to build model classes when possible could help accomplish this.
• Modifying the home layout from light modules is frustrating. It seems that any configuration overrides made merge with the default rather than overwriting, which makes for a difficult combination of guess-and-check while referencing the documentation to see what should be in each row/column when making changes.
• Including "mark all as read" or "delete all" in the notifications app would be a great quality of life improvement. It seems that by default, users have to individually select messages and operate them.

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.

We use it for every landing page and we plan on only doing more dynamic content creation. We dont see that option coming in-house any time ever in the future. ION has a very robust platform for us to work with that really allows us to do more for our customers in regards to having the one-to-one conversation.

Incentivized

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

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

Usability is straightforward, with extensive documentation and tutorials provided to ensure landing pages are built to specifications and can be optimized for performance. Built-in platform funnels give insight into customer dropoff, success/failures, and conversions (at a glance). Setting up a landing page can be done quickly and easily, with numerous integrations (CRMs like SalesForce, for instance) supported

Incentivized

We've shown it to a number of users both clients and our own team and despite initial apprehensions, they "get it" very quickly. It's intuitive and friendly and quick to perform daily tasks. We once had a client tell us "Using Magnolia makes me smile" which says it all for us.

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

Sometimes the editor can be a little slow.

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.

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

The ION support team is amazing. There has not been a single issue they they could not solve for me. If there is a feature or request that they do not have, they have even, on occasion, created custom scripts for our team. *Update 6/5/17 - ION has continued to delight on multiple occasions. I appreciate their attention to detail and ability to solve whatever issue I have. After 3+ years of use and support, ION still has my full endorsement.

Incentivized

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

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.

They offer a great amount of online training, videos, articles, etc. There is usually an answer available if you run into an issue. I would recommend taking advantage of the online training they offer. I wish I would have done it sooner.

Incentivized

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

There were a lot of things we learned about the tool once we really got in and got our hands dirty. Being hands-on was essential for our team to be able to utilize ION in the most effective manner.

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

I was not the decision maker to choose this over Uberflip, but the UI is much more appealing to me. It's incredibly easy to use, clean, and from a backend standpoint, it requires little to no tech savvy'ness. Our team has really enjoyed using it and has required no training what-so-ever.

Incentivized

I've used several CMSs like AEM and EpiServer, and comparatively, they all excel at different things. Magnolia is the best to develop for/against. Episerver has the best/most fluid UI in terms of content editing, and the overall admin experience AEM is just all around sucks.

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

Separate client portfolios enable scalability, however, some elements are still grouped for all accounts so it's difficult to scale for an ad agency with multiple clients. Would prefer totally separate sections of the platform for all clients with each element housed separately.

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

• Though we have not had the service long enough to see any measurable outcomes, we've been able to create interactive web content faster than ever before
• The speed with which we can build interactive pages and re-use assets has been critical as projects we've done with Ion have made their way around and more and more internal clients have said "me too" for their own projects
• It is very pricey at $28K for the base annual subscription (dropping to $24k after the first year), so depending on your budgetary situation, that may make no sense for your team--but we had contract money set aside for a company to build us a microsite for around the amount, so we just used it for Ion instead and will now be building the microsite ourselves using it

Incentivized

• 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

Incentivized