Compare les CMS (WordPress, Shopify, Sanity, Strapi, Payload, Webflow, Ghost) pour un brief client et recommande la meilleure stack

Scaffold un thème Shopify Online Store 2.0 complet (sections modulaires + CI Theme Check)

Scaffold un projet WordPress 6.x moderne (block theme FSE + plugin custom + dev environment)

Ghost 5 publishing platform specialist — build and maintain Ghost themes with Handlebars templates (default.hbs, index.hbs, post.hbs, page.hbs, tag.hbs, author.hbs), members functionality (signup, signin, portal, tiers, subscriptions, comments), newsletters (ActiveMQ-style distribution, Mailgun integration), Ghost Admin API (posts, pages, members, tiers, newsletters mutations), Ghost Content API (public read-only for headless setups), Staff Apps (custom integrations), webhooks, and deployment (self-hosted Node + MySQL, Ghost(Pro) managed, or Docker). Use for any Ghost project: theme development, members portal customization, newsletter editor configuration, Admin/Content API consumption, headless Ghost with Next.js frontend, migration from WordPress/Medium/Substack, or integrating Stripe for paid subscriptions. Differentiates from WordPress (CMS-first plugin ecosystem) by being publisher-first with built-in memberships and newsletters — no plugin needed for paid subscriptions. Differentiates from Substack by self-hostability and full API control. The go-to choice for editorial sites, author newsletters, and membership publications.

Magento 2 / Adobe Commerce expert agent — covers Magento 2.4.x architecture (modules, themes, layouts XML, blocks, view models, UI components), PWA Studio for headless storefronts (React-based PWA replacing Luma theme), Adobe Commerce Cloud (managed hosting with built-in CDN, Fastly, image optimization, cron jobs), GraphQL API (the modern API replacing legacy REST and SOAP), MSI (Multi-Source Inventory), MVS (Multi-Vendor Sales), Catalog (products, attributes, categories, EAV model), Cart Rules + Catalog Rules for promotions, Sales (orders, invoices, shipments, credit memos, RMA), Customer (segments, groups, B2B Company accounts), Indexers (price, stock, URL rewrites, Elasticsearch), Caching (Varnish full-page cache, Redis for session + cache, OPcache), database optimization (read replicas, split databases for catalog vs sales vs checkout), CLI commands (bin/magento setup:upgrade, cache:flush, indexer:reindex, queue:consumers:start, deploy:mode:set), composer-based module installation, security (Magento Security Scan, 2FA mandatory, signed extensions from Marketplace), and migration from Magento 1 to Magento 2. Use when developing modules, themes, or integrations for Magento 2 / Adobe Commerce, debugging performance issues, implementing B2B features, hardening security, or migrating between versions. Differentiates from `wordpress-expert` (WooCommerce on WP) and `shopify-expert` (Shopify Liquid + Hydrogen) by Magento-specific architecture (PHP enterprise-grade EAV model, complex caching layers).

Payload CMS 3 headless CMS specialist — build and maintain TypeScript-first Node.js/Next.js backends with Collections (CRUD entities), Globals (singleton data), Blocks (reusable content sections for rich text and page builders), Access Control (field-level and document-level permissions via functions), Hooks (beforeChange, afterChange, beforeValidate, afterRead, etc.), Jobs Queue (background workers), Admin UI customization (field overrides, custom components, custom views), Rich Text Editor (Lexical-based with custom features), Localization (locale arrays), Versions and Drafts, and integrations with Next.js App Router (Payload 3 runs inside Next.js). Use for any Payload project: schema design via TypeScript config, custom field types, access control logic, hooks for business logic, background jobs, Admin UI extensions, rich text customization, i18n setup, or Payload + Next.js monorepo architecture. Differentiates from Strapi (PHP-style schema files) and Sanity (GROQ + Studio) by being fully TypeScript, code-first (no Content-Type Builder UI), and by running natively inside Next.js App Router for zero-cold-start headless commerce.

Sanity headless CMS specialist — structured content modeling with defineType/defineField, GROQ queries (buyer-facing and introspective), TypeGen for end-to-end type safety, Sanity Studio v3 customization (structure builder, singletons, desk tool, custom components), Portable Text rendering and custom serializers, Visual Editing with Presentation Tool + Stega + live preview, image pipeline (URL builder + hotspots + LQIP + Next.js Image integration), localization (document vs field-level), content migrations (JSON import, HTML → Portable Text via block-tools), and Sanity App SDK for custom applications. Use for any Sanity project: schema design, GROQ queries, Studio extensions, preview setups, framework integrations (Next.js / Nuxt / Astro / Remix / SvelteKit / Angular / Hydrogen), content migrations, or reviewing an existing Sanity codebase. Differentiates from other headless CMS experts (strapi-expert, payload-expert) by mastering Sanity's unique concepts: GROQ (not GraphQL), Studio as a first-class editing UI, Content Lake architecture, and Presentation-based Visual Editing. Leverages the imported sanity-best-practices + sanity-content-modeling + sanity-seo-aeo + sanity-content-experimentation skills as authoritative references, and the Sanity MCP server (mcp.sanity.io) when available for live dataset introspection.

Shopify platform specialist — build and maintain Online Store 2.0 themes (Liquid + JSON templates + sections + blocks + metafields UI), Shopify apps (Remix framework + App Bridge + OAuth + webhooks + billing), Hydrogen headless storefronts (React + Remix on Oxygen), Shopify Functions (Wasm in Rust or JavaScript for discounts, shipping, payments, checkout), Storefront API queries (GraphQL for buyer experience), Admin API mutations (GraphQL for merchant operations), Polaris design system for embedded app UIs, and commerce primitives (products, variants, metaobjects, checkouts, orders, fulfillments, subscriptions via Selling Plans). Use for any Shopify project: theme development, app development (public or custom), checkout customization via Shopify Functions or UI Extensions, headless migration to Hydrogen, B2B/Plus customizations, multi-currency/multi-market setup, or custom commerce workflows. Differentiates from atum-stack-web generic React/Next.js coverage by mastering Shopify-specific constraints: Liquid DSL, OS 2.0 JSON templates, Theme Editor UX, section/block schemas, Hydrogen's Oxygen deployment, App Bridge session tokens, webhook HMAC verification, and the billing + privacy compliance required for App Store submission.

Strapi 5 headless CMS specialist — build and maintain Strapi backends with content-types (collection types + single types + components + dynamic zones), custom plugins (admin + server extensions), role-based permissions, i18n localization, media library with providers (AWS S3, Cloudinary), Document Service API (Strapi 5 replacement for Entity Service), REST and GraphQL endpoints, lifecycle hooks, custom controllers and services, webhooks, and deployment (self-hosted Node + Postgres, or Strapi Cloud). Use for any Strapi project: schema design (content-type builder), writing custom plugins, extending admin panel UI, configuring i18n workflows, creating lifecycle hooks, querying via Document Service, deploying to production, or migrating from Strapi v4 to v5. Differentiates from other headless CMS experts (sanity-expert, payload-expert) by mastering Strapi's unique concepts: the content-type builder workflow, the plugin architecture (admin SPA + server routes), the Document Service API v5, and the permission model with RBAC roles.

Webflow platform specialist — build and maintain Webflow sites via the Designer (visual builder), CMS (collections + items + rich text + reference fields + multi-image galleries), Ecommerce (products, variants, checkout, Stripe/PayPal), DevLink (sync Designer components as React components for code projects), Logic (visual workflow automation with API calls + Make.com/Zapier bridges), Code Components (custom React/Vue components embeddable in the Designer), and Webflow APIs (Data API for CMS programmatic access, Designer API for Designer extensions, Site API for site management, Apps API for marketplace extensions, Webhooks for event-driven integrations). Use for Webflow projects: Designer customization, CMS modeling, rich text content strategy, ecommerce store setup, DevLink integration with a React codebase, Logic workflows, Code Components authoring, custom apps for the Webflow App Marketplace, Webflow → Sanity/Strapi/Payload migration, or consuming the Webflow Data API from an external app. Differentiates from pure code CMS (Sanity/Strapi/Payload) by being visual-designer-first, merchant-friendly, with native hosting — and from WordPress by having a modern component system and no plugins to maintain.

WordPress 6.x agency-grade specialist — build and maintain block themes (FSE with theme.json), classic themes, custom plugins, Gutenberg blocks (native + ACF), WP-CLI automation, REST API endpoints, Multisite networks, headless WordPress, and WooCommerce integration. Use for any WordPress project: theme/plugin development from scratch, legacy migration to block themes, Gutenberg block library authoring, custom post types and taxonomies, ACF field architecture, WP-CLI deployment scripts, REST API extension, security hardening, performance audits, and WooCommerce customization. Differentiates from the generic PHP expert in atum-stack-backend by mastering WordPress conventions (hooks system, template hierarchy, block.json registration, kses sanitization, wp_nonce, capability checks) and the WordPress plugin/theme ecosystem that no generic PHP agent knows. Covers WordPress 6.x+ including Full Site Editing, global styles, pattern libraries, and the block editor Data API.

CMS and headless architecture decision framework — compare WordPress, Shopify, Sanity, Strapi, Payload, Webflow, and Ghost across 12 criteria (content modeling flexibility, editor experience, developer experience, pricing model, hosting, i18n, multi-currency, e-commerce support, API maturity, migration effort, team size fit, vendor lock-in). Use when a client brief requires choosing a CMS or e-commerce platform, when planning a migration between CMS, when architecting a multi-CMS setup (e.g. Shopify for commerce + Sanity for content), or when reviewing an existing stack for fit. Differentiates from individual CMS expert agents by being platform-agnostic and decision-oriented: outputs a recommendation, not implementation code. Companion to the /cms-compare slash command which applies this framework to a specific brief.

Sanity development best practices for schema design, GROQ queries, TypeGen, Visual Editing, images, Portable Text, Studio structure, localization, migrations, and framework integrations such as Next.js, Nuxt, Astro, Remix, SvelteKit, Angular, Hydrogen, and the App SDK. Use this skill whenever working with Sanity schemas, defineType or defineField, GROQ or defineQuery, content modeling, Presentation or preview setups, Sanity-powered frontend integrations, or when reviewing and fixing a Sanity codebase.

Content experimentation and A/B testing guidance covering experiment design, hypotheses, metrics, sample size, statistical foundations, CMS-managed variants, and common analysis pitfalls. Use this skill when planning experiments, setting up variants, choosing success metrics, interpreting statistical results, or building experimentation workflows in a CMS or frontend stack.

Structured content modeling guidance for schema design, content architecture, content reuse, references versus embedded objects, separation of concerns, and taxonomies across Sanity and other headless CMSes. Use this skill when designing or refactoring content types, deciding field shapes, debating reusable versus nested content, planning omnichannel content models, or reviewing whether a schema is too page-shaped or presentation-driven.

SEO and AEO best practices for metadata, Open Graph, sitemaps, robots.txt, hreflang, JSON-LD structured data, EEAT, and content optimized for search engines and AI answer surfaces. Use this skill when implementing page SEO, technical SEO, schema markup, international SEO, AI-overview readiness, or improving content for Google, ChatGPT, Perplexity, and similar assistants.

Shopify Hydrogen (headless React storefront) pattern library — Hydrogen 2024+ with Remix + Vite, Oxygen edge deployment, Storefront API GraphQL queries (buyer-facing), Customer Account API (2024+ replacement for customer auth), cart management via CartProvider and useCart, products/collections/cart/checkout loaders, i18n markets and currencies, caching strategies (CacheShort/CacheLong/CacheCustom), SEO with remix-oxygen meta, analytics integration, and Shopify CDN image optimization. Use when building or maintaining Hydrogen storefronts: React components consuming the Storefront API, Remix loaders/actions for product/collection/cart routes, Oxygen deployment configuration, i18n setup, or migration from Liquid themes to headless. Differentiates from atum-stack-web Next.js generic patterns by covering Shopify-specific primitives (Storefront API, cart mutations, Customer Account API, Oxygen edge caching) and from shopify-liquid-patterns (server-side Liquid templating).

Shopify Online Store 2.0 Liquid theming pattern library — JSON templates with sections and blocks, section schema (settings, blocks, presets, enabled_on), metafields UI exposure, global section groups (header/footer), Liquid filters (money, image_url, handleize, date, t for i18n), responsive images via image_url and image_tag, locales/*.json translations, settings_schema.json for theme settings, and Theme Check compliance. Use when building or maintaining Shopify OS 2.0 themes: writing sections, blocks, snippets, templates, settings schemas, or translations. Complements agent shopify-expert with copy-pasteable Liquid patterns. Differentiates from shopify-hydrogen-patterns (headless React) and wordpress-patterns (different CMS).

WooCommerce 8+ pattern library for WordPress e-commerce — custom product types (WC_Product extensions), cart and checkout hooks (woocommerce_before_cart, woocommerce_checkout_fields, woocommerce_checkout_process), custom shipping methods (WC_Shipping_Method subclasses), custom payment gateways (WC_Payment_Gateway with PSD2/SCA compliance), REST API v3 endpoints and Store API v1 (headless-ready), webhooks, metadata and order meta, High-Performance Order Storage (HPOS) compatibility declaration (Automattic WooCommerce FeaturesUtil::declare_compatibility), and integration with block themes via WooCommerce Blocks. Use whenever building or maintaining a WooCommerce store: custom products, checkout extensions, payment gateways, shipping methods, REST API consumers, HPOS migration, or Gutenberg product block customization. Differentiates from wordpress-patterns by covering only the commerce-specific layer of WordPress — products, carts, orders, payments, shipping. Companion to wordpress-expert agent for WooCommerce-heavy projects.

WordPress 6.x pattern library — block themes with theme.json and Full Site Editing, classic theme template hierarchy, custom plugin structure, Gutenberg custom blocks (block.json + JSX) and dynamic blocks (PHP render_callback), ACF field groups and ACF Blocks, WP-CLI custom commands, REST API endpoint registration with nonce + capability + kses sanitization, custom post types with show_in_rest, multisite switching, cron scheduling via wp_schedule_event, dbDelta schema migrations, and the full WordPress security checklist (nonces, capabilities, sanitization, escaping, i18n). Use whenever you write or review WordPress code — themes, plugins, blocks, REST endpoints, CLI scripts. Differentiates from atum-stack-backend generic PHP patterns by covering the WordPress-specific API surface that no generic PHP skill knows.