No reclamado: están trabajando en Sanity ?
Sanity Reseñas y detalles del producto
Sanity es una nube de contenido componible que permite a los equipos crear increíbles experiencias digitales a escala. Proporciona colaboración en tiempo real, edición multiusuario en vivo y control de cambios. Los creadores de contenido, diseñadores y desarrolladores pueden unirse mientras separan el contenido de la presentación.
| Capacidades |
|
|---|---|
| Segmento |
|
| Despliegue | Nube / SaaS / Basado en web |
| Soporte | 24 horas al día, 7 días a la semana (representante en vivo), chat, correo electrónico/servicio de ayuda, preguntas frecuentes/foro, base de conocimientos, soporte telefónico |
| Cursos | Documentación |
| Idiomas | Inglés |
Compara Sanity con otras herramientas populares de la misma categoría.
Sanity is the most flexible CMS I've ever used. It's a dream for content modeling and tailoring the interface to users' needs. Sanity's pricing model is fair, and the team is responsive in Slack.
The documentation leaves one hunting around for answers and there are are not many examples of best practices (except some tailored to one specific framework, which is not helpful to those who don't use it).
Sanity gives us the ability to design a an interface that is easy to use, and give our team a content model that is flexible and modular.
GROQ, APIs, UI, structure, documentation, headless.
We had to spend a lot of time upgrading/migrating our advanced custom implementation on Sanity v2 into Sanity v3.
Our content storing and modeling separated from UI. Great experience for our content team to create and publish content without any dev involvement.
Flexible content model and easy configuration. Custom react components makes for endless possibilities and customization.
Limited data filtering and no bulk editing capability.
We use Sanity for all content management of our website and e-commerce store.
You can fully customize sanity according to your needs.
May be there are some premade options that would be great.
I have a portfolio site that includes blogs. Sanity is helping me in managing my content, categories, and authors easily according to my needs.
The ease of managing catalogs and connecting them to the application
I have had some errors that sometimes blocked me from updating a catalog in the administration platform.
The ease of managing catalogs and products, and is implemented quickly to the application.
I love developing custom components and fields for applications
There's nothing I don't like about Sanity's content studio.
Sanity is solving the headless CMS for all of my NextJS applications
I've been using Sanity CMS for several months now, and I have to say that I'm impressed with the platform. One of the things that stands out to me is how flexible and customizable it is. The fact that it's a headless CMS allows me to use it for various projects, from building static websites with Gatsby to creating mobile apps with React Native. One of the things that I appreciate about Sanity is its content modeling system. Creating and modifying content types and fields is easy, and the user interface is intuitive and user-friendly. The real-time collaboration feature has also been a game-changer for my team. It allows multiple team members to work on the same document simultaneously, which has streamlined our workflow and made managing content across different projects easier. I also appreciate the wide range of integrations that are available with Sanity. It integrates seamlessly with popular front-end frameworks like React, Gatsby, and Next.js, which has made it easy to get up and running quickly. Additionally, the API-first approach of Sanity makes it easy to integrate with other tools and services, such as search engines and analytics tools. One thing to note is that while Sanity is a powerful CMS, it has a learning curve. However, the documentation and support resources are excellent, and the community is active and helpful. Overall, I highly recommend Sanity CMS to anyone looking for a flexible, scalable, and customizable content management system. Its real-time collaboration features, content modeling system, and integrations make it an excellent choice for teams working on variety of projects.
I don't see any downsides to it. It's working well so far for our team.
The way we can set up the meta data regarding the field. Its awesome
Sanity has a really nice developer experience allowing us to integrate into our tech stack with ease and enabling us to easily create a fully customised CMS that enables our clients to deliver their content how they want it and without friction
I would like to see a larger ecosystem of plugins, however this isn't a huge negative as the quality of plugins available so far are excellent and I can only see this getting better with the advent of the new Plugin API in v3.
One of the major problems Sanity solves with such ease is the ability to host the studio ui on their platform without having to worry about the maintenance and overhead of this part ourselves. This benefits us in a number of ways by allowing developers to spend more time on writing features using their tech stack of choice.
I can create my schemas using the GROQ query language to access my content and design components in React to consume them with EASE, that the entire backend is react-based and modifiable to suit my needs. The articles and resources are available online in case I encounter situations requiring help.
I don't particularly appreciate how to do tagging is convoluted, in which you have to install and configure dependencies and that it should be something that is native to the software. Also, the dashboard can be more robust. I don't particularly appreciate having to fiddle often using console.log functions to get url images to work.
Keeping my data housed in a single source of truth within the data lake, the GROQ query language makes accessing the data more accessible than SQL statements. It makes my content available to multiple applications with ease.
Sanity is an excellent compromise between editor and developer experience. It can handle both modeling and presenting data in any way you like. That's a massive advantage over other headless products like Contentful and Prismic, which require you to define schemas via the web app. They are definitely pushing the boundary of what headless CMS's are capable of.
I think the v3 launch was a little premature, and integrating the studio into a Gatsby project isn't there yet (at least, I have seen). I want to see more documentation and sample projects related to v3.
The ability to define content architecture in code saves me a considerable amount of time. A clean and refined editorial experience also reduces the training and support that we have to do.