From e4298fe996b6f30048516b3717ac70962c3efe48 Mon Sep 17 00:00:00 2001 From: ContentOneBot Date: Fri, 11 Sep 2026 02:02:17 -0400 Subject: [PATCH] =?UTF-8?q?Vs=20pages=20Phase=203=20=E2=80=94=20customer?= =?UTF-8?q?=20proof=20+=20pricing=20slot=20+=20three-way=20+=20related=20r?= =?UTF-8?q?eading=20(kaya=20SEO=20brief)?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Phase 3 wraps kaya's 2026-09-10 vs pages brief. Four new sections injected on all 10 vs pages via a script, using per-page config for competitor name, alternatives blog post, sibling comparisons, and customer logos. ## New sections per page (top → bottom, injected right after the comparison table) 1. Customer proof (brief #2d) 3 customer logo cards linking to case studies. Per-page mapping from kaya's brief: - Enterprise DXP (AEM/Sitecore/Optimizely/Drupal): Salvation Army, Sony, Singlife - Headless (Contentful/Sanity/Contentstack/Storyblok): Sony, Rocket League, Wattpad - Website builders (Webflow/Duda): Salvation Army, PetDesk, Jackpocket Reversed-white logos get brightness(0)+opacity treatment to read on the light card bg; colored logos render as-is. 2. Pricing H2 slot (brief #5a) 'Competitor pricing in 2026' H2 + 'Pricing detail coming soon.' placeholder. Awaiting Wordify copy. 3. Three-way comparisons — 3 cards + full-width card (brief #5b + kaya's Discord clarification) Header: 'How [Competitor] compares to other options' 3 sibling cards linking to same-category vs-Content.One pages with 'X vs [current-competitor]' framing (e.g. on Sitecore: AEM vs Sitecore, Optimizely vs Sitecore, Drupal vs Sitecore) Full-width Content.One positioning card underneath (dark royal gradient) with dual CTA: 'Start a Content.One build' + 'Get a migration estimate' 4. Related reading (brief #2b) 5 links, per kaya's spec: - Federated multisite CMS → /solutions/federated-multisite/ - GEO and SEO features → /features/geo-and-seo/ - Content.One MCP server → /ai-mcp-server/ - CMS migration guide → /blog/cms-migration-guide-... - The matching alternatives blog post (per-page, highlighted as full-width royal-tinted card since it's the specific-to-this-competitor reference) ## Sibling mapping for three-way section contentful → sanity, storyblok, contentstack sanity → contentful, storyblok, contentstack storyblok → contentful, sanity, contentstack contentstack→ contentful, sanity, storyblok sitecore → aem, optimizely, drupal aem → sitecore, optimizely, drupal optimizely → sitecore, aem, drupal drupal → sitecore, aem, optimizely webflow → duda, contentful, sanity duda → webflow, contentful, sanity Not in this PR: - Wordify copy for pricing sections (slots ready, awaiting content) - Wordify copy for individual three-way paragraphs (kaya's original brief mentioned Sitecore vs AEM, Sitecore vs Drupal, AEM vs WordPress, etc. — those specific pairings can drop into the cards' description slot when the copy arrives) - Reverse-links in the 9 alternatives blog posts (content-edit workflow, parallel deliverable) - Zesty-side sitemap serving fix (ardeay) --- ...obe-experience-manager-vs-content-one.html | 139 ++++++++++++++++++ .../views/contentful-vs-content-one.html | 139 ++++++++++++++++++ .../views/contentstack-vs-content-one.html | 139 ++++++++++++++++++ webengine/views/drupal-vs-content-one.html | 139 ++++++++++++++++++ webengine/views/duda-vs-content-one.html | 139 ++++++++++++++++++ .../views/optimizely-vs-content-one.html | 139 ++++++++++++++++++ webengine/views/sanity-vs-content-one.html | 139 ++++++++++++++++++ webengine/views/sitecore-vs-content-one.html | 139 ++++++++++++++++++ webengine/views/storyblok-vs-content-one.html | 139 ++++++++++++++++++ webengine/views/webflow-vs-content-one.html | 139 ++++++++++++++++++ 10 files changed, 1390 insertions(+) diff --git a/webengine/views/adobe-experience-manager-vs-content-one.html b/webengine/views/adobe-experience-manager-vs-content-one.html index fb8a8dc..ad12315 100644 --- a/webengine/views/adobe-experience-manager-vs-content-one.html +++ b/webengine/views/adobe-experience-manager-vs-content-one.html @@ -386,6 +386,99 @@

The comparison

Accurate as of September 2026.

+ +
+
+
+

Who runs on Content.One

+

Real customers, real deployments.

+
+ +
+
+ + +
+
+

Adobe Experience Manager pricing in 2026

+

Pricing detail coming soon.

+
+
+ + +
+
+
+

How AEM compares to other options

+

If AEM is on your shortlist, these usually are too. Content.One is the reference point across all three.

+
+ + + +
+
+
+

Why teams choose Content.One over all of these

+

Federated multisite, marketer-led publishing, and included AI — as the platform, not add-ons.

+

Whichever of the above you were considering, Content.One replaces per-property licenses, agency-mediated migrations, and credit-based AI billing with one instance-based subscription. See the specifics in the comparison above, or start a build to see the network shape yourself.

+
+ +
+
+
+
+
@@ -462,6 +555,52 @@

Frequently asked qu

+ + +
+ +
+
diff --git a/webengine/views/contentful-vs-content-one.html b/webengine/views/contentful-vs-content-one.html index 064cedf..d1e23aa 100644 --- a/webengine/views/contentful-vs-content-one.html +++ b/webengine/views/contentful-vs-content-one.html @@ -379,6 +379,99 @@

The comparison

Accurate as of September 2026.

+ +
+
+
+

Who runs on Content.One

+

Real customers, real deployments.

+
+ +
+
+ + +
+
+

Contentful pricing in 2026

+

Pricing detail coming soon.

+
+
+ + +
+
+
+

How Contentful compares to other options

+

If Contentful is on your shortlist, these usually are too. Content.One is the reference point across all three.

+
+ + + +
+
+
+

Why teams choose Content.One over all of these

+

Federated multisite, marketer-led publishing, and included AI — as the platform, not add-ons.

+

Whichever of the above you were considering, Content.One replaces per-property licenses, agency-mediated migrations, and credit-based AI billing with one instance-based subscription. See the specifics in the comparison above, or start a build to see the network shape yourself.

+
+ +
+
+
+
+
@@ -462,6 +555,52 @@

Frequently asked qu

+ + +
+ +
+
diff --git a/webengine/views/contentstack-vs-content-one.html b/webengine/views/contentstack-vs-content-one.html index ad3e54f..529de18 100644 --- a/webengine/views/contentstack-vs-content-one.html +++ b/webengine/views/contentstack-vs-content-one.html @@ -392,6 +392,99 @@

The comparison

Accurate as of September 2026.

+ +
+
+
+

Who runs on Content.One

+

Real customers, real deployments.

+
+ +
+
+ + +
+
+

Contentstack pricing in 2026

+

Pricing detail coming soon.

+
+
+ + +
+
+
+

How Contentstack compares to other options

+

If Contentstack is on your shortlist, these usually are too. Content.One is the reference point across all three.

+
+ + + +
+
+
+

Why teams choose Content.One over all of these

+

Federated multisite, marketer-led publishing, and included AI — as the platform, not add-ons.

+

Whichever of the above you were considering, Content.One replaces per-property licenses, agency-mediated migrations, and credit-based AI billing with one instance-based subscription. See the specifics in the comparison above, or start a build to see the network shape yourself.

+
+ +
+
+
+
+
@@ -481,6 +574,52 @@

Frequently asked qu

+ + +
+ +
+
diff --git a/webengine/views/drupal-vs-content-one.html b/webengine/views/drupal-vs-content-one.html index edbe89b..9b11d0f 100644 --- a/webengine/views/drupal-vs-content-one.html +++ b/webengine/views/drupal-vs-content-one.html @@ -389,6 +389,99 @@

The comparison

Accurate as of September 2026.

+ +
+
+
+

Who runs on Content.One

+

Real customers, real deployments.

+
+ +
+
+ + +
+
+

Drupal pricing in 2026

+

Pricing detail coming soon.

+
+
+ + +
+
+
+

How Drupal compares to other options

+

If Drupal is on your shortlist, these usually are too. Content.One is the reference point across all three.

+
+ + + +
+
+
+

Why teams choose Content.One over all of these

+

Federated multisite, marketer-led publishing, and included AI — as the platform, not add-ons.

+

Whichever of the above you were considering, Content.One replaces per-property licenses, agency-mediated migrations, and credit-based AI billing with one instance-based subscription. See the specifics in the comparison above, or start a build to see the network shape yourself.

+
+ +
+
+
+
+
@@ -478,6 +571,52 @@

Frequently asked qu

+ + +
+ +
+
diff --git a/webengine/views/duda-vs-content-one.html b/webengine/views/duda-vs-content-one.html index 79d7284..2446cc2 100644 --- a/webengine/views/duda-vs-content-one.html +++ b/webengine/views/duda-vs-content-one.html @@ -382,6 +382,99 @@

The comparison

Accurate as of September 2026.

+ +
+
+
+

Who runs on Content.One

+

Real customers, real deployments.

+
+ +
+
+ + +
+
+

Duda pricing in 2026

+

Pricing detail coming soon.

+
+
+ + +
+
+
+

How Duda compares to other options

+

If Duda is on your shortlist, these usually are too. Content.One is the reference point across all three.

+
+ + + +
+
+
+

Why teams choose Content.One over all of these

+

Federated multisite, marketer-led publishing, and included AI — as the platform, not add-ons.

+

Whichever of the above you were considering, Content.One replaces per-property licenses, agency-mediated migrations, and credit-based AI billing with one instance-based subscription. See the specifics in the comparison above, or start a build to see the network shape yourself.

+
+ +
+
+
+
+
@@ -466,6 +559,52 @@

Frequently asked qu

+ + +
+ +
+
diff --git a/webengine/views/optimizely-vs-content-one.html b/webengine/views/optimizely-vs-content-one.html index 6deac91..d1c6ea8 100644 --- a/webengine/views/optimizely-vs-content-one.html +++ b/webengine/views/optimizely-vs-content-one.html @@ -370,6 +370,99 @@

The comparison

Accurate as of September 2026.

+ +
+
+
+

Who runs on Content.One

+

Real customers, real deployments.

+
+ +
+
+ + +
+
+

Optimizely pricing in 2026

+

Pricing detail coming soon.

+
+
+ + +
+
+
+

How Optimizely compares to other options

+

If Optimizely is on your shortlist, these usually are too. Content.One is the reference point across all three.

+
+ + + +
+
+
+

Why teams choose Content.One over all of these

+

Federated multisite, marketer-led publishing, and included AI — as the platform, not add-ons.

+

Whichever of the above you were considering, Content.One replaces per-property licenses, agency-mediated migrations, and credit-based AI billing with one instance-based subscription. See the specifics in the comparison above, or start a build to see the network shape yourself.

+
+ +
+
+
+
+
@@ -445,6 +538,52 @@

Frequently asked qu

+ + +
+ +
+
diff --git a/webengine/views/sanity-vs-content-one.html b/webengine/views/sanity-vs-content-one.html index ae4457c..e3b9c32 100644 --- a/webengine/views/sanity-vs-content-one.html +++ b/webengine/views/sanity-vs-content-one.html @@ -388,6 +388,99 @@

The comparison

Accurate as of September 2026.

+ +
+
+
+

Who runs on Content.One

+

Real customers, real deployments.

+
+ +
+
+ + +
+
+

Sanity pricing in 2026

+

Pricing detail coming soon.

+
+
+ + +
+
+
+

How Sanity compares to other options

+

If Sanity is on your shortlist, these usually are too. Content.One is the reference point across all three.

+
+ + + +
+
+
+

Why teams choose Content.One over all of these

+

Federated multisite, marketer-led publishing, and included AI — as the platform, not add-ons.

+

Whichever of the above you were considering, Content.One replaces per-property licenses, agency-mediated migrations, and credit-based AI billing with one instance-based subscription. See the specifics in the comparison above, or start a build to see the network shape yourself.

+
+ +
+
+
+
+
@@ -477,6 +570,52 @@

Frequently asked qu

+ + +
+ +
+
diff --git a/webengine/views/sitecore-vs-content-one.html b/webengine/views/sitecore-vs-content-one.html index 866d09b..b4c5af6 100644 --- a/webengine/views/sitecore-vs-content-one.html +++ b/webengine/views/sitecore-vs-content-one.html @@ -392,6 +392,99 @@

The comparison

Accurate as of September 2026.

+ +
+
+
+

Who runs on Content.One

+

Real customers, real deployments.

+
+ +
+
+ + +
+
+

Sitecore pricing in 2026

+

Pricing detail coming soon.

+
+
+ + +
+
+
+

How Sitecore compares to other options

+

If Sitecore is on your shortlist, these usually are too. Content.One is the reference point across all three.

+
+ + + +
+
+
+

Why teams choose Content.One over all of these

+

Federated multisite, marketer-led publishing, and included AI — as the platform, not add-ons.

+

Whichever of the above you were considering, Content.One replaces per-property licenses, agency-mediated migrations, and credit-based AI billing with one instance-based subscription. See the specifics in the comparison above, or start a build to see the network shape yourself.

+
+ +
+
+
+
+
@@ -481,6 +574,52 @@

Frequently asked qu

+ + +
+ +
+
diff --git a/webengine/views/storyblok-vs-content-one.html b/webengine/views/storyblok-vs-content-one.html index f641c01..e3520e0 100644 --- a/webengine/views/storyblok-vs-content-one.html +++ b/webengine/views/storyblok-vs-content-one.html @@ -369,6 +369,99 @@

The comparison

Accurate as of September 2026.

+ +
+
+
+

Who runs on Content.One

+

Real customers, real deployments.

+
+ +
+
+ + +
+
+

Storyblok pricing in 2026

+

Pricing detail coming soon.

+
+
+ + +
+
+
+

How Storyblok compares to other options

+

If Storyblok is on your shortlist, these usually are too. Content.One is the reference point across all three.

+
+ + + +
+
+
+

Why teams choose Content.One over all of these

+

Federated multisite, marketer-led publishing, and included AI — as the platform, not add-ons.

+

Whichever of the above you were considering, Content.One replaces per-property licenses, agency-mediated migrations, and credit-based AI billing with one instance-based subscription. See the specifics in the comparison above, or start a build to see the network shape yourself.

+
+ +
+
+
+
+
@@ -444,6 +537,52 @@

Frequently asked qu

+ + +
+ +
+
diff --git a/webengine/views/webflow-vs-content-one.html b/webengine/views/webflow-vs-content-one.html index 8f45e80..b87589b 100644 --- a/webengine/views/webflow-vs-content-one.html +++ b/webengine/views/webflow-vs-content-one.html @@ -384,6 +384,99 @@

The comparison

Accurate as of September 2026.

+ +
+
+
+

Who runs on Content.One

+

Real customers, real deployments.

+
+ +
+
+ + +
+
+

Webflow pricing in 2026

+

Pricing detail coming soon.

+
+
+ + +
+
+
+

How Webflow compares to other options

+

If Webflow is on your shortlist, these usually are too. Content.One is the reference point across all three.

+
+ + + +
+
+
+

Why teams choose Content.One over all of these

+

Federated multisite, marketer-led publishing, and included AI — as the platform, not add-ons.

+

Whichever of the above you were considering, Content.One replaces per-property licenses, agency-mediated migrations, and credit-based AI billing with one instance-based subscription. See the specifics in the comparison above, or start a build to see the network shape yourself.

+
+ +
+
+
+
+
@@ -468,6 +561,52 @@

Frequently asked qu

+ + +
+ +
+