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.
Schema creation in code is awesome = nice to have it in source control.
Groq language is something new you need to learn, but not a showstopper.
Having control over the editor UI (Sanity Studio)
As a content manager Sanity is excellent because I only have exactly the functionality I want, no more, no less.
I feel small shock each time it disconnects and I get the "it crashed" message... I would like bigger windows to view more details of the content in drop-down menus.
When we don't have capacity to do everything in-house, multiple external partners do work for us directly in Sanity.
Sanity is easy to set up and easy to use. And when I say easy to set up, I don't just mean it's plug-and-play. The amount of customisation that Sanity offers versus the ease of use and setup seems almost suspicious at first, like you're waiting for the other shoe to drop and discover some horrible opinionated pattern. But that never happens. Sanity's UI, data structuring and querying are leaps and bounds ahead of other CMS options out there.
Sanity uses a lot of opinionated data shapes that require their own dependency to parse. We've had issues before where bugs in these parsers have broken things like edited images and markdown. Still, to their credit, Sanity's support team is very responsive and able to help out whenever this happens.
Sanity's simple UI makes it easy for our editors to upload and manipulate content even without much tech knowledge. Sanity's schema system using JS objects makes it easy for us as developers to adjust the UI in response to our editor's feedback. Finally the GROQ language for querying is very powerful. It's transformations drastically simplify our callbacks, and simpler callbacks means less bugs.
I like how it simplifies the setup of anything that I work on. In the past, using something like WordPress, I would often find myself disabling more features than adding. Sanity gives me an easy starting base to add all the elements I need for the websites and tools that I am building. My clients love it as it's easy to use and I love it as my clients can't deviate too far from the design systems I build within their sites.
Sometimes when creating complex nested layouts and page builder style blocks it can get a bit confusing where you are. Usually though it's not too much of a problem.
For me, I'm able to get a CMS ready to roll in a few hours. Previously in other CMS's this would take a lot longer and the results wouldn't be as user friendly. Sanity also allows me to keep clients to stick to specific design elements to keep their sites looking consistent.
The ease of integrating Sanity with your product, whether you need it for only a single feature or if you want it as the core of your product.
As long as you don't forget that it's just a headless CMS, you shouldn't run into any issues with Sanity. Or at least I haven't found any as of yet.
Any time I need the option for product users to manipulate data, Sanity is my go-to due to the ease of integrating it.
One of the best parts of Sanity CMS is how flexible it is. The interface is 100% customizable and configurable. There are almost no limits on how you can configure it. You can change its interface, add icons to content type, or customize per role. I’ve never seen that flexibility in any of the CMS I had experience with.
There are very few elements I can name as downsides. One of them is that you must read the documentation first in order to make use of CMS. To unleash the full power of Sanity CMS, you must spend some time on its internals. The CMS itself is developer friendly. For me, it is a big plus; however, for non-developers, it might be the downside as one should understand how to operate it and how to customize it using code.
In our company Sanity was chosen as a replacement to the old cms system. Before Sanity CMS our marketing department had to use an old system that wasn’t user-friendly and required lots of repetitive work. Using Sanity CMS, we created templates for different content types and displayed them using the front-end application. It allowed product owners to create multiple banners and promotion pages, publish them using the scheduled publishing option, and duplicate content automatically across different environments.
Maintaining your content schemas alongside your application codebase. Easy to release together. The Studio application is so customisable. I honestly haven't seen anything like it on the market.
The documentation is pretty good, but maybe some more information on customisation using the Structure Builder. Need to get v3 out the door more quickly!
Moving from a 'legacy' CMS was made possible by the solution that Sanity offers. We could reshape our content model, which had suffered from years of piecemeal updates and then repopulate using the relevant APIs. Previous attempts to alter content schemas were challenging, even within the same CMS.
Good balance of flexibility and rigidity. As a developer, I can enforce my schema similarly to the ways I can enforce my types with Typescript. This gives me confidence that the data received by the client will be exactly in the shape it expects.
Deeply nested document structures can be difficult to preview/test within a single dataset. This is especially true due to our current setup which includes complex menu data. There are workarounds for this, so not a huge deal.
Creating an easy-to-spin-up/configure structured content experience both on the developer side and on the customer side. We use Sanity to empower our content teams to own the content experience with limited engineering work required.
Super easy to customize. This is the perfect cms for everyone with more than the basic blog. Made by nerds for nerds. It is straightforward to set up and understand. We found that we already understood how to customize code for our needs within the hour. We still have not encountered a task that sanity has not solved for our content.
We don't have any bad stuff for sanity. If anything, it could be easier to import word and pdf without programming. (might be a plugin for this, that I don't know about)
All the content that we serve in our app is from sanity. We have an app for health education (ed-tech), so we rely heavily on content.
I like that I can deploy it quite easily to a project and then modify it as I see fit. Since the whole process can be accomplished in javascript, you can easily extend the functionality into whatever you need. Also, maintenance and hosting are effortless and an absolute joy to work with.
There is not much that I can say I dislike about Sanity. So far, I have not run into a reason not to use it in many of my past projects. I rarely turn away from it when looking for a cms solution
Mainly providing a cms for a static site generator. The combo of sanity and gatsby has become a favorite of mine. Since sanity is so malleable I have been able to use it from a simple blog to designing an eCommerce solution.
Once content is moved to Sanity.io it can be seen on any frontend scenario. This means you can shift with the times regarding what user experience is winning the race without restructuring the content that populates the project. This saves a ton of time by allowing you to restructure projects without restructuring content. Sanity.io also doesn't create an opinionated model for your content. With each project, you decide what is needed. Anything you don't need doesn't exist. This frees up a ton of time either removing, hiding, or updating content editing scenarios that were never in use in the first place.
Tools/Solutions/Tutorials to simplify the migration from popular CMS's could be more abundant. While the migration process helps you leave broken methods in the past, it still would be nice to cherry-pick small tools/tutorials on a case-by-case basis.
Sanity.io has provided a unified (yet inclusive) content layer for our client projects. Clients reaching out with requests nearly never ends in a 'Sorry that's not possible. When we handle the development of their request, it's incredibly fast and logical to build out. What we didn't realize the appreciation we'd get for migrating our client work to Sanity.io. To date, every client we have migrated to Sanity.io from their previous content solution (mostly WP or WebFlow) has said something similar to: "I know I would have to stop using my current solution at some point to keep up. I'm relieved at how easy and fast it is to work in the Sanity studio." or: "I feel like I can't break it which makes it way less stressful to work with" As an agency, Sanity.io has relieved us of feeling like custodians of their content management solution. We spend less time cleaning up things that have broken. Working with content within the Sanity Studio and migrating page content to Portable text offers so many benefits we never realized possible. So much that after 10+ years of using very established solutions at enterprise levels, we can't even justify continued support moving forward.
We are currently running several projects for different purposes, the versatility of Sanity Headless CMS is of great value. Our usage was initially a partner portal, and the use has grown into handling templates for professional systems.
We have not registered anything negative to highlight so far.
We have implemented a new partner portal in a very short time. We are using it to handle templates in professional systems, enabling us to perform changes not related to the release cycle of other systems.
The process to create a content model is simple and intuitive. The Sanity Studio CMS is very flexible and feature-rich. In particular, I like the revision history, image editing and plugins.
There is a learning curve, as with any other headless CMS for people from a WordPress or Drupal background, but this is understandable and something that you have to pay to gain flexibility and a better DX.
My less tech savvy clients can edit the content of their websites on their own, while I can use the frontend that I want, instead of choosing to take the traditional route with WordPress.
I like the total freedom to invent your own data structure, separated from a website or app. And how easy it is to develop and evolve the structure as a project takes form. I can start however many projects, tests, or playgrounds I want for free and only pay as it matures and reaches relevant adaptation.
Sometimes I miss the predictability of relational databases. But then I quickly realise how I never let those types of systems evolve in the same natural way. Most of the functions I found missing in their data query language GROQ is on the roadmap or in their backlog.
I'm building an article library for an app growing in size and complexity in all directions from day to day. Plus heaps of small hobby projects for training and play purposes.
Excellent documentation and flexible pricing make Sanity my CMS solution of choice. It's easy to customize and build an intuitive interface for clients - which is already great out of the box, thanks to the effort put into making it responsive and clean.
Owing to their thorough test and review process, it took relatively long for essential features like conditional fields to be available in production. Sanity also does not provide a drag and drop UI builder tool, like some other platforms, which I think might be helpful.
I have built content-driven sites such as blogs for my clients, and Sanity proves to be a convenient way for them to manage the content that goes on the website. The ease of use is especially evident from all the positive feedback from clients.
I love the developer experience of using Sanity, it feels so simple and yet powerful to use.
Maybe there could be more info about the mindset of creating new schemas and document types.
Sanity is solving the problem of creating an easy to use backend for my websites. This lets me spend more time working on developing the frontend site.
The query language GROQ is very powerful and, coupled with the great docs and superb developer support, has enabled me to use data the way I need to.
Can't think of anything, perhaps more examples of how to customise the studio for clients?
Initially handling fat for an e-commerce site. The site is growing and I have Sanity so easy to scale up.
I love how customizable Sanity is. I've used it for a fitness library, a custom course platform, and several other freelance projects.
There is a bit of a learning curve, although after a project or two, I feel very productive spinning up a new project.
I use Sanity for freelance web development projects requiring a CMS.
The simplicity of use, out-of-the-box to use with typescript, and the sanity studio is fantastic!
At the moment there is nothing to complain
I'm using it for a landing page, and it's awesome.
Best thing about Sanity has to be the dashboard which you can customize based on your needs and also the documentation is well writen and offers great insights for developers who want to implement certain features on their projects.
So far, I didn't find anything that's laking about this platform. If you find that Sanity doesn't offer what your projects need, you won't lose anything since Sanity provides a pretty generous free tier.
The main benefit of this platform is the ease of use and great user and developer experience.
The customisation that they allow. Rather than telling me how to present my data, I can tell Sanity how I want to present it. There are no hard and fast rules. If I want to keep things simple, I can by using schema already built, or I can dive right into the heart of darkness and build from the ground up.
The lack of styling on the backend is my only bugbear. I would like to be able to add more colour and styling to the whole interface. They have done an amazing job with Sanity UI but, sadly, this is the one area that feels prescriptive. You can edit anything and everything (including the styling – Tailwind CSS anyone?), but that is a lot more work.
We have swathes of related data that we needed to get into some sort of controllable order. The fact that various items reference various others made this difficult, but Sanity's schema system and GROQ made this so easy to put together. We can have strong and weak references. I am able to build an admin for staff that answers the questions they have rather than implementing already built systems that kinda answer their questions, but not quite. I can also use external data sources with ease, using custom components.
I find the way to customize the CMS reasonably easy. So far, I have used it in production once. I want to use it more.
I wish there were more generous free usage. I use it for minimal websites that don't have traffic at all. But I wish there was a starter plan that allowed lots of projects in a free or reasonably priced plan.
Switching away from WordPress was a big thing. Sanity is easy to customize and hand it over to the person who can easily update content on their end.
The ability to customize every single bits of the admin interface while starting from sane defaults built over React components.
Documentation is there, but often not specific enough to answer all questions you may have.
I am creating a vitrine website for a client owner of a campsite. Thanks to the heavily customizable admin interface, I can build a UI that specifically caters to their need.
The community is friendly and helpful. Whenever there is an issue, and I get stuck, the Sanity community helps me find my way. Our company uses Sanity as a data collector for our Cognitive Therapy Reading game.
I really can't say that there is anything specifically that I dislike. Whenever anyone on our team uses Sanity for our project, they all find it easy and can get help quickly.
We needed a platform that allowed us to create a place to hold our data for our games using Unity 2020. Sanity typically is used for blogs but was able to support our needs.
The sanity schema is incredibly easy to setup and very extendable. Portable text will change the way you structure content!
Not necessarily a downside, but sanity's structured content makes it easy to structure your content in a sensible way , but it takes a bit to get used to if you're coming from an environment like Wordpress where content is page based.
I don't have to spin up a custom server to host my content which makes hosting costs cheaper. I'm realizing how valuable structured content is across different mediums.
Scalable, customisable. My go-to for just about every project.
Nothing. Anything not to your liking can be customised.
Strict content control and better adherence to style guidelines out of the box. Easiest platform I've seen to enable cross-team collaboration and our build reviews/approvals process directly into the a platform's workflow.
As a developer it is extremely helpful that I can write both the Frontensegeln and cms(backend) in JavaScript. Using sanity makes you feel like you have superpowers.
I have used sanity in over 5 projects now and I still haven't found anything I dislike. And the best thing is the community support in their slack channel.
With sanity I work more sufficient. And best of all Sanity us helped me in the way I structure my content and code for the customer. The easy integration with services like Netlify makes it a dream
The most significant upside to using SANITY is the control you have to customize the editing experience for marketers and content writers.
It could be intimidating for someone who is newer to coding or computer programming to use this tool as you need to code in order to create the UI.
We are creating a fully custom content database for editors and marketers.
Sanity is full of awesome features, to name a few: GROQ query language, customizable studio, unique content editing experience, live preview feature, PORTABLE TEXT!
Sanity is constantly shipping new features and listen to the community. I honestly can't find anything I dislike.
I'm using Sanity for the last 3 years, and it has been a great experience both for my studio and for my clients.
Sanity has built a product that prioritizes both the developers and the content editors equally, making the experience a joy for both parties. The ease of spinning up a fully relational content schema in an afternoon is incredibly empowering for teams that want to move fast.
One obstacle to getting business buy-in to using Sanity is that there's no self-hosting capability. Sanity hosts your data. While they do allow you to export the data, the inability to self-host is a hard-stop for some contexts.
One significant benefit is that product teams predominantly composed of front-end engineers can rapidly build robust, high-integrity relational content schemas despite lacking the back-end experience normally needed to do so.