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
Webflow
Score 8.1 out of 10
N/A
Webflow headquartered in San Francisco offers what they describe as a visual solution to web design, with a CMS for editors, designers, and developers that they state allows users to create needed content structures, add content (by hand, from a CSV, or via our API), and then design it visually. Webflow service plans also include website hosting, with a basic plan for sites that don't need a CMS as well as CMS, Business, and Enterprise plans. Webflow's ecommerce plans are designed to support new…
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.
Webflow is great for designing pages and creating a really nice looking website, without needing to be a pro designer. However, trying to scale a company blog for SEO leaves a lot of room for desire. There are various SEO-related shortcomings (like how canonical tags are added to pages) and I also need to add a lot of custom code elements to blog posts to get the desired control. This means adding new posts and getting them looking the way we want takes way more time than it should do. Also doesn't support next-gen images, which is impacting our page speed scores and leaving us behind when it comes to Core Web Vitals update. Finally, the fact that only one person can enter the designer at one time is really annoying. I get that the Editor should be the solution to this, but it's so so so slow and jumpy that this is essentially unusable.
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.
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.
It is extremely easy to use, especially with available templates and guides. It is used primarily by accounts and creative rather than dev. It is also easy to import/export projects or duplicate them for re-use and modification for another client. While it is rarely the end platform for a deliverable, it is often instrumental in pitching.
In my experience, their customer service is an absolute joke, I tried reaching out to them they took forever. I had to keep following up with them as if they never received it in the first place. It’s a new platform, so guidance is needed. Tried the university they offer, in my opinion, it is completely useless, I would just completely move on from this website.
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.
In my opinion, it is horrible, the rendering takes forever. I have the newest MacBook and the platform will still lag and slow down on me. I’m not a developer, I am a designer which makes it worst because I am using the features they are providing not extra coding features. In my opinion, it is a horrible platform really, stay away.
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
We pay hundreds of dollars a month to Webflow, yet their support is worse than a typical free SaaS product. We were prevented from deploying changes to our site because of how Webflow structures its support. It delayed a product launch for the whole company. Support options? Beg for help on community forums, it took a threat to email the CEO to finally get movement. If there were easy alternatives, we would switch. But for now we just pray nothing breaks and that we don't need to interact with Webflow support.
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.
The code quality and speed can't even be compared to Elementor; Webflow is simply a much better tool. Instapage has a cool feature for dynamic landing pages, which changes according to Google Ads Keyword, which I miss; however, amazing webflow community members recreated that functionality with a custom script. For the majority of users, it's a safer bet than WordPress in terms of speed and code quality. WordPress could provide amazing results if hosted properly (nginx, caching configuration) and requires best practices to maintain code quality. Webflow solves these issues out of the box at a fraction of cost.
I feel it doesn’t perform the way it’s supposed to and it doesn’t have any beneficial factors to it. In my opinion, there is no reason to use a platform like this when Wix and Shopify, and WordPress exist. I believe Webflow is a platform that shouldn’t exist and it’s only popular because of the hype it received. I tried it and hate it completely.
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.
