Sanity Reviews & Product Details
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 |
|
|---|---|
| Segment |
|
| Deployment | Cloud / SaaS / Web-Based |
| Support | 24/7 (Live rep), Chat, Email/Help Desk, FAQs/Forum, Knowledge Base, Phone Support |
| Training | Documentation |
| Languages | English |
Sanity has excellent documentation and a great API, especially if you love GraphQL.
Learning GROQ seems like a unessecary because I haven't run into a reason why GraphQL hasn't worked.
We finally replaced WordPress to give Marketing complete content control.
It is pretty easy to create objects and then be able to refer back to them later when posting documents. I also like the picture search so it's easy to find previous pics.
There are often a lot of bugs with sanity - sometimes it just tells me the referenced object doesn't exist and I have to log out of the whole thing. A lot of times the body input will suddenly glitch and say I put invalid marks and again, I have to reload the whole thing.
Sanity does help us to have a website that we can post content on fairly easily that looks good and well organized with a pretty simple process. The layout does give it a professional look too.
Easily can access the information that I'm looking for with clear directions.
Is not 100% entirely intuitive - i'm not a power user of the tool, so sometimes it's not very easy to navigate.
Content Management. Access to required information.
The ability to modify the Studio to exactly match our needs is nice.
I dislike the lack of different environments - we have those implemented as different datasets, but that means that we can on accident change data in the wrong dataset because we are connected to the only environment that exists. I dislike the low functionality implemented in GROQ. I dislike the Studio styling and how basic the interface is out of the box - to get something truly useful you need to invest a lot of development time, so I wonder whether writing our own UI makes economic sense? I dislike the caching for both the Studio and the data, which means verifying changes takes way too much time, and fixing any issues takes even longer.
We are using Sanity as the primary datastore for content.
not much at all. there are so many bugs.
It's a struggle to get it to function properly. Even simple features like sorting don't work.
It serves as our frontend CMS