Vs pages Phase 3 — customer proof, pricing slot, three-way, related reading - #105
Merged
Merged
Conversation
…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)
Contributor
💾 Stage sync previewNew files to create (0): Will add/update — differ from dev (10):
Unchanged, skipped: 0 205 mapped resources · zesty-sync |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
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:
Reversed-white logos get
brightness(0)+opacitytreatment for the light card bg; colored logos render as-is.2. Pricing H2 slot (brief #5a)
[Competitor] pricing in 2026H2 +Pricing detail coming soon.placeholder. Awaits Wordify copy.3. Three-way comparisons — 3 cards + full-width card (brief #5b + kaya's Discord)
How [Competitor] compares to other optionsX vs [current-competitor]framing (e.g. on Sitecore page: AEM vs Sitecore, Optimizely vs Sitecore, Drupal vs Sitecore)Start a Content.One build+Get a migration estimate4. Related reading (brief #2b)
5 links per kaya's spec:
Sibling mapping for three-way section
Not in this PR
Preview
Any vs page — sections all consistent:
Sanity checks