Subscribe
Sign in
It is a CMS tool and stack that works well when it is working but works very poorly when it is not working. I hate how it stores its data. I wish there was some sort of data migration or a tool that makes the cloud data and the local schema data of the studio app either communicate better or not at all. So many times I have been working on creating new schemas and there is some sort of miscommunication and then my consuming app does not have the data it should have. It is a decent tool but I really would not recommend it in certain use cases. Those are non-enterprise projects. Luckily the clients on my teams are large organizations so they can waste the money.
It's a great product. The documentation and developer relations seemed to be stretched by the constant growth. Seeing older (outdated?) docs/support content archived would be great. Support is offered in many channels, which is great for some. I would prefer fewer options and more effort in the core docs.
It's just about the worst CMS I've ever used. Whatever it says it does, none of it works in production.
Its pretty good out of the box and the general DX around it is really quite amazing. Until you need to integrate a plugin then its hit and miss. Would love to see better support for internationalization and TypeScript types generation. Also certain common UI elements like tables would be nice to have built in. Despite these drawbacks, I am using this across multiple projects, and I now find that it only takes minutes to setup on a new project.
The whole experience with Sanity composable content (or should that really be 'compostable') is unpleasant, unintuitive and very difficult to get working when it goes wrong. Even the video supplied by Sanity where they migrate V2 to V3 shows them struggling at one point and unable to acheive their objective. I drop f-bombs every day trying to get Sanity to do what I want it to do.
