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

+ 1

+ 1
Add tool

WordPress vs What are the differences?

Introduction: In this article, we will highlight the key differences between WordPress and, two popular content management systems (CMS) used for building websites.

  1. Deployment and Hosting:

    • WordPress: It requires self-hosting, meaning users need to find and manage their own web hosting provider to host their WordPress website.
    • It offers a cloud-based hosting solution, meaning users do not need to worry about hosting or server management. They can directly deploy their website on's infrastructure.
  2. Content Management Approach:

    • WordPress: It follows a traditional Content Management System (CMS) approach where content is stored in a database, and website pages are dynamically generated from that content.
    • It follows a headless CMS approach, where the content is stored separately from the presentation layer. It provides an API through which developers can fetch and display content on their website or application.
  3. Customization and Flexibility:

    • WordPress: It provides a wide range of themes and plugins that allow users to customize their website's design and functionality without much coding knowledge.
    • It provides a flexible content modeling system that allows users to define custom content types and structures. It is more suitable for developers who want to build highly customized websites.
  4. Multilingual Support:

    • WordPress: It has built-in multilingual support and offers plugins like WPML to manage translations of content into multiple languages.
    • It provides built-in internationalization features where users can create variations of content in different languages and manage translations easily.
  5. Workflow and Collaboration:

    • WordPress: It provides basic user roles to manage content creation, editing, and publishing. However, advanced workflow features require additional plugins.
    • It offers collaborative tools, content versioning, and role-based access control, making it easier for teams to collaborate and manage content creation and publishing workflows.
  6. Scalability and Performance:

    • WordPress: It can handle a large number of pages and content but may require optimization and caching plugins for optimal performance.
    • It is built for scalability and can handle high traffic websites without performance issues. It automatically optimizes images and provides a global content delivery network (CDN) for faster content delivery.

In Summary, WordPress is a traditional CMS with self-hosting, while is a cloud-based headless CMS with a focus on customization, scalability, and collaborative workflows.

Advice on and WordPress
Kamil Debbagh
Product Manager at Wooclap · | 8 upvotes · 113K views
Needs advice

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.


  • 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)

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 · 70.5K 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
Gagan Jakhotiya
Engineering Manager at BigBasket · | 1 upvotes · 58.7K views

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

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)

Former 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. 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
Decisions about and WordPress
Kamaldeep Singh

I usually take a slightly different tack because the technical level of people I usually am dealing with is lower. I tend to be pitching to decision makers and not tech people. A bit of my standard answer is below.

Wix and Squarespace are proprietary systems meant for unsophisticated users who want to build their own websites quickly and easily. While they are good for that specific use case, they do not offer any way to move beyond that if your needs arise. Since they are proprietary closed systems if you need something more advanced at some point your only option is to start over.

WordPress is an Open Source CMS that allows much more freedom. It is not quite as simple to setup and create a new site but if you are talking to me then you are not looking to build it yourself so that is really a non-issue. The main benefit of WordPress is freedom. You can host it on virtually any decent web hosting service and since it uses PHP and MySQL you can have virtually any developer take over a project without problem.

I believe in open source because of that freedom. It is good for me as a developer and it is good for my clients. If something were to happen to me or my company you would have no problem finding another qualified WordPress developer to take over the site in a totally seamless fashion. There would be no need to start from scratch.

Additionally the extensible nature of WordPress means that no matter what your future needs, WordPress can handle it. Adding things like e-commerce and custom quoting systems are just two examples of advanced solution's that I have added to WordPress sites years after they were first built.

WordPress is used by tiny one person businesses all the way up to major websites like the NY Times and I think it is right for this project as well.

See more
Xander Groesbeek
Founder at Rate My Meeting · | 5 upvotes · 222.6K views

So many choices for CMSs these days. So then what do you choose if speed, security and customization are key? Headless for one. Consuming your own APIs for content is absolute key. It makes designing pages in the front-end a breeze. Leaving Ghost and Cockpit. If I then looked at the footprint and impact on server load, Cockpit definitely wins that battle.

See more

10 Years ago I have started to check more about the online sphere and I have decided to make a website. There were a few CMS available at that time like WordPress or Joomla that you can use to have your website. At that point, I have decided to use WordPress as it was the easiest and I am glad I have made a good decision. Now WordPress is the most used CMS. Later I have created also a site about WordPress:

See more
Get Advice from developers at your company using StackShare Enterprise. Sign up for StackShare Enterprise.
Learn More
Pros of
Pros of WordPress
  • 7
    Nice writing room
  • 3
    Very Good UX
  • 3 powers
  • 2
    Friendly Pricing
  • 2
    Nice UI and clean
  • 2
    Works with GraphQL with Gatsby
  • 1
    Releases - Scheduling content to go live
  • 1
    Integration Field
  • 1
    Slices - Reusable components
  • 1
    Page "slices" very useful
  • 1
    SDKs for render frameworks
  • 415
  • 366
    Easy to manage
  • 354
    Plugins & themes
  • 258
    Non-tech colleagues can update website content
  • 247
    Really powerful
  • 145
    Rapid website development
  • 78
    Best documentation
  • 51
  • 44
    Product feature set
  • 35
    Custom/internal social network
  • 18
    Open source
  • 8
    Great for all types of websites
  • 7
    Huge install and user base
  • 5
    Perfect example of user collaboration
  • 5
    Open Source Community
  • 5
    Most websites make use of it
  • 5
    It's simple and easy to use by any novice
  • 5
  • 5
    I like it like I like a kick in the groin
  • 4
  • 4
    API-based CMS
  • 3
    Easy To use
  • 2
    <a href="https://secure.wphackedhel">Easy Beginner</a>

Sign up to add or upvote prosMake informed product decisions

Cons of
Cons of WordPress
  • 2
    No write API yet
  • 1
    Bad Documentation
  • 1
    No admin UX control (only schema)
  • 13
    Hard to keep up-to-date if you customize things
  • 13
    Plugins are of mixed quality
  • 10
    Not best backend UI
  • 2
    Complex Organization
  • 1
    Do not cover all the basics in the core
  • 1
    Great Security

Sign up to add or upvote consMake informed product decisions

- No public GitHub repository available -

What is

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.

What is WordPress?

The core software is built by hundreds of community volunteers, and when you’re ready for more there are thousands of plugins and themes available to transform your site into almost anything you can imagine. Over 60 million people have chosen WordPress to power the place on the web they call “home” — we’d love you to join the family.

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

What companies use
What companies use WordPress?
See which teams inside your own company are using or WordPress.
Sign up for StackShare EnterpriseLearn More

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

What tools integrate with
What tools integrate with WordPress?

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

What are some alternatives to and WordPress?
With Contentful, you can bring your content anywhere using our APIs, completely customize your content structure all while using your preferred programming languages and frameworks.
JavaScript is most known as the scripting language for Web pages, but used in many non-browser environments as well such as node.js or Apache CouchDB. It is a prototype-based, multi-paradigm scripting language that is dynamic,and supports object-oriented, imperative, and functional programming styles.
Git is a free and open source distributed version control system designed to handle everything from small to very large projects with speed and efficiency.
GitHub is the best place to share code with friends, co-workers, classmates, and complete strangers. Over three million people use GitHub to build amazing things together.
Python is a general purpose programming language created by Guido Van Rossum. Python is most praised for its elegant syntax and readable code, if you are just beginning your programming career python suits you best.
See all alternatives