Sanity Reviews & Product Details

The Sanity team has been responsive and friendly with every interaction. From a programming standpoint, the product has been easy to use and well documented.

We are on the Proof Of Concept phase of our project, so I cannot speak about Sanity and its performance in production.

We are on WordPress today, and Sanity is a big step forward as we move to an enterprise solution. We manage two dozen websites today, and sanity allows us to consolidate shared data that we currently duplicate. Sanity is also removing some inherent issues with WordPress that will improve site speed and speed to market.

The GROQ Query language and schema design are all pretty easy to pick up, and the Docs are well-written and helpful. It integrated well with Next JS and was an easy choice for a CMS.

I would love a way to query images and cache them at build time, rather than having to request them at runtime. For Static sites, it seems an unnecessary use of bandwidth.

The backend is simple and easy to onboard non-developers on, which is very useful for the types of sites we're making.

Sanity strikes the perfect balance between having useful out-of-the-box features and allowing cusomisability when required. The CMS interface has a clear UI (preferable to some other CMS platforms I've used) and the plugin eco-system is a real plus.

Adding and editing fields in Sanity is done in code by updating the schema. While most of the time, I've got a code editor handy, I sometimes wished I could easily add new fields directly from the UI.

Sanity was a bit of a revelation when I first started using it. I'd never considered building my own CMS, and Sanity made it achievable. As a fan of the JAMStack Sanity fits in perfectly; I can build in React and Sanity and quickly deploy on Netlify - all without having to touch any backend code.

It was easy to drop into my React project without any hassle. Easy to query and return data in the format I expected. Much easier to use than learning a new technology like Gatsby, etc.

I am trying to use their API to upload information to the CMS. It's well-documented, but I am having trouble setting it up correctly for my application. I likely need more time to understand it.

Our website needed a simple headless CMS to drop into an existing project. We were moving from developers entering information to marketing people, and it made the process very easy for them!

The Studio! Version controlling schema is never accessible, but Sanity has made it a seamless experience. It's a fast, easy to use application.

Sanity could tie GraphQL deployments into the Studio flow better. Also, there should be a better multi-developer experience since datasets are maxed at 6, so a dataset per developer isn't always viable. Multiple developers working on a single dataset often cause conflicts.

Being able to release code and schema at the same time. Using Contentful in the past revealed how much of a pain it can be to manually move content models around.

It is super easy to learn, compared to some CMS it is so flexible.

Nothing really, cannot fault it. Would highly recommend.

I needed something super lightweight for brochure websites, this fits the bill perfectly

I enjoy the built-in features that Sanity offers. I also like that the third-party ecosystem is fairly robust and many plugins can be found for customization

Custom use cases can be difficult to implement. Sometimes the documentation is lacking when it comes to this. Major version upgrades have been a major pain point for my team as we have many custom implementations that are completely unusable on newer Sanity versions.

Allowing our marketing team to easily manage site content through a good UI

I really liked how easy it was to get a backend deployed and the built-in query language was nice. I don't have that much experience with hosted backend services but what I have seen so far I like.

I can't say that I've used it long enough to tell. Excited to keep working with Sanity though so time will tell how it will grow on me or what I dislike, ha!

Quick backend solution without all the heavy lifting.

What I like the best with sanity is the possibility to customize each of my projects exactly how I want them to be. Both for myself as a developer and for the customer.

Because of the many possibilities, it also takes some time to learn how to use sanity. It is not for people who are new to building websites. It requires some experience. Also, compared to other brands, Sanity has less documentation from users that have solved problems that one might have.

Some of the benefits I've realized with sanity are the possibility to customize the admin page to the customer and to use groq as query language. It makes it easier for the developer to make requests from the api.

As a content editor, it's saved me loads of time and headaches. It's smoother for delivery and guarantees a smoother relationship with our dev team.

Sometimes Sanity Studio's previewer lags behind.

Friction-free authoring experience. We're now embracing headless platforms - everything's more performant.

It's a simple platform that makes using it very easy and efficient. It always is reliable and never down.

I often find that there are lags and delays with seeing changes updated in Sanity.

Site updates. It's seamless and easy to use.

Flexibility. Studio customization with plugins, parts system & react components. GROQ is awesome. HTTP API is super cool. Plugins marketplace contains a lot of tools. In general I'm super happy with a way how can we create own features on top of Sanity. We had to implement a migration tool for operators for copying content from another dataset - I really like the way how plugins system works.

Referencing documents poor implementation (I see there is a new article "connected-content" I'll inspect it) Keep studio up-to-date when having custom parts - is a pain because of compatibility issues Parts-based customization appears not so cool when you want to change nonstandard parts because they contain a lot of imports - the case when "you need a banana, but you getting a gorilla and entire jungles". E.g. you can't simply provide your custom list item element, another example - when I wanted to create a custom object input that would contain standard components inside (I had to implement a behavior that now can be achieved with conditional fields) I finished with a lot of deep imports right from a package. some CLI tools aren't working. E.g. I can't simply clone a dataset with CLI (I'm on Linux - maybe it's the reason). Importing content from big datasets also not working - I can't import data from production at ones, have to divide it into small pieces by content types. But some content types have a big amount of documents so I can't import them as well.

We creating a pretty big CMS with content spread through a range of datasets, environments, and labels (label stands for US state). It contains a custom publishing flow when documents go through a series of environments before appearing on production. CMS users have custom roles. Labels implemented in a way when any document can be forked from a white label into its own label and being edited then. We're using custom read tokens with special filter settings in order to simplify frontend teams' life so they're consuming only needed filtered content for a specific env and label.

The best is clarity of how you set up a banner, promotion, and promotion texts.

For my part not easy to see a overview for repeated schedules

Manual work is now scheduled instead.

Setting on up sanity was extremely simple, and intuitive. Being a new developer, Sanity was definitely one of the easier backend's to get working. Their free plan for deploying a live db is also amazing!

It was a bit difficult to find updated versions of their docs. I would have to use stackoverflow or youtube to find answers, rather than their own documentation. The docs are a bit outdated, but id love to see them more detailed and updated!

A very simple way to add content to the backend, which allows for my clients to modify them easily on their own.

Two things that I like the most about Sanity thus for is the branding as well as the organization of the tech documentation.

My main dislike with Sanity is the fact that even though the docs seem to promise a great dev experience, I haven't made the time to fully build anything yet!!

The main problem I am looking to solve right now with Sanity is the opportunity to provide a better eCommerce/Onboarding experience with mico-businesses.