Conversation
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.
Contributor
💾 Stage sync previewNew files to create (6):
Will add/update — differ from dev (4):
Unchanged, skipped: 0 192 mapped resources · zesty-sync |
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. |
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.
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
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.htmlrow.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
Preview
https://hj5v68xn-kaya-webflow-vs-page.webengine.zesty.io/webflow-vs-content-one.html?zpw=bobby
webflow-vs-content-one.html— same standing manual step as prior standalones. Drop the ZUID when ready.Test plan
openby default