Comparisons that start from WordPress, the GPL PHP CMS with automatic background updates and a large plugin ecosystem, against CMSs other than Drupal.
For publishers, newsletters and membership sites: WordPress with plugins for members, payments and email against Ghost, which builds those in. Covers the MIT versus GPL licenses, the Node.js and MySQL stack Ghost needs against PHP hosting, what Ghost's WordPress importer moves and leaves behind, and when a multi-purpose site or store should stay on WordPress.
For teams running WordPress headless behind a JavaScript front end: keep WordPress with custom fields plugins and its REST API, or move to Payload, an MIT TypeScript CMS that lives inside a Next.js app. Covers schema in code versus admin configuration, access control, localization, hosting and the rebuild effort, since Payload documents no WordPress importer.
WordPress against Joomla for business websites: plugin and extension ecosystems, built-in multilingual support in Joomla, update and security handling, support windows, hosting requirements and the effort to keep each patched.
Automattic's hosted WordPress.com plans against running WordPress.org software on your own servers: published plan prices, which plans allow plugins, what you take on for updates, security and backups, and when WordPress VIP enters the picture.
Whether to run many WordPress sites as one multisite network or as separate installations: shared users, themes and plugins, subdomain versus subdirectory rules, server requirements and when the WordPress handbook says multisite is the wrong choice.
Running WordPress as a content API behind a separate front end against a classic theme-rendered site: what the REST API gives you, what you lose in themes, plugins and preview, and the extra hosting and build work a headless front end brings.
WordPress, used traditionally or headless, against Strapi's API-first headless CMS: content modeling, editor experience, GPL versus open-core licensing with Enterprise-only features, database support and the Node.js versus PHP hosting stack.
Tell us what you're working on, whether it's a deployment, an audit, a security test or a cyber range. You'll speak with an engineer who can help you scope it.