Founded in 1997 with a vision to create the first truly open content management system, Magnolia is presented as a fast way to launch digital experiences. With a mission to help clients move fast and stay flexible and boasting users among brands like Atlassian and The New York Times, Magnolia DXP supports industries ranging from automotive to telecommunications, offering enterprise features and headless agility to help them stay ahead. From humble beginnings in Basel, Magnolia's…
N/A
Tridion
Score 9.1 out of 10
N/A
Tridion (formerly SDL Tridion) aims to connect people, processes, and information through a complete portfolio of collaborative Content Management, Knowledge Management and Headless delivery technologies. Combine with Accelerators for fast time-to-value and RWS Translation Management solutions for global reach. Its key components include: Tridion Sites provides web content management capabilities, connecting people, processes, and information across teams, brands, and markets,…
Magnolia is very well suited to scenarios where there are multiple end points for content eg. apps, remote devices, websites etc. and with multiple users. Magnolia is very good at working with different "shapes" of content so it's not necessarily all about HTML content for the web which tends to be the default for a number of other products of this nature. This means that it's more logical for people to work with structured data and easier for the applications to sort and manage that content when they receive it.
This works really well when you have multiple team members (often in multiple locations). We've had clients who've had people in twelve European locations with sixteen languages and they can share skills and resources between them but still manage their own content.
Magnolia is less appropriate for SMEs who have fewer digital assets and content. It's not to say that it can't be done but it's more that the budget would not necessarily fit.
Love the product and I really like how we use it for public sites. The only negative aspect is that it is just hard to find Tridion devs that understand the tool, grasp .net, react, and understand the blueprint, etc.
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.
Tridion is complicated in enough ways that it makes it difficult to train new users. Therefore, we have to limit the number of people with access to the system since we have not yet implemented Workflow.
When something goes wrong (items fail to publish, or there is unexpected behavior with components), there is little explanation provided that would point us in the right direction to troubleshoot. As a result, content Authors and Editors have to frequently ask for IT assistance.
I am giving this a semi-high rating because we have already got Tridion up and running and we are still in the process of moving the sites over to Tridion. It is unlikely we will be moving things to a new CMS AGAIN in the near future as the cost to get Tridion was high.
There are a ton of small things that could make this CMS great Off the top of my head... 1) Better navigation between a component and its corresponding node in the jcr ( devs often have to flip between a page and a spot in the jcr even though there could be a button to take you from a page/component in the pages app to its location in the JCR) 2) Why does a content editor need to open the page to edit the page properties? They could just as easily edit the dialog from the tree view if they have many pages to touch, and it would save them time by not having to render the page.
The editor user interface is very user friendly and in-site editing makes simple updates fast and easy. The extensibility of Tridion is a big plus and the ability to add our own options into the default Tridion interface helps us integrate with external systems. Finally, the user permissions and security system helps us deploy it within our large organization.
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.
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
Prior to using Magnolia as an enterprise CMS solution, different teams leveraged different website platforms including WordPress, Weebly, 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.
It is a nuclear missile compared to the other handguns and knives on the market today. But it also requires nuclear technicians and expertise that a handgun doesn't require. Do you need to decimate your competition and you have the investment capabilities necessary to put a nuclear missile into the sky? Then definitely do it. Especially if you need a very good multi-lingual blueprint provider like Tridion.
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.
