DatoCMS Reviews & Product Details

We choose DatoCMS because we needed an easy way to implement localization in our pages, migrate all of our pages to a WYSIWYG format with no complications and manage roles for the people in the company. And this CMS has everything that we needed, a lot of plugins, libraries to integrate it with React, excellent localization management, very good performance and an amazing way to manage webhooks. DatoCMS has everything that we need!

This may be a bit technical review, but something very very complicated is updating content in specific fields types. For example, I have a big modular block and I wanted to create the content of it from a script written in Nodejs, as I didn't how to do it, I had to make a change manually in the model, check the browser's console -> network, expand the request and look for that field to see the format that DatoCMS uses to save it, then copy that structure into my Nodejs script and adapt it to save the information that I needed. Another thing that I struggled with, is translating a structured text but keeping the format of the original content. This was veeery dificult to me, but I managed to make it. I think that is something very normal that you have an english blog post and you want to translate it to french/italian or any other language, but you want to keep the original format of the WYSIWYG editor. Those are things that I have to take a looot of time to figure out how to do it, but I was able to. I'm not saying that the CMS is worse than other ones because of my feedback, not at all, I think Dato is the better one with no doubts. But IMHO those things could be improved.

Now we are able have multiple languages on our site, have a better performance compared to our actual CMS (we are migrating from another one to Dato), we were able to implement ISR with DatoCMS webhooks (which is aaawesome!). Our content editors are happy because they have an amazing WYSIWYG editor and an amazing way to edit images! Also, I love the Nodejs client, the libraries to manage structured text with react and the graphql API, now is easier for us to get information from a CMS.

The UX of both the content modeling and the content editing is much better than its competitors. On the rare occasions that I required support, their support team was super responsive and helpful.

There's nothing to dislike about the platform, but it would be great if they added the ability to purchase additional bandwidth for projects on the free tier.

DatoCMS provides a platform to rapidly spin up a headless CMS for websites & apps. It's so quick and easy to do so, that it makes the whole process of getting a project live so much quicker than it otherwise would have been.

DatoCMS allows you to create a fully customised CMS backend for JAMstack websites. You can model data structures accurately while allowing editors the ability to easily manage content. Data can then be pulled down into your app via a variety of APIs which work well. The system is responsive and the developers are friendly and genuinely engaged with how their product is used. Sensible pricing is offered, meaning that even smaller companies can benefit from this great product.

The CMS user interface – already the best on the market – could still be better if there was a final layer of usability polish applied. Some terminology is still designed for highly technical end-users. The interface is very solid but there are also occasionally bugs. Some parts of some of the APIs are not as well documented as I'd like.

I provide easy-to-use CMSs for client websites that allow them to edit their site in a safe and controlled way. I can provide clients with only and exactly the controls they need, so that editing is simple, and they can't accidentally break anything.

1. Great and responsive customer support 2. Great user interface of the app 3. Small and agile team with fast feature releases

Nothing really serious. If I have to pick something: 1. Simpler live previews 2. Missing some of the features of big competitors, but nothing breaking

Centralized content management for websites and apps. Offers great UI for both content modeling and editing. Pricing is fair. Offers great multilanguage capabilities.

Meshes really nicely with Gatsby, with very modern, simple yet flexible model editing. Editing data models is easy for devs, editing records is easy for editors.

We had a few bugs historically, but they have all been fixed so there is nothing to dislike now.

Migrating from Wordpress to a more modern CMS. We have very diverse content, but also some pages (such as a blog) that require many records. DatoCMS fits the bill really nicely by providing a good approach and way of working with both of these.

Minimum setup required to trigger deploys of the site e.g. to Vercel. Flexible type system (schema) and extendable block-based editor.

The price is too high for smaller projects with ~1000 records. The lowest-paid plan is 199€/month. The free plan is suitable for development only.

Deploying a multilingual website with rich media to a global audience. The main benefits were low maintenance costs for IT and an easy and joyful editing experience for editors.

The ever-evolving feature set, ease of use and extremely responsive product team.

Hard to think of anything honestly. The only thing I would have said would be the lack of client isolated infrastructure, but that has recently been added.

Single source of truth for CMS content across multiple applications. Composable content modules that allow designers to easily craft unique experiences in a matter of minutes.

As part of a website upgrade project (moving from Drupal), we evaluated more than a dozen CMSes, both traditional ones like Wordpress or Drupal 9 and headless ones like DatoCMS, GraphCMS, or the industry giant Contentful. We evaluated more than a dozen criteria and built several prototypes. DatoCMS was the one our content editors liked the best due to its excellent editor experience. Out of the box, it offered a good balance between features and ease-of-use, giving a streamlined editor interface and field types that were useful without being overwhelming. Some of its competitors were either too simple (good for only plain posts/pages, not more complex models) or too dev-centric (heavy on relationships and data semantics, but difficult for non-devs to understand and use). DatoCMS hit that perfect balance. In terms of data architecture, it allows a good amount of flexibility and relationships, allowing both links to other records and embedded "blocks" that can be reused and repeated. Records can be organized either in a flat list or in a nested tree-like structure. This makes it possible to model anything from simple blog posts to composable landing pages with fields inside sections. On the API side, content is served via a very easy to use read-only GraphQL API fronted by a CDN. The editor/admin GUI includes a GraphQL Explorer that makes query building dead-simple. If needed, records can also be edited via a separate REST API (not GraphQL). Images can be similarly queried via the GraphQL interface and then are served via the Imgix CDN (included), which also allows powerful on-the-fly image transformations using URL parameters. The plugin ecosystem allows you to make custom field types (such as multi-checkbox fields or better Markdown editors), and a new plugin architecture was just announced in Dec 2021 (haven't tried it yet), which should make it even more powerful. DatoCMS is one of the more reasonably-priced CMS options (and worth every penny), especially compared to established players like Contentful. Support is fast and responsive, and I also appreciate the developers' transparency when it comes to feature requests and which ones will be prioritized or not. Makes our own internal roadmapping easier. Updates are frequent (several times a year) and helpful, without breaking backward compatibility. Features are rolled out in a nonintrusive way and the API is versioned so as to not break existing requests. We're about a year into building our project, and between DatoCMS and Next.js, the new stack is much easier to work with and MUCH faster than the old Drupal setup. Would strongly recommend this setup for consideration.

There are some minor things that maybe could be improved: * Better field primitives (maybe a multiselect checkbox/dropdown, a built-in JSON tree editor, a better Markdown editor like Toast...) * A proper JS SDK for the GraphQL API with built-in React hooks, pagination support, etc. would be nice. Right now you have to manually form GraphQL queries and make the request yourself and handle refetches and paginations. * An official product roadmap and feature request estimate system would be better than the ad-hoc forum based approach we have right now. All in all these are minor complaints, and we're very happy with DatoCMS.

Separation of concerns between content, presentation/styling, and display/infrastructure.

Structured text is a perfect match for us, allowing us to create custom components on the front-end that can easily be created/rearranged/etc. by CMS users, all within a beautiful UI!

Custom assets URL is pretty involved (although documentation is excellent), benefits of Imgix & auto-tagging certainly worth it, though.

Marketing site content and asset management. This has been a huge success, with the easy-to-understand and use UI extending the number of people in the company able to update the site autonomously.

Every single feature in DatoCMS is well thought, engineered, and fine-tuned to deliver the best experience both for end-users and as well for the developers. The community is thrilling and you can always find some hint to fix a problem or some proper help from the support team. Actually, I've never experienced a faster and ultra dedicated support team than DatoCMS's. Whether if you're a single developer willing to delve into the future of web technologies with the best-in-class headless CMS and one of the pioneers of the Jamstack philosophy, an Agency with a lot of clients to serve, or an enterprise with mission-critical requirements, DatoCMS is the cherry you're looking for.

Actually, there's nothing I dislike about DatoCMS. The rare times that I've encountered a glitch, a bug, or I got stuck for any reason I could count on the strong community support and on the kindness of DatoCMS's team that always guided me through towards the solution, sometimes even developing new features ad-hoc!

I've migrated a legacy monolithic application to a modern, future-proof Jamstack architecture that increased performances for end-users by more than 5 times and, at the same, time lowered drastically the running costs.