Sanity Reviews & Product Details

Love how easy it is to customize it to our needs.

A bit unclear how to best integrate with Gatsby (2021).

Sanity was the only alternative that was able to deliver the freedom we wanted from a headless CMS.

Data model built with code makes it easy to build the system you want, not the one you're allowed. Customization of the Studio with React components allows you to further customize the experience for Content teams

Not the biggest fan of GROQ, though thankfully GraphQL is supported so you can opt out of it. Really wished we could have Array of Arrays in the data model (though it's easy to workaround). Last, wished all paid plans included SLA

Dynamically built e-commerce (dynamic layout). It's the only CMS with which I don't see us hitting any limitations as the system grows in complexity and new functionalities

Customized data type, images optimization.

Sanity Studio is a bit hard to build. Sanity is a bit awkward to use for blogging or portfolio website database.

Flexibility and customization.

There are no frills, which allows for both simplification and also powerful customization.

Sometimes logging in doesn't work the first time.

Making site and content management more efficient and scalable.

As an engineer, Sanity provided a very robust solution that met all my needs for flexibility, ease of use, customizing validations, etc. It also allowed our content creators to own their own content, not needing engineering intervention for almost anything. There is a wide array of plugins that helped us with things like translations into multiple languages. I also found it very easy to ramp up on - being able to create schemas in javascript was easy, and their documentation was extensive. Their active slack community has also been helpful in getting any of my questions answered.

The biggest issue I've had recently is being unable to search for referenced documents easily inside Sanity Studio Desk. Ex. if I my content creators want to find all places where a given document is referenced, they tend to have to ask engineers, as this is not possible via the search tool, as far as I know. Also, at least as of when I was implementing it (about a year ago), we could not integrate SSO with Okta, so our permissions have to be handled manually.

Previously, all of our content was either stored in a database or via Wordpress. The content in the database was frustrating to manage because it required engineering time every time the content creators wanted something new, or even just to fix a typo, and Wordpress didn't allow us the flexibility we wanted. Letting content creators own their own content has saved many engineering hours, and the additional flexibility from not using Wordpress has allowed our content to be more rich.

I love the fact that Sanity is an API driven CMS. Being able to have remote structured data, that can be customised by React Components. I find the way it exposes the content via APIs and GraphQl makes this a fast and easy to use CMS.

Finding a reason to dislike Sanity is hard; however it is hard to understand to how Sanity will work at scale for your use cases. This is based on my project examples - it would be good for my White Papers and data on operations at scale and which

I have been able to use Sanity to mimic other powerful CMS solutions in place. It shows and distruibutes quick and easy data modeling/

The UI is easy to use and ways to customize it is very flexible. It's effortless to get it up and running especially if you're looking to create numerous sites for clients or personal use.

Lots of popups if there are multiple functionalities within nested components. It can get cumbersome if the user is trying to dig through the popups to get to where they want to edit. Tutorials for more advanced customization of the UI would be great too.

It gives the ability for the user to update their product quickly and gives the developer the tools to be hands off.

The most helpful thing about Sanity is the ease of customization of the platform, and now also the easy integration with Shopify, where I build most of my projects.

I would like to see the option of adding separate headings into document structures so that complex document types are easily readable. Also, the documentation on structure-builder icons is minimal. I would like to see a visual overview of out-of-the-box options for this.

I have migrated a blog from Squarespace to the Sanity system, which posed problems at first. However, once I had enough knowledge of using the Block-Tools scripts, it was easy sailing. I now use Sanity to develop new and better experiences bundling the powers of Sanity and Shopify's Hydrogen.

The ease of use. We are a small team and I am not a website editor by trade. I was given access to part of the website so I can update the media placements that I garner for the company. The interface is SUPER easy to use and I am able to update my section with ease. Thanks!

I really can't think of anything negative in my experience with Sanity so far.

I am able to get our media placements up QUICKLY on our wesbite so we can show our website visitors the impact we are making, and also so we can link to them in our social media posts.

I've had the chance to use Sanity Studio for my personal projects as well as on the job, and I like the customization options that it provides. Sanity Studio is well suited for many different usecases. Pretty good documentation overall as well!

I think advanced uses of Sanity Studio can be a bit daunting to those that have never written CMS schemas before or people that are new to programming in general.

I'm solving the problem of not having data hard-coded into a website by using Sanity Studio. It's a great way to decouple the content of your website, and the layout. You can also have multiple non-developer team members manage your content instead of a having content hard coded into the files.

Content version control, publishing and management is simple. Works well with Jamstack web applications. Sanity offers a significant improvement over older generation monolithic CMS offerings.

Requires development support for implementation in more significant projects. Documentation supports this well, but it is not as simple as monolithic CMS implementations.

Building an internationalised website with member-gated content has been significantly easier. We have consolidated 9 previous websites into a single CMS, which renders to different regional domains using a Next.JS front end. Google Lighthouse improvements from 49/100 to 99/100.

Content migration from Legacy CMSes are easy Can create your own features/components as needed Deployment is catered to

UI is not aesthetically appealing as it seems to be developed for the development team only

We are revamping our client's existing websites using Sanity CMS by migrating content from their legacy website to Sanity. Deployment is less headache as the build process is auto through Git.

Truyly powerful CMS that can be customised to suit different organisational needs. An intuitive CMS that a wide range of staff with varying technical know how can pick up.

The amount of time and effort required to set up the backend properly.

Allow modules to be designed in a custom way, and website content to be editable by many people in one place.

Flexibility. Ease of development - using standard Javascript and Typescript Good community and support

Documentation could be a little better Can slow down a bit with large datasets

We rebuilt both our legacy websites using Sanity as the CMS. It allowed us the flexibility to add any new feature we could imagine without too much fuss.

I like its flexibility and opportunity for improvements. Its easy to navigate, has great customer support and is frequently used by a lot of people in our team.

The Media Library limitations. How difficult it can be to enable change, and requiring a developer to build custom elements. It doesn't allow for me to build much, without developers.

Sanity is yet to be implemented correctly, but will allow us to have a Headless CMS.

Simple Uiser interface and the compatibility of integeration with other front end techs. Moreover the documentations. Hatsoff for that. The query language that has been used by Sanity is a excellent option for me.

As a developer I use the sanity for backend purpose , I have been using Sanity for past several months. I found implementing slug or redirecting inner pages in pure HTML CSS became a bit hard.

As a front end developer I am facing a lots and lots of issue regarding the backend area and I am not into the backend techs . But Sanity helped me to get rid of that issue.

I like the very huge options of customizations and the incredible user experience and learning curve that is soft.

It's diffucult to say something to improve, it's a very nice tool.

It's a difficult task to enrich media content from Spotify, but with Sanity we can do that with minimal effort and allowing an interface where content manager can handle with.

The most valuable part of Sanity is the flexibility to control your content and shape it to your business requirements. We've used Stapi before, and Sanity is much more powerful and easier for both our developers and non-digital team members.

Although Sanity is powerful, the editing workspace's UX could be prettier. I find that the dark mode is a little bit too dark for my preferences. The API webhooks are nice, but I would like to see a log of when they are triggered.

Sanity is a great CMS system that allows different teams (Development and Digital content team) to work asynchronously so there are fewer blockers in our pipeline.

Easy to set up, customizable and works well with my tech stack!

Block editor could use an upgrade from a UI standpoint

Running a blog

I like that you can access the studio directly inside the localhost.

The client is not yet supported in the fetch of NextJS. You cant get decoupled requests with the client unless you use the http.

Right now, I can dynamically render components with Sanity.