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
Magnolia
Score 9.9 out of 10
Mid-Size Companies (51-1,000 employees)
Founded in Switzerland in 1997, Magnolia is a CMS used to build composable digital experiences. Magnolia helps create fully integrated customer experiences and speeds up digital delivery of content. Magnolia boasts 480 enterprise customers, thousands of Community Edition deployments, and more than 200 certified Magnolia Partners around the world. They further state that their enterprise customers include Sanofi, Generali, the Atlassian, The New York Times, Harley Davidson, and Union…
$3,500
per month
Titan CMS
Score 8.0 out of 10
Mid-Size Companies (51-1,000 employees)
Titan CMS is a web content management system (CMS) used to build public websites, intranets, extranets and portals. Powered by Northwoods, it leverages industry standard MVC for .NET Framework and provides a content management workstation interface to produce performance-driven websites.
In my mind, Drupal and WordPress are the top open source CMSes, and I rarely recommend not going with an open source CMS. WordPress can be great, especially for single developers, but I find that the code structure and extensibility of Drupal makes it superior for many use …
I've used a number of Content Management Systems in the past that have similar features to Magnolia including custom ones that aren't widely used or can be listed, but Drupal is probably the most comparable. I would say that Drupal is more kind to custom code and overall …
Magnolia is not as costly as other enterprise grade platforms and is easier to deploy, more reliable and less resource hungry. It's often also easier to use and certainly easier to use than it's Open Source counterparts. It also manages content in a much more structured manner …
Cost was prohibitive for SiteCore. We liked the support that Magnolia gives us in terms of being an actual Company. We love open-source, but have had problems with Umbraco in the past in terms of upgrade paths etc.
Of all the ones we looked at that met our requirements Magnolia was clearly the best value for money and had a solid background that you could trust and that could take care of you in case of problems.
Putting all together: capabilities, support, community and price... Magnolia is the best combination, maybe not the best on each aspect, but for sure in the combination
Magnolia has an automatic, and speedy social media publication extension, which spread content to all social sites. Also, the insertion of extensions and plugins is more effective when on Magnolia against the opponents. Magnolia admits and adopts diversity, hence, it is a …
I evaluated many CMS products and I’m continuing to evaluate them to verify the new functionality introduced.
I evaluated these products: Alfresco, Apache Lenya, DotCMS, Drupal, Liferay, Hippo, Joomla, OpenCMS. I chose Magnolia because Magnolia offers two licensed community …
It worked great that Titan CMS was developed by a local company (we're both in Wisconsin). Not only that, they have user group meetings twice a year which highlights what others are able to accomplish with the same software - immensely helpful. Support calls are handled in a …
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.
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.
Titan CMS is a good full featured CMS if users are fairly tech savvy. It is under active development and has added significant features through the years.
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.
Utilizing a Filter to determine what shows on a page saves countless hours of configuring content that should be displayed on a page - it's been a lifesaver how easy it is to set up too.
Smart Search takes the search box and makes it magical. Common misspellings and alternate names can still send a user to the proper page!
Data nodes and filters can also be configured to Find a Dealer, Doctor, Location etc. It puts the power into a users hands and makes is easy to use.
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.
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.
I would love to see a "View this Page" button after a page has been updated/published. Every time I publish a new page, I have to open a new browser window, navigate to a different tab, copy the page url "example/example/example" and paste it after "www.mywebsite.com" in order to preview the new page/content.
If Titan and WordPress were in a beauty competition, there is no way that Titan would win. Titan's dashboard, buttons, etc are dated and bland, and is in dire need of a refresh.
A drag and drop to upload feature would be very helpful.
Creating forms is very cumbersome and the pop-up window in which the form is created needs to be revamped. The font-size is much too small and it is not as customizable as it could be.
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.
Titan CMS had a great support system and they helped make my experience go smooth. They offer courses to help people get acquainted, offer support over the phone and are more than willing to make your experience a great one. Once I was familiar with Titan I always found myself wanting to learn more and do more to improve upon the website. Titan makes CMS fun and exciting!
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.
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.
Everything we've needed to accomplish, Titan CMS has been able to accomplish. From multiple levels of user rights, document rights, tagging pages and documents to make filters do the work of content displayed on a page - it's all easy to set up too. Creating a content rich product detail page template and customizing a ecommerce cart to work for those using a dealer network - needing a request for quote, to go to dealers instead of a self checkout.
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.
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.
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 understand that our Web Development Team is very busy, however, sometimes there is a delay in response and a followup email is needed to determine the progress of the issue/question
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.
It was customized to include screen shots of our site and how users can access the content that only pertains to them as well as advanced training sessions for admin duties and everything that goes along with it. Training is in small groups and can be private (your company only) if you like too.
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%
Talk to your project manager for Titan early on in development about minimalizing customizations. It seems obvious, but many times they do what you ask in the respect of "This is how we do it now, make that happen in Titan" vs. think of how Titan can deliver the same results within the confines of the base software. It's not a fault, just human nature.
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.
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.
Clients have access to the online and PDF documentation, also tips and how-tos for the most current versions of Titan CMS in the market. Check out our full documentation library! unlimited Dev/ QA/ Server install. Load balancing, and cluster support included. Upgrade options included free of cost along with unlimited CPUs per server.
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.
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.
Positive ROI by allowing content contributors embedded within departments with the department domain knowledge to update the site directly. More efficient and less centralized spending.
Requirement for investment in training users of CMS cuts into ROI. Would recommend a two-step workflow where department content contributors enter information into CMS and then approval step is done by webmaster team to ensure content meets standard formatting guidelines. This workflow functionality exists in the Titan CMS.
Positive ROI experienced during projects such as moving to a responsive design because much of the content can migrate untouched. Also positive when updating graphics in template to give site new look.
