Unclaimed: Are you working at Sanity?
Sanity Reviews: 4.7/5 — Highly Rated
Sanity is a Composable Content Cloud that lets teams create amazing digital experiences at scale. It provides real-time collaboration, live multi-user editing, and track changes. Content creators, designers, and developers can come together while separating content from presentation
| Capabilities |
API
CLI
OSS
|
|---|---|
| Segment |
Small Business
Mid Market
Enterprise
|
| Deployment | Cloud / SaaS / Web-Based |
| Support | 24/7 (Live rep), Chat, Email/Help Desk, FAQs/Forum, Knowledge Base, Phone Support |
| Training | Documentation |
| Languages | English |
Compare Sanity with other popular tools in the same category.
The super agnostic API-driven datastores, combined with functional image CDN and rich query language in GROQ is all what one would need in terms of data retrieval. The automatic form builder which actually works for data models is the cherry on top!
Studio customization is endless, but the learning curve is quite steep. Data retention could be opt-in or possible to opt-out and reduce costs if not needed. On-demand listeners or buying extra listener quotas for more real-time projects would be great without needing to go enterprise/custom plan way that provides overkill of a feature set otherwise.
No matter the content needs, we can solve them with Sanity. We have made rich content decorations for eCommerce projects, as well as built custom eCommerce solutions altogether. Heck, we even built a 3D product generator that is driven by Sanity data in a highly customizable fashion with no extra development effort needed.
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
Good developer experience building studio
Still missing first-class typescript support
Content management for various apps, blogs, articles
The ease of use and customizations that Sanity provides is rivaled by no other CMS. I can structure my content however I want but more importantly, I can structure the editing experience for non-developers as well.
I wish the documentation provided more examples of advanced changes that we can make to the editing experience with our custom input components. Although it does provide some information, I think more examples and references would be awesome.
We transitioned our wordpress marketing site to Sanity with a Next.js frontend. The experience has been really smooth and the editors appreciate the live preview mode that next-sanity provides.
Easily customizable studio with React which plugs into our own API's.
Having to learn a new query language, Grok, which is sometimes mind bendingly complex.
Marketing team creating and publishing content. They can pull in data from our API's and populate preconfigured frontend templates.
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.
I've found Sanity to be incredibly user-friendly and easy to learn despite being a beginner to all things website building/management. After being informally trained on the platform by one of my colleagues, I was able to jump right in and begin editing existing pages/building new pages with ease. The different module types make it incredibly easy to create and modify content and give me the freedom to play around with how each page looks.
My only complaint regarding Sanity is that there is sometimes a lack of flexibility when it comes to using the different modules (e.g. a certain module might require an image or a header title despite me not wanting to include one) This rigidity requires me to get creative and propose alternative solutions, which I am able to do, but I would like the platform even more if it allowed for more user freedom and didn't require all of its module fields to be filled out.
Through Sanity, I'm able to improve the user experience on my brand's website in a relatively agile way. For example, if we receive customer feedback that a certain service or product is difficult to find on the site, I'm able to update our main navigation menu right away to make that product/service more easily discoverable.
You can write custom React code but still make it so that the content is easily editable by non-technical people, while the structure of the content is highly customizable: There are units and dialogs and interconnectivity between different types of content, with excellent interplay between what the engineers can write in code and the underlying UX that lets content and design edit the actual content.
Missing true collaboration functionality - we use Cord.com to be able to leave comments and work in-line. Other than that having a preview for each section you edit rather than seeing the entire page in preview mode or in edit mode would've been nice (though I understand how technically challenging it is)
We have our cord.com landing page on Sanity, which includes blogs, team about pages, FAQs - basically all of our TOFU and MOFU nurturing content, SEO-friendly pages that are meant to help people find out about Cord. This solves the problem of having a stand-out, unique website built by designers, with flexible content units that are custom to us, but easily editable by non-technical content writers.
I often proudly describe Sanity as the “Command Center” when explaining a custom website build to clients. With Sanity, practically anything is possible when it comes to structuring and connecting your content (data). Learning to understand and love structured content will forever change the way you think about development and how you populate your website/app/etc. Having well-structured content has not only simplified complex website builds, but it multiplied the possibilities of what's possible, leading to larger contracts for my small business. Here are the features that make Sanity my GO-To solution: - THE STAFF is just delightful: Attentive, supportive, inclusive and genuinely kind is just the beginning of how I would describe every staff member I've gotten to know over the past few years in the Slack channel. - The community: Sanity has a strong community of passionate followers. Most tech communities I'm a part are filled with more questions than answers, not to mention rude answers to not simple questions. BUT the Sanity Slack channel always has great folks that answer any questions I have. - The Studio: Easily hand over the content reigns to your clients without worry. The studio is written in simple to edit JavaScript files allowing you to pull in your favorite NPM packages, write custom logic, and commit your files to your favorite git repository. - GROQ: GROQ is the data querying language Sanity uses. It has turned around my dread of database querying languages. With GROQ you can easily get the data you need. Filters, joins, sorting, etc. are all developer friendly. Also, if you prefer graphQL, Sanity's got your back. - The " Image URL" NPM Package: Remove the need to use a 3rd party image solution. "Image URL" takes care of image transformations like cropping, resizing, transforming, and compressing images before they are delivered to your website. - Connect & sync with Shopify Products: e-commerce will never be the same!
The only thing that I dislike is that the Studio is built with React, and that you'll most likely need to know React decently well to make custom components. I actually agree, choosing React was wise for Sanity, considering React is by far the most popular JavaScript framework, I however, just don't like it. I shy away from creating my own custom elements because this. The silver lining here is that I've only needed a custom component once, and a member from the amazing Slack Community had already created the exact component I needed and sent me a link to the GitHub repository!
I use Sanity for my websites that need a custom solution for content. You can power a simple blog using most any CMS... But only with Sanity can you power a blog with an e-commerce shop and place connected products into the blog posts!
Flexibility. I was able to easily fulfill my clients needs in terms of data structure and workflows to add, edit, and delete data. I delivered a completely bespoke web app and I was able to use my preferred development tools and packages (not locked into using only sanity's tools and clients)
The mobile version of sanity studio gave my clients some trouble when logging in (missing a cookie). Looks like sanity is aware of the issues and working on a solution.
- Quick Development and Iteration Speed - Flexible Data Structures - built in change management for custom data structures - mainly used to spin up web apps for small to medium sized apps from thought to production ready code in hours not days
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.
architecture along with understanding ou r tech solution, also a host of features that can support marketing
the add ons are not visible, butyou find them with more use and understanding
no problems, but with more access being provided by my product team as a marketer more and more benefits are becoming visible to me
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.
Very open and flexible CMS. So much so that we are now even using it as an admin interface to our API's
Not really a dislike form my side but my developers sometimes feel it could have better documentation
Initially started as simple content management of sections of a VUE web app, then progressed to full content management across the application, and now we are even extending using Sanity to manage API configurations and settings
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/
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.
Sanity's biggest strenght is that they let you configure almost anything about their interface. The studio is fully customizable, and content is delivered in a platform agnostic format that can be used with any technology. They have excellent documentation and a helpful community that is willing to help when stuck.
Image management feels incomplete without a file system and the option to bulk upload images. You can integrate with other services like Cloudinary, but an out-of-the-box solution would be very helpful.
We use Sanity to create content following complex custom data structures, without making any assumptions about how we want to use that content in our front end.
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.
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.
We used Sanity to rapidly build an API for a new mobile app, with minimal need to involve our development team (i.e. it's a "low-code" solution). And even though we thought it was just for prototyping, we're now using Sanity to power the live application.
Not much, at this point. The docs are quite extensive, although (maybe because it's a relatively new product), there doesn't seem to be a lot of sample code to borrow from. The Sanity team is very responsive in the community Slack, though, so this isn't always a problem.
The biggest benefit was being able to go from zero to a production-ready API in less than a week. Testing changes locally and then deploying them to production is also incredibly easy, as is the built-in tools for optimizing image assets ... all with very little custom code required.
Sanity's super power lies in its use of GROQ. GROQ allows for data stored in the Sanity content lake to be queried and structured in a format that best serves the need of the frontend website or app without the need for multiple API calls. GROQ presents content in a structured way such that content does not need to be authored using markdown. This allows for rich media content to be placed right along side traditional text content during the authoring process. And all of this content is simple served in a well formatted JSON response when querying using GROQ.
When you first start with Sanity, it may seem like you have to configure everything in the Studio (content authoring and management app) based on the schema of your content before using it. To some, this may be cumbersome, but in reality, this "requirement" translates to a whole world of unparalleled flexibility in terms of how the content authoring and management experience can be tailored.
We operate multiple sites and apps across the organisation. This presents a significant challenge in managing content and providing a consistent authoring experience for all content moderators. Sanity allows all our content to be managed in one location as a single source of truth. We're also then able to present this content on the frontend in a way that best suites the digital experience we want to deliver.
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.
Everything is manageable through code. You can version control your schema, and the studio is just awesome and easy to customize to fit your needs. Most other solutions don't let you customize the *CMS* part, but it's not only possible but relatively easy to get it done.
Not used it for very long or big clients so don't know. But 2 things come to my mind: 1. DB-level schema validation. I've read it's coming soon and I'd love to see custom-validation work server-side as well. 2. Studio is very sluggish. It updates the draft on every keystroke. Would be cool to disable this or have it not lag on every keystroke, especially in development mode.
Primarily e-commerce and custom merchant needs. (headless commerce)
Ability to build the CMS interface in a custom way that works for our team. Sanity provides the tooling for interacting with the realtime database, building interfaces for saving, validating and publishing data.
If you don't have the technical resources on your team to build the Sanity studio, a more traditional headless CMS might be better for you. The tools for building the studio are still a little primitive, but every month I'm seeing improvements that give me confidence that the studio will be more fully featured over time.
Creating a place for non-technical members of the team to draft, edit and publish content to our marketing website.
Developer flexibility. You can do pretty much anything with the UI.
Not easy to style the out-of-the-box UI components.
Speed. Our focus is fast loading sites. Sanity as a back-end is super flexible and allows us to use whichever front-end optimisation techniques we want.
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.
With their templates to launch sites via Netlify, they make it really easy to get up and running with sites that get you started. Really low barrier to entry. I also like that they are not committed to just one technology - they even have a Sapper blog starter!
Please support Brave! Also, would love to see more choices than just Netlify. I'm a little concerned with the limits on the account levels because I'm not sure what my business will need, but that is all part of the adventure!
Instead of searching for solutions to launch a landing page, a blog, and future sites, this has it all in one easy place.
Developers often appreciate the ease of use and flexibility that Sanity provides.
There are some limitations and I hope that comunity will grow.
Simple and powerful content management system.