Showing results from page 20. Use search to find specific reviews.
Unclaimed: Are are working at Sanity ?
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
( 1 )
| 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 |
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.