Cloud CMS vs Cockpit vs Contentful

Need advice about which tool to choose?Ask the StackShare community!

Cloud CMS

5
35
+ 1
6
Cockpit

36
175
+ 1
10
Contentful

682
775
+ 1
67
Advice on Cloud CMS, Cockpit, and Contentful
Kamil Debbagh
Product Manager at Wooclap · | 7 upvotes · 56.1K views
Needs advice
on
StrapiStrapiprismic.ioprismic.io
and
ContentfulContentful

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.

See more
Replies (3)
Recommends
ContentfulContentful

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

See more
Krassimir Boyanov
Independent IT Consultant, CEO at KBWEB Consult · | 3 upvotes · 36.8K views

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!

See more
Recommends

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!

See more
Maxim Filimonov
Needs advice
on
SanitySanityprismic.ioprismic.io
and
ContentfulContentful

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.

See more
Replies (1)
Recommends
ContentfulContentful

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.

See more
Get Advice from developers at your company using Private StackShare. Sign up for Private StackShare.
Learn More
Pros of Cloud CMS
Pros of Cockpit
Pros of Contentful
  • 4
    API-first, "headless" CMS
  • 2
    Available via SaaS or On-Prem
  • 2
    Easy for Content Managers to understand and use
  • 2
    Open Source
  • 2
    Flexible and plays nicely with any frontend
  • 1
    Fast & lightweight
  • 1
    GraphQL
  • 1
    Self hosted
  • 1
    Modular
  • 28
    API-based cms
  • 17
    Much better than WordPress
  • 11
    Simple and customizable
  • 4
    Images API
  • 3
    Free for small projects
  • 1
    Extensible dashboard UI
  • 1
    Super simple to integrate
  • 1
    Managed Service
  • 1
    Tag Manager like UI

Sign up to add or upvote prosMake informed product decisions

Cons of Cloud CMS
Cons of Cockpit
Cons of Contentful
    Be the first to leave a con
      Be the first to leave a con
      • 5
        No spell check
      • 5
        No repeater Field
      • 3
        Slow dashboard
      • 3
        No free plan
      • 2
        Limited content types
      • 2
        Enterprise targeted
      • 2
        Pricey
      • 1
        Not scalable

      Sign up to add or upvote consMake informed product decisions

      No Stats
      - No public GitHub repository available -
      - No public GitHub repository available -

      What is Cloud CMS?

      Easily Create, Upload and Edit;Use Simple Content Forms;Full Text Search and Query; Workspaces

      What is Cockpit?

      An API-driven CMS without forcing you to make compromises in how you implement your site. The CMS for developers. Manage content like collections, regions, forms and galleries which you can reuse anywhere on your website.

      What is Contentful?

      Contentful enables teams to unify content in a single hub, structure it for use in any digital channel, and integrate seamlessly with hundreds of other tools through open APIs and a leading app framework.

      Need advice about which tool to choose?Ask the StackShare community!

      What companies use Cloud CMS?
      What companies use Cockpit?
      What companies use Contentful?

      Sign up to get full access to all the companiesMake informed product decisions

      What tools integrate with Cloud CMS?
      What tools integrate with Cockpit?
      What tools integrate with Contentful?
        No integrations found

        Sign up to get full access to all the tool integrationsMake informed product decisions

        What are some alternatives to Cloud CMS, Cockpit, and Contentful?
        prismic.io
        Prismic is a Content Management System, a tool for editing online content, also known as a headless CMS, an API CMS, a content platform, a disruptive content-as-a-service digital experience.
        Sanity
        Sanity is a headless, real-time CMS where the editor is an open source React-based construction kit and the backend is a graph-oriented cloud datastore with a globally distributed CDN.
        GraphCMS
        GraphCMS is a GraphQL Based Headless Content Management System. It lets you build a hosted GraphQL backend for your applications and gives you all the tools you need to manage your content.
        Tipe
        All your Apps have text and your developers don't want to manage it. Create and manage your text or assets with powerful editing tools and access it from anywhere with a GraphQL or REST API.
        Nuxeo
        It is a platform for rich and structured content management. Its cloud-native, modular platform plugs easily into legacy infrastructure, scales with your team, and your progress.
        See all alternatives