← 42flows

Platform capability matrix

Use this page to pick the right website connection. It is written in customer-facing terms: what you connect, what 42flows can publish, and what your website still owns.

Quick comparison

Website pathSetupNew contentExisting pagesBest fit
WordPressWordPress publishing access and 42flows companion plugins where needed.Posts with body, SEO fields, schema, category, and optional image.Strong support for Page Optimizer on WordPress pages and posts.WordPress sites that want publishing and in-place improvements.
ShopifyShopify store connection.Shopify blog articles with SEO fields, tags, body, and optional image.Use Shopify admin/theme workflows for existing-page changes.Stores that use Shopify's blog for SEO articles.
GitHub/Nuxt ContentGitHub App access to the repo and branch.Markdown files and optional assets committed to the repo.Good when the existing page is a markdown file.Nuxt Content and other file-backed sites.
Nuxt direct receiver@42flowsdotcom/nuxt-content package and a receiver token.Content sent to the receiver endpoint.Depends on how the receiver stores and renders content.Self-hosted Nuxt sites that want direct delivery.
Universal webhookOne HTTPS endpoint and bearer token.Markdown, HTML, metadata, schema data, and slug sent to your app.Your app owns existing-page edits.Next.js, Astro, SvelteKit, Rails, Laravel, Django, and custom CMS sites.

WordPress

WordPress is the most complete website path because it has a stable publishing API and a mature plugin layer.

42flows can:

  • Publish posts.
  • Set titles, body content, categories, and featured images.
  • Work with common SEO plugin fields.
  • Add 42flows metadata needed for verification.
  • Read pages/posts for Page Optimizer.
  • Apply targeted improvements where the page structure supports them.
  • Restore a saved WordPress snapshot after a Page Optimizer apply.

Start with the WordPress setup guides and the WordPress publishing feature page.

Shopify

Shopify is the right path when the store uses a Shopify blog for SEO content.

42flows can publish a blog article with:

  • Title.
  • Body HTML.
  • Summary.
  • Tags.
  • SEO title and description.
  • Optional featured image.

Your Shopify theme controls how the article looks on the public site. If the store is headless or stores content somewhere outside Shopify's blog, use the universal webhook instead.

Read the standalone Shopify publishing setup.

GitHub and Nuxt Content

Use GitHub-backed delivery when content lives as files and your deploy pipeline turns those files into pages.

42flows can:

  • Inspect the repo enough to find the content folder and route shape.
  • Commit a markdown article file.
  • Commit optional article assets.
  • Let the customer's normal deploy pipeline publish the page.
  • Verify the public URL after deployment.

For Nuxt, start with the Nuxt setup guides, Connect your Nuxt site via the GitHub App, and GitHub and Nuxt Content integration.

Nuxt direct receiver

The Nuxt receiver is useful when the site can accept content directly instead of receiving Git commits.

The customer installs:

npm install @42flowsdotcom/nuxt-content

The site then exposes a health check and a content receiver endpoint protected by a bearer token. This is best for Nuxt sites where the customer controls the server/runtime and wants direct delivery.

Universal webhook

The webhook is the cleanest path for custom apps.

42flows sends the article payload. Your app:

  1. Verifies the bearer token.
  2. Accepts the ping test.
  3. Saves or updates the article by slug.
  4. Triggers revalidation, cache purge, or build work if needed.
  5. Returns the public postUrl.

The key guidance is simple: make the handler idempotent by article.slug. If 42flows sends the same article again, your app should update the existing article rather than create a duplicate.

Read the universal webhook integration.

Which one should I choose?

If this is trueChoose
The site is WordPress and the customer wants 42flows to publish posts.WordPress
The site is a Shopify store with a blog.Shopify
The site is Nuxt Content or another file-backed site deployed from GitHub.GitHub/Nuxt Content
The site is Nuxt and wants direct API delivery.Nuxt direct receiver
The site is Next.js or any custom app with its own content model.Universal webhook

The safest choice is the one that matches how the website already publishes content.