# Word & Press > An independent guide to publishing CMS software and to running news and article websites: CMS profiles, side-by-side comparisons and practical guides, with sources for every factual claim. word-press.net was the home of phpWordPress, a PHP news and article manager (2004–2006). Word & Press is a new, independent publication on the same subject and is not affiliated with WordPress or any vendor. ## CMS profiles - [CMS for publishers: 24 publishing platforms profiled](https://www.word-press.net/cms/): Fact-checked profiles of the content management systems publishers use, with licences, requirements, editorial features and costs. - [CMS comparison table: licences, versions and prices (free CSV)](https://www.word-press.net/cms/data/): A free CSV of the publishing CMSs we profile, with licence, latest version checked, platform, price and maker, each traceable to a source. - [Ghost for publishers: memberships and newsletters built in](https://www.word-press.net/cms/ghost/): Ghost is an MIT-licensed Node.js publishing platform with built-in memberships and newsletters. Fit for news sites, costs and limits. - [WordPress for news websites: the default choice and its trade-offs](https://www.word-press.net/cms/wordpress/): A publisher's profile of the open-source WordPress software: licence, requirements, editorial workflow, SEO features, extensions, costs and limits. - [Craft CMS for publishers: flexible content modelling at a licence fee](https://www.word-press.net/cms/craft/): Craft CMS is a PHP and Twig system with free Solo and paid Team and Pro editions. What it offers publishers for workflow and multi-site, and the cost. - [Drupal for publishers: structured content and a heavier build](https://www.word-press.net/cms/drupal/): Drupal profiled for publishers: GPL licence, core content moderation, JSON:API, multilingual modules, SEO add-ons, requirements, costs and limits. - [Joomla for publishers: built-in access control and multilingual tools](https://www.word-press.net/cms/joomla/): Joomla profiled for publishers: GPL licence, version 6 requirements, workflow, multilingual and schema.org components, API, costs and limits. - [Statamic for publishers: a flat-file Laravel CMS with a Pro tier](https://www.word-press.net/cms/statamic/): Statamic is a Laravel flat-file CMS with a free Core and a paid Pro edition. What it offers publishers for workflow, APIs and speed, and its limits. - [Kirby for publishers: a flat-file CMS with a one-off licence](https://www.word-press.net/cms/kirby/): Kirby is a flat-file PHP CMS with no database and a paid per-site licence. What it offers publishers for content, roles and languages, and its limits. - [TYPO3 for publishers: workspaces and enterprise-grade structure](https://www.word-press.net/cms/typo3/): TYPO3 profiled for publishers: GPL licence, LTS versions and support dates, Workspaces, SEO extension, multilingual model, requirements and limits. - [Backdrop CMS for publishers: a lighter descendant of Drupal 7](https://www.word-press.net/cms/backdrop/): Backdrop CMS profiled for publishers: GPL licence, version 1.35.1, config management, core Views and layouts, requirements, costs and limits. - [Grav for publishers: a free flat-file CMS built on Markdown](https://www.word-press.net/cms/grav/): Grav is an MIT-licensed flat-file PHP CMS using Markdown and Twig, with no database. What it offers publishers for content, languages and SEO. - [Concrete CMS for publishers: in-context editing under an MIT licence](https://www.word-press.net/cms/concrete/): Concrete CMS profiled for publishers: MIT licence, in-context editing, version 9.5.5, blocks, workflow and multilingual code, requirements, costs and limits. - [ProcessWire for publishers: a flexible PHP CMS with a strong API](https://www.word-press.net/cms/processwire/): ProcessWire is a free, MPL-licensed PHP CMS with role-based access and built-in multi-language support. Fit, cost and limits for publishers. - [Strapi for publishers: open-source headless, paid editorial tiers](https://www.word-press.net/cms/strapi/): Strapi is a self-hosted, MIT-licensed headless CMS on Node.js. Review workflows and audit logs sit behind paid plans, and the front end is yours to build. - [Sanity for publishers: hosted content store, open-source Studio](https://www.word-press.net/cms/sanity/): Sanity pairs a hosted content API with an MIT-licensed editing Studio. Per-seat pricing, GROQ queries, visual editing and a front end you build yourself. - [Contentful for publishers: hosted API-first content platform](https://www.word-press.net/cms/contentful/): Contentful is a hosted, API-first content platform with separate delivery and preview APIs. What its front end must handle, and what we could not verify. - [Storyblok for publishers: visual editing on a hosted headless CMS](https://www.word-press.net/cms/storyblok/): Storyblok is a hosted headless CMS built around a Visual Editor. Plans start free, with workflows, scheduling and roles that depend on your tier. - [Payload for publishers: MIT-licensed headless CMS inside Next.js](https://www.word-press.net/cms/payload/): Payload is a free MIT-licensed headless CMS that installs inside a Next.js app. Roles and workflow are written in code, so it favours developer-led teams. - [Directus for publishers: SQL-first headless CMS, source-available](https://www.word-press.net/cms/directus/): Directus wraps your SQL database in APIs and an admin studio. Its licence is source-available, not open source, with a free tier and an eligibility grant. - [Umbraco for publishers: an MIT-licensed .NET CMS](https://www.word-press.net/cms/umbraco/): Umbraco is a free, MIT-licensed .NET CMS with scheduled publishing and a headless API. What it offers publishers, what it costs and where it falls short. - [Wagtail for publishers: a Django CMS built around editors](https://www.word-press.net/cms/wagtail/): Wagtail is a BSD-licensed Python and Django CMS with StreamField, workflows and an API. What it offers publishers, what it costs and where it falls short. - [django CMS for publishers: placeholders, plugins and versioning](https://www.word-press.net/cms/django-cms/): django CMS is a BSD-licensed Python CMS with front-end editing and multilingual support. What it offers publishers, what it costs and where it falls short. - [Hugo for publishers: a fast static site generator, not a CMS](https://www.word-press.net/cms/hugo/): Hugo is an Apache-licensed static site generator in Go. How editors work with it through Markdown, Git or a Git-based CMS, and where it falls short. - [Decap CMS for publishers: a Git-based editor for static sites](https://www.word-press.net/cms/decap/): Decap CMS (formerly Netlify CMS) is an MIT-licensed, Git-based editor for static sites. What it gives editors, how workflow works and where it falls short. - [Arc XP for publishers: The Washington Post's enterprise platform](https://www.word-press.net/cms/arc-xp/): Arc XP is a proprietary media platform developed by The Washington Post, with the Composer editor and an API. What public sources say and what they leave out. ## Compare - [CMS comparison for publishers: platforms side by side](https://www.word-press.net/compare/): Side-by-side comparisons of CMSs for news and article publishers, covering licences, editorial workflow, SEO controls, hosting and cost. - [WordPress vs Drupal for publishers: simple launch or structure?](https://www.word-press.net/compare/wordpress-vs-drupal/): WordPress and Drupal compared for news and magazine sites: licence, versions, editorial workflow, SEO, multilingual, headless use, hosting and cost. - [WordPress vs Ghost for publishers: plugins or built-in memberships?](https://www.word-press.net/compare/wordpress-vs-ghost/): WordPress and Ghost compared for publishers: licence, hosting stack, editorial roles, SEO, memberships and newsletters, headless use and cost. - [WordPress vs Joomla for publishers: plugins or built-in components?](https://www.word-press.net/compare/wordpress-vs-joomla/): WordPress and Joomla compared for publishers: licence, versions, requirements, workflow, SEO, multilingual, API, and what each documents as core. - [Drupal vs Joomla for publishers: documented depth or built-in parts?](https://www.word-press.net/compare/drupal-vs-joomla/): Drupal and Joomla compared for publishers: licence, versions, requirements, moderation and workflow, multilingual, SEO modules, APIs and cost. - [Drupal vs TYPO3 for publishers: two developer-led systems compared](https://www.word-press.net/compare/drupal-vs-typo3/): Drupal and TYPO3 compared for larger publishers: licence, support dates, moderation and Workspaces, SEO, multilingual model, requirements and cost. - [Strapi vs Sanity for publishers: self-hosted or hosted content store?](https://www.word-press.net/compare/strapi-vs-sanity/): Strapi is a self-hosted, MIT-licensed headless CMS. Sanity is an MIT Studio on a hosted data store. How they differ on workflow, roles, cost and front-end work. - [Sanity vs Contentful for publishers: two hosted headless platforms](https://www.word-press.net/compare/sanity-vs-contentful/): Sanity and Contentful are both hosted headless platforms. What the docs show on drafts, preview, pricing and front-end work, and what we could not read. - [Contentful vs Storyblok for publishers: API-first or visual editor?](https://www.word-press.net/compare/contentful-vs-storyblok/): Contentful is an API-first hosted platform; Storyblok is built around a Visual Editor. Workflow, preview, pricing and what we could not verify. - [Strapi vs Payload for publishers: admin-first or code-first?](https://www.word-press.net/compare/strapi-vs-payload/): Strapi and Payload are self-hosted, MIT-licensed headless CMSs on Node.js. How they differ on roles, drafts, preview, databases and what developers must build. - [Strapi vs Directus for publishers: MIT core or source-available?](https://www.word-press.net/compare/strapi-vs-directus/): Strapi's Community Edition is MIT; Directus is source-available under the Monospace Sustainable Core License. Licence, cost, workflow and SQL support compared. - [Ghost vs Craft CMS for publishers: reader revenue or custom build?](https://www.word-press.net/compare/ghost-vs-craft/): Ghost and Craft CMS compared for news and magazine sites: licences, editorial roles, SEO, hosting and what each really costs to run. - [Craft CMS vs Statamic for publishers: database or flat files?](https://www.word-press.net/compare/craft-vs-statamic/): Craft CMS and Statamic compared for publishers: licence terms, editions, editorial workflow, APIs, hosting and cost for developer-led news sites. - [Kirby vs Grav for publishers: paid licence or free Markdown?](https://www.word-press.net/compare/kirby-vs-grav/): Kirby and Grav compared for small publishers: two flat-file PHP CMSs with no database, differing on licence, cost, editorial controls, SEO and languages. - [Wagtail vs Drupal for publishers: Python editors or PHP structure?](https://www.word-press.net/compare/wagtail-vs-drupal/): Wagtail and Drupal compared for news and magazine sites: licences, workflow, SEO modules, languages, APIs, hosting and cost for developer-led teams. - [Umbraco vs Drupal for publishers: .NET or PHP, and who builds it?](https://www.word-press.net/compare/umbraco-vs-drupal/): Umbraco and Drupal compared for publishers: MIT and GPL licences, editorial workflow, SEO, languages, headless APIs, hosting and cost of ownership. - [Payload vs Sanity for publishers: self-hosted code or hosted Studio?](https://www.word-press.net/compare/payload-vs-sanity/): Payload is a self-hosted, MIT-licensed CMS inside Next.js. Sanity is an MIT Studio on a hosted data store. How they differ on roles, drafts, preview and cost. ## Guides - [How to choose a CMS for a news website: practical guides](https://www.word-press.net/guides/): How to choose, license, budget for and run a CMS for a news, magazine or article website, written for editors and publishers. - [Website CMS manuals: practical guides to running a publishing CMS](https://www.word-press.net/doc/): Practical administration guides for editors and publishers: how a CMS works, how to organise content, and how plugins and themes behave. - [CMS features checklist for news and article publishers](https://www.word-press.net/features.php): A practical checklist of the CMS features a news or article publisher should require, with why each matters and what to ask the vendor. - [CMS licences explained: GPL, MIT and commercial](https://www.word-press.net/license.php): What GPL, MIT, source-available and SaaS licences mean for a publisher who wants to own, modify or sell a site, with real CMS examples. - [How much does a CMS cost? A publisher's guide to running costs](https://www.word-press.net/pricing.php): The real cost of running a news or article CMS: licences, hosting, development, plugins, maintenance and migration, with vendor prices cited. - [How to evaluate a CMS: trial it before you commit](https://www.word-press.net/demo.php): A practical method for evaluating a publishing CMS: demos, local installs, realistic test content, an editor task script and what to measure. - [News site design patterns: pages, accessibility and speed](https://www.word-press.net/gallery.php): Design patterns for news and article sites: home page, section fronts, article and author pages, with WCAG 2.2 and Core Web Vitals as the checks. - [How to evaluate a CMS editor: a task-based checklist](https://www.word-press.net/screenshots.php): A task-based checklist for judging a CMS editing interface: drafting, embeds, images, preview, revisions and accessibility, using W3C's ATAG 2.0. - [Accepting contributor and reader submissions safely](https://www.word-press.net/tour.html): How to set up roles, review queues and spam control for contributor and reader submissions, and how to label sponsored posts and user links. - [Web CMS reviews: how to read CMS comparisons critically](https://www.word-press.net/reviews.php): How to judge CMS reviews and comparison articles: affiliate disclosures, testing claims, sources and dates, using the US FTC's endorsement guidance. - [What CMS do news sites use? Sourced examples from publishers](https://www.word-press.net/sites.php): Twelve publishers and the CMS each is documented as using, every one backed by a vendor case study, a vendor showcase page or the publisher itself. ## Headless - [Headless CMS for publishers: headless and static explained](https://www.word-press.net/headless/): When a headless CMS or static site suits a publisher, how editorial preview and workflow change, and what it costs to run. ## Self-hosted - [Self-hosted CMS for a news or article site: what it takes](https://www.word-press.net/self-hosted/): What it takes to install, secure, back up and maintain a self-hosted CMS for a publishing website, from server requirements to updates. - [How to install a CMS on a server: self-hosted PHP setup today](https://www.word-press.net/doc/installation.html): What installing a self-hosted PHP CMS involves: PHP, database and web server requirements, domain and SSL, install steps, hardening and backups. ## History - [The history of word-press.net and phpWordPress](https://www.word-press.net/history/): The release history of phpWordPress, the PHP news and article manager that lived on this domain from 2004 to 2006, and what became of it. - [phpWordPress release history: versions 2.52 to 3.25](https://www.word-press.net/whatsnew/): Version-by-version history of phpWordPress from 2.52 in 2004 to 3.25 in 2006, with what each release added, and which ideas became standard. - [phpWordPress news and press releases, 2004 to 2006](https://www.word-press.net/news.php): A dated timeline of phpWordPress news, press releases and forum announcements from 2004 to 2006, ending with the rename to Vivvo. - [phpWordPress changelog: versions 3.11, 3.2 and 3.25](https://www.word-press.net/changelog.php): The archived phpWordPress changelog for 3.11, 3.2 and 3.25 (January to June 2006), set out by version, with notes on writing CMS release notes today. - [phpWordPress 3.2 tabbed article management, then and now](https://www.word-press.net/whatsnew/feature1.php): What tabbed article management did in phpWordPress 3.2 in 2006, and how Ghost and WordPress organise article settings in their editors today. - [phpWordPress 3.2 membership-based access, then and now](https://www.word-press.net/whatsnew/feature2.php): How phpWordPress 3.2 limited site sections to registered members in 2006, and how Ghost and WordPress control who can read content today. - [phpWordPress 3.2 in-place editing for Preferences, then and now](https://www.word-press.net/whatsnew/feature3.php): What in-place editing for Preferences meant in phpWordPress 3.2 in 2006, and how WordPress now previews changes live before they are published. - [phpWordPress 3.2 improved search, then and now](https://www.word-press.net/whatsnew/feature4.php): What the advanced search in phpWordPress 3.2 offered in 2006, with its changelog trail since 2005, and how Ghost's built-in search works today. - [phpWordPress 3.2 new plug-in manager, then and now](https://www.word-press.net/whatsnew/feature5.php): The rebuilt plug-in manager in phpWordPress 3.2 (2006) and its central dump manager, compared with the official WordPress and Drupal approaches today. - [phpWordPress 3.2 ContactBuilder plug-in, then and now](https://www.word-press.net/whatsnew/feature6.php): What the ContactBuilder wizard in phpWordPress 3.2 did in 2006, and how Drupal's Contact module and the Contact Form 7 plugin handle contact forms now. ## Forums - [The phpWordPress support forum, 2004–2006, revisited](https://www.word-press.net/forums/): Questions and announcements from the original phpWordPress support forum, kept as history and answered again for today's publishing software. - [News and Announcements, from the phpWordPress forum](https://www.word-press.net/forums/forumdisplay.php?f=5): Archived company news and announcements from the phpWordPress support forum, 2004 to 2006, from releases to server moves. - [Product Updates, from the phpWordPress forum](https://www.word-press.net/forums/forumdisplay.php?f=8): Archived product update threads from the phpWordPress forum, covering new features, fixes, patches and upgrade questions from 2005 and 2006. - [Testimonials and Feedback, from the phpWordPress forum](https://www.word-press.net/forums/forumdisplay.php?f=13): Archived customer feedback from the phpWordPress support forum, kept as a record of what 2006 publishers valued in their article software. - [Chit-Chat, from the phpWordPress forum](https://www.word-press.net/forums/forumdisplay.php?f=14): Archived general discussion from the phpWordPress forum, covering feature requests, traffic logs, browser quirks and vendor support. - [Themes and templates for a news CMS: buy, build and keep upgrades safe](https://www.word-press.net/forums/showthread.php?t=144): Buying or building a news site theme, keeping customisations upgrade-safe with child themes and template overrides, and checking performance and accessibility. - [Why CMS template hacks break on upgrade, and how to customise safely](https://www.word-press.net/forums/showthread.php?t=179): Why editing core files and line numbers breaks at upgrade time, and how template overrides, hooks, child themes and version control keep customisations safe. ## About - [About Word & Press](https://www.word-press.net/about/): Who publishes Word & Press, why this domain has a twenty-year history with publishing software, and how we stay independent. - [Editorial policy](https://www.word-press.net/editorial-policy/): The rules Word & Press writes by, covering sourcing, independence, how we describe testing, archive material and updates. - [How we research publishing software](https://www.word-press.net/how-we-test/): The evidence behind every Word & Press CMS profile, from vendor documentation to our own installs, and how scores will work.