Skip to content

Build /webflow-vs-content-one.html versus landing - #94

Closed
ardeay wants to merge 2 commits into
stagefrom
kaya-webflow-vs-page
Closed

ardeay wants to merge 2 commits into
stagefrom
kaya-webflow-vs-page

Conversation

@ardeay

@ardeay ardeay commented Aug 30, 2026

Copy link
Copy Markdown
Contributor

Summary

10th Vs page: Webflow vs Content.One. Same 7-section template as prior Vs pages. Copy verbatim from kaya's brief (2026-08-30).

Positioning angle: Webflow as design-led per-site platform (Designer, hosting, developer surface, MCP 2.0 all genuinely strong). Content.One as federated multisite for organizations governing 80+ owned properties. Argues on architecture and cost curve rather than AI/MCP — Webflow's July 2026 MCP 2.0 launch is credited openly rather than contested. Same integrity call kaya made on the Sanity page.

Sections

  • Hero (dark gradient, launch + migration CTAs, cost anchor: 80 Premium sites ≈ $24k/yr in plans alone)
  • G2 reviews (Content.One 4.6/36 vs Webflow 4.4/~975)
  • 4-card At a glance: per-site pricing, three-layer pricing model, site-scoped Collections, MCP parity
  • Full capability comparison table across 5 buckets (fit, pricing, editorial, AI/agents, platform)
  • Body: per-site-vs-network positioning + "Where Content.One takes the lead"
  • When Webflow wins (design control, single site, dev-heavy work, agent-heavy workflows)
  • 7-question FAQ (50/100-site cost math, multisite support, network-wide publish, MCP, May 2026 pricing changes, Zesty rebrand, migration path)
  • CTA

Also patched: cross-link footer on all 8 stage-live Vs pages

Inserted Webflow link before Blog on: contentful, drupal, sanity, sitecore, storyblok, contentstack, adobe-experience-manager, optimizely.

Note on Duda: PR #92 (kaya-duda-vs-page) is still open. When Duda merges to stage first, I'll add Webflow to its footer in a small follow-up. If Webflow merges first, the Duda branch already needs a Webflow addition before merge. Either way — trivially resolvable, just flagging the sequencing.

Sitemap

Added /webflow-vs-content-one.html row.

Internal cross-links (per kaya's brief, all verified live)

  • /solutions/federated-multisite/
  • /blog/federated-multisite-cms-manage-100plus-websites-from-one-platform/
  • /blog/why-content-operations-break-in-multilocation-businesses-and-what-to-fix-first/

Deferred cross-link from brief: /blog/webflow-alternatives — kaya to confirm URL before publish, will patch in later.

Caveats from kaya's production notes

  • Webflow's May 2026 pricing (Basic $15, Premium $25 yearly, 20k CMS items, 50GB bandwidth) verified 2026-08-30
  • Workspace seat pricing described structurally, not numerically — kaya's brief flagged that Core/Growth figures come from secondary breakdowns rather than webflow.com/pricing directly. Skipped explicit dollar figures on seats
  • One row flagged in brief for confirmation: "Editing runs through the Designer since the legacy Editor was deprecated" — deprecation is confirmed but exact replacement UX for non-designer editors wasn't verified end-to-end. Copy is defensible as written but soften-able if a Webflow reviewer pushes back
  • Deliberately not claimed: Webflow lacks MCP/AI/localization/SSO/API — it has all of them, several well

Preview

https://hj5v68xn-kaya-webflow-vs-page.webengine.zesty.io/webflow-vs-content-one.html?zpw=bobby

⚠️ Preview will 404 until a Zesty view record is created for webflow-vs-content-one.html — same standing manual step as prior standalones. Drop the ZUID when ready.

Test plan

  • Webflow rating card shows 4.4/~975 with 4 gold stars + 1 dim
  • All 8 existing Vs pages show Webflow in the "Compare Content.One" footer nav (between Optimizely and Blog)
  • Comparison table scrolls cleanly on mobile
  • FAQ opens/closes; first item open by default
  • Sitemap includes /webflow-vs-content-one.html row

ContentOneBot added 2 commits August 30, 2026 16:11
10th Vs page, same 7-section template. Copy verbatim from kaya's brief (2026-08-30).

Positioning: Webflow as design-led per-site platform (real strengths in
Designer, hosting, developer surface, MCP 2.0), Content.One as
federated multisite for organizations governing 80+ owned properties.
Fair 'When Webflow wins' section credits Webflow's design control,
MCP, and per-site economics for the single-site use case. G2 reviews
card 4.4/~975 vs Content.One 4.6/36.

Also updated the 'Compare Content.One' footer nav on all 8 existing
stage-live Vs pages to include Webflow (contentful, drupal, sanity,
sitecore, storyblok, contentstack, aem, optimizely). Duda page (PR
#92, still open) already gets Webflow added when it merges to stage.

Sitemap: added /webflow-vs-content-one.html row.
@github-actions

Copy link
Copy Markdown
Contributor

💾 Stage sync preview

New files to create (6):

  • 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
  • webengine/views/webflow-vs-content-one.html

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

  • webengine/views/drupal-vs-content-one.html
  • webengine/views/sanity-vs-content-one.html
  • webengine/views/sitemap.xml
  • webengine/views/optimizely-vs-content-one.html

Unchanged, skipped: 0

192 mapped resources · zesty-sync

@ardeay

ardeay commented Aug 31, 2026

Copy link
Copy Markdown
Contributor Author

Superseded by v2 (PR to follow) after PR #92 (Duda) landed and created merge conflicts on the shared 'Compare Content.One' footer nav across all Vs pages. Same intent, rebased on latest stage.

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