Need advice about which tool to choose?Ask the StackShare community!
Sanity vs prismic.io: What are the differences?
Flexibility of Structure: One key difference between Sanity and prismic.io is the flexibility of structure. In Sanity, the data structure is very flexible, allowing for the creation of custom schemas and relations between different content types. This makes it suitable for complex projects or websites with changing requirements. On the other hand, prismic.io follows a more rigid content model approach where the structure is predefined and it might not be as adaptable to changing requirements or complex relationships between content types.
Collaborative Editing: Another difference between Sanity and prismic.io is in their approach to collaborative editing. Sanity offers real-time collaborative editing, allowing multiple users to work on the same content simultaneously and see instant updates. This can be beneficial for teams working on content creation or editing together. However, prismic.io does not provide real-time collaboration out of the box. Users need to manually save and publish changes, which can be limiting for teams that require simultaneous editing.
Hosting and Infrastructure: When it comes to hosting and infrastructure, Sanity and prismic.io have different approaches. Sanity is a headless CMS that allows users to host their data wherever they choose, giving them full control over their hosting solution. This can be advantageous for users who require specific hosting configurations or have existing infrastructure in place. In comparison, prismic.io provides an all-in-one hosting solution, taking care of the infrastructure and hosting the content on their own servers. This convenience of hosted infrastructure might be beneficial for users who prefer a simpler setup.
Querying and Retrieval of Content: The way content is queried and retrieved differs in Sanity and prismic.io. Sanity uses a powerful query language called GROQ (Graph-Relational Object Queries) which allows for complex queries, filtering, and sorting of content. This can be useful in scenarios where highly customized content queries are required. In contrast, prismic.io uses a more simplified querying system, but it provides features like pagination and filtering that can still meet the needs of most projects.
Webhooks and Automation: Sanity and prismic.io handle webhooks and automation differently. In Sanity, webhooks can be set up to trigger automated processes whenever certain events occur, such as content updates or publishing. This allows for easy integration with external services or custom workflows. On the other hand, prismic.io does not natively support webhooks, although it offers a RESTful API that can be used to build custom integrations or automation.
Pricing Model: One important difference to consider is the pricing model offered by Sanity and prismic.io. Sanity provides a generous free tier with certain limitations, and their pricing is based on usage, such as the number of API calls, bandwidth, and storage. This can be beneficial for smaller or low-traffic websites. In contrast, prismic.io offers a more traditional tiered pricing model that includes a limited free plan and paid plans with different features and usage limits. The choice of pricing model could depend on the specific needs and budget of a project.
In summary, Sanity offers more flexible structure and collaborative editing abilities, allows users to host their data independently, provides a powerful query language, supports webhooks for automation, and offers a usage-based pricing model. On the other hand, prismic.io follows a more rigid content model approach, provides an all-in-one hosted solution, has a simpler querying system, lacks native webhook support, and has a tiered pricing model.
Hi StackSharers, your help is dearly needed as we're making a move to which we will commit for the next few years.
Problem: As our Marketing team gets growing needs to publish content fast and autonomously, we're trying to add a CMS to our stack.
Specs:
This CMS should have fairly advanced marketing features: either natively built, and/or be open source, so we can either find third parties' plugins suiting our needs or build our own plugins homebrew.
"Advanced marketing features" like these: Non-devs should be able to handle content autonomously, Should have a non-dev friendly interface, should allow creating a library of reusable components/modules, should show the preview before publishing, should have a calendar with all publications, should show the history/tracking, should allow collaborating (Google Docs like), should display characters limit optimized for SEO.
Solution: We're considering an SSG + Headless CMS combination. We're fairly confident for the SSG (Gatsby), but we're still uncertain which CMS we should choose.
Of all the content management systems out there, contentful seems to be the most flexible. It consist of an user interface with an API a front end app can retrieve data from.
It makes no assumptions about how your data is presented or structured, and you can form any kind of content in the interface. Architectural portfolio with square footage attributes? Check. Carousel section on a page? Check. A blog? No problem. Entire landing pages consisting of sections that have child items in them and attributes for each child? Not an issue. Image hosting / cdn and resizing? No problem. Character limits? Widely supported. Multilingual? Easy peasy
There are two parts of the interface. Content types and content items. Content types is just a definition of how a content item is structured, you can add fields such as title, unique id, image, rich text, lists of child content items, etc. And then the API will just return a list of content items in JSON array or object format.
There is service integration with common apps, or data sources.
Because it’s just an API call, you can use literally any tech stack with it. It won’t stop you from using MySQL or any other technology alongside it. No messing about compilation, Java, maven, like with AEM. No being constrained to the CMS’s programming language or hosting environment like with Wordpress (to an extent, wp has an API too). You can integrate it with any app, whether it be serverless, on a vm, or inside a docker container.
Downside is the front end is really up to you. It’s just a cms for structuring your data. No preview though. How you present it is not handled by contentful. It is it’s greatest strength and not a weakness though
Hi Kamil, Have you considered Adobe Experience Manager (AEM)? It is not completely open-source but is built on top of many open source modules - like Apache Sling, Apache Felix, has a great deal of open-sourced core components, supports SPA - React and Angular Recently and can be deployed as a cloud service. Good luck in your search!
I'd like to share my experience for a similar use case.
A couple of months back I was in a similar place while facing some similar set of challenges within our SEO and Content Team. We were working with WordPress at that moment and for some parts - we still do. While WordPress is a very fast, intuitive and comprehensive tool to power static pages, it's not ideal for: 1. The content team as it requires some level of technical skills 2. Code reusability perspective - impacts performance in a longer run 3. Performance and user experience can easily go for a toss considering content team may not be diligent with everything outside the scope of the content
While evaluating we were looking at these key criterias: 1. SEO, Performance and UX 2. Ease of use for Content Team, developer independence 3. Learning Curve for devs and more importantly content creators 4. Support for complex design cases 5. Cost
Being part of a small org on a tight budget our natural inclination was for open-source solution, Strapi, and so we gave it a go for a smaller project before jumping the marketing wagon.
Strapi is a great tool, easy to learn and pick up. You get most of the design use cases out of the box baked for you. It's a Node.js service so you'll need to manage the service (meaning you'll have to handle monitoring, logging, cdn, auth, etc) and DB - which requires quiet some dev bandwidth. Now Strapi is still very young in term of DB migrations (not a seamless deployment yet - no schema diffing mechanism), setting up different environments required effort and you can do content modeling only in development environment (the db migrations complexity) - which becomes really critical when you want devs, design and content to collaborate simultaneously and don't want repeated work for modeling. Over a 5-6 weeks of use we realised that more and more dev bandwidth is required to do progressive addition of new content and hence we did another PoC with contentful.
Comparing this with contentful - which is a managed service, comes with inbuilt environment and preview setup, gives on-the-fly content modeling (replacing all the dev bandwidth dependency for managing migrations, cdn, auth, service, etc) gives a huge advantage of speed and developer independence at a very moderate price. Plus, the UI is very intuitive (taking some concepts from Tag Manager).
Few other thing to highlight: - Both Strapi and Contentful have plugins for common tooling. - Both the dashboard supports custom data type and UI extensions. I found Contentful UI extensions much more easier to implement. - Contentful has only US based availablility zone. Simple in-memory caching can be used to improve costing and SLA.
Hope this helps!
Hi Community, Would like to ask for advice from people familiar with those tools. We are a small self-funded startup and initial cost for us is very important at that stage. That's why we are leaning towards Sanity. The CMS will be used to power our website and flutter cross-platform mobile applications.
Former Prismic.io developer here. If you want something robust vs "looks good from a distance," I would recommend Contentful. They are the biggest for a reason. Their CMS handles a lot of use cases and has great documentation. Prismic.io will work well in simple blog-esque use cases. Their more complex features break easily and their documentation is confusing. It has fallen quite a distance behind Contentful. Sanity appears to be a much newer CMS and you might come to regret the lack of features, but I've only briefly reviewed their product.
Pros of prismic.io
- Nice writing room7
- Very Good UX3
- Prismic.io powers lichess.org/blog3
- Friendly Pricing2
- Nice UI and clean2
- Works with GraphQL with Gatsby2
- Releases - Scheduling content to go live1
- Integration Field1
- Slices - Reusable components1
- Page "slices" very useful1
- SDKs for render frameworks1
Pros of Sanity
- Headless12
- Hosted11
- Realtime7
- Powerful read + write API7
- Free for small projects7
- Customizable6
- API-based cms5
- Schema as a code5
- Easy setup, endless flexibility4
- Lightweight & pluggable Content studio4
- Works with GraphQL with Gatsby4
- Images API4
- Much better than WordPress4
- Preview content1
Sign up to add or upvote prosMake informed product decisions
Cons of prismic.io
- No write API yet2
- Bad Documentation1
- No admin UX control (only schema)1