Magnolia vs. Netlify CMS

If you need a business CMS that brings along a good amount of features and also give you the chance to develop features on your own, Magnolia would be a good choice. Even if you have not the fitting infrastructure around, Magnolia provides you different ways like SAAS oder PAAS. If you have to review your code our have any problems the team behind will helps in a short time. Without using the connectors it is not so easy to connect special functionalities like Marketing tools or optimization tools. The DAM is very slow if you have an huge amount of documents and pictures to store for your website - you have to add an external DAM.

Incentivized

Netlify CMS is well suited when you have very less frequent updates to your content, maybe once a day and very few people need to access your data. You can connect it to Netlify, GitHub, or any platform and have multiple people access it and do as many updates as you wish, but the process is not well-defined and you need to build your own system for that. It is well suited for projects you need to pull off with very low cost, it is essentially free as the software is open source and free to use, and all you need to do is set up your schema correctly and find a deployment pipeline where you can build your static site/API to redeploy whenever the content changes. I personally used a GitHub Login -> Netlify CMS -> next app consumer of content -> GitHub pipelines to run next SSG -> GitHub Pages to deploy the built static site. It might not be appropriate for large teams where users themselves need no-code tools to modify the schema of the content.

Incentivized

• 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.

Incentivized

• Storing content data in customized schema without a database
• Full control over your content and infrastructure where it is deployed and stored
• Very low-cost way for building your own CMS and CDN

Incentivized

• 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.

Incentivized

• Linking between different schema types, i.e. having some relations between content
• Better ways to define content schema, like how TinaCMS would handle using a JSON

Incentivized

Magnolia is an innovative CMS, for example it is possible to use the ipad to manage the contents. Magnolia’s team works hard to improve the product; the community is small but active and the support for the enterprise version is good. Magnolia’s team asks the users what they think and what they need, and the new functionalities planned for Magnolia 5.3 are very exciting for example the content personalization.

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.

Incentivized

It's a lean and performant platform. You don't need to put reverse proxy servers in front of it to speed it up (although that does make it go even quicker) as there are various layers of caching built in to the application. While it's a little cryptic, the internal caching system is actually quite configurable and can be tuned to the right sort of content.

Often what tends to surprise many an IT manager is that you can run it on relatively modest hardware. We've often been met with "are you sure ?" but the reality is that it doesn't need a whole lot of horsepower.

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

Magnolia DXP offers similar or more capability compared to the other platform, while much easier to implement. For example, Adobe Experience Manager tend to be more monolithic in nature, heavier footprint compared to Magnolia. Hence when implementing a DXP, it is much faster to build using Magnolia, at a much lower TCO. The other platform like Kontent.ai and Strapi are pure headless platform and offer lesser features. What really make Magnolia different is the APAC team, who are all out to support their client in the implementation, ensuring their client maximize their platform and the project implementation is successful. This is some thing that is not experienced when using other platform(s)

We really can't compare it to full-fledged CMS software, like WordPress, which has a lot of community and support with widgets, plugins, and whatnot. It's not built for that, but you can compare it to Contentful, Ghost, Strapi, etc., which provide similar functionality to a headless CMS with custom schema options, but even among them, it still lacks a lot of functionality, ease of use, and support. But Netlify CMS pros would be of the opinion that compared to other platforms where most schemas need to use their own tools and frameworks, it's very cost-effective. Something new called TinaCMS has come up to compete with Netlify CMS by covering most of its shortcomings, but it's something new being built by the same team that built Forestry CMS and comes with many modern features, yet currently only supports NextJS SSG.

Incentivized

• We have placed web content management in the hands of the organisation than retained it within the technology team.
• We were able to quickly move to MVP and release and we are now focussed on moving the platform forward at some pace whilst not being burdened with BAU work inside the technology team as so much as self-service to trained organisational users
• The use of the SAAS/PASS has inbuilt business resiliency as specialist work and aspects such as underlying security is done by Magnolia and we are able to focus internal effort on building out the platform.

• Helped us inject dynamic content into existing site very quickly
• Wasted a lot of time to implement when something complex, such as querying content, was needed

Incentivized