Skip to content

Vs pages Phase 3 — customer proof, pricing slot, three-way, related reading - #105

Merged
ardeay merged 1 commit into
stagefrom
kaya-vs-pages-phase3
Sep 11, 2026
Merged

ardeay merged 1 commit into
stagefrom
kaya-vs-pages-phase3

Conversation

@ardeay

@ardeay ardeay commented Sep 11, 2026

Copy link
Copy Markdown
Contributor

Phase 3 wraps kaya's 2026-09-10 vs pages brief. 4 new sections injected on all 10 vs pages via a script with per-page config (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 for 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. Awaits Wordify copy.

3. Three-way comparisons — 3 cards + full-width card (brief #5b + kaya's Discord)

  • 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 page: 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, styled as a 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, awaits content)
  • Wordify copy for individual three-way card descriptions (currently uses a generic 'See how X stacks up against Content.One' — swap in when specific copy arrives)
  • Reverse-links in the 9 alternatives blog posts (content-edit workflow, parallel deliverable)
  • Zesty-side sitemap serving fix (ardeay)

Preview

Any vs page — sections all consistent:

Sanity checks

  • All 10 pages show Customer proof block (3 correct customer logos per page)
  • All 10 show empty Pricing slot placeholder
  • All 10 show 3 sibling cards + Content.One full-width card in Three-way section
  • All 10 show 5-link Related reading block with the correct per-page alternatives link

…d reading (kaya SEO brief)

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)
@github-actions

Copy link
Copy Markdown
Contributor

💾 Stage sync preview

New files to create (0):
none

Will add/update — differ from dev (10):

  • webengine/views/drupal-vs-content-one.html
  • webengine/views/sanity-vs-content-one.html
  • webengine/views/optimizely-vs-content-one.html
  • webengine/views/duda-vs-content-one.html
  • webengine/views/webflow-vs-content-one.html
  • webengine/views/adobe-experience-manager-vs-content-one.html
  • webengine/views/contentful-vs-content-one.html
  • webengine/views/contentstack-vs-content-one.html
  • webengine/views/sitecore-vs-content-one.html
  • webengine/views/storyblok-vs-content-one.html

Unchanged, skipped: 0

205 mapped resources · zesty-sync

@ardeay
ardeay merged commit 4c641bd into stage Sep 11, 2026
4 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant