Jahia Digital Experience Platform vs. Netlify CMS

In my experience, Jahia Digital Experience Platform as a CMS platform is excellent when you have a large amount of content that needs to be customized. It is also good for when you have templated content that has minor variations. I would say it is less appropriate when the content has numerous mathematical computations, or a large amount of business logic that comes into play with data processing.

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

• Content management: It is very easy to update text, images, files and videos even for a non technical user.
• Multi-site Management: It has a robust multi-site management capability, It helps in maintaining multiple websites with consistent branding.
• Digital asset management: It is easier to store organize and retrieve images, videos and documents.
• It has a great built-in analytics and reporting feature.

• 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

• It lacks the ability to manage multiple versions of a page or content in general.
• The back office interface sometimes encounters bugs or display problems.
• It's difficult to keep pre-production sites up to date in terms of content compared to production, because the time required to import/export sites is very long once the site is rich in content.

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

I would not use Jahia as it proved too complex for our needs and didn't help our over goal of customer satisfaction. Along with the man hours to build and execute, it wasn't worth the hassle

The interface and ergonomics are designed to facilitate the use of the product. The creation of template is easy which allows to minimize the actions necessary for the provision of content.

[I give it this rating because it] was up most of the time. There are so many scheduled reboots that I don't think it would be a good choice for a 95% SLA.

Incentivized

It's stable after upgrade to Jahia 8. Not much server down so far

Incentivized

As I was saying, the support makes sure to be available for any question, or any technical point that we may need to discuss about. Moreover, whenever we have an issue with the platform they get alerted and also send us an email so that we are aware. We had multiple complex topics to work on in the past, but they always have been answering our question

Incentivized

Jahia provides a similar user experience to other CMS I have used in the past - it features a simple interface that makes navigating and learning how to use the platform easy and the ability to copy and paste content saves time and effort when building new pages. The ease in which you can manage the site in different languages is also a big plus!

Incentivized

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

You can create your own feature module and it can be resuable across the projects. The Java libraries is available for development of Tomcat or JSP

Incentivized

• Our once frustrated contributors are now happy to create content with Jahia Digital Experience Platform!
• Pages are snappy and bug-free, which wasn't always the case.
• Jahia Digital Experience Platform has mapped our complex organization into nice roles and permissions.
• All our external services were nicely integrated into a modern portal.

Incentivized

• 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