Build /duda-vs-content-one.html versus landing - #92
Merged
Merged
Conversation
- Standalone HTML page following the same 7-section template as the other 8 Vs pages (hero, reviews, at-a-glance, comparison table, body, FAQ, CTA + cross-link footer) - Copy verbatim from kaya's brief (2026-08-30) - Positioning: Duda as reseller-model website builder for agencies, Content.One as federated multisite for organizations that own their properties. Pricing analysis at 80 sites, MCP terms, migration path, team-seat cap. When-Duda-wins section preserves fairness (small networks, transparent pricing, agency white-label) - G2 reviews cards: Content.One 4.6/36, Duda 4.6/~780 - Internal cross-links to /solutions/federated-multisite/ + 2 blog posts per kaya's link plan Also updated the 'Compare Content.One' footer nav on all 8 existing Vs pages to include Duda (inserted between Optimizely and Blog). Sitemap: added /duda-vs-content-one.html row per sitemap-coverage convention.
Contributor
💾 Stage sync previewNew files to create (6):
Will add/update — differ from dev (3):
Unchanged, skipped: 0 192 mapped resources · zesty-sync |
5 tasks
This was referenced Aug 31, 2026
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
1 participant
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
9th Vs page: Duda vs Content.One, following the same 7-section template as the other 8. Copy verbatim from kaya's brief (2026-08-30).
Positioning angle: Duda as reseller-model website builder for agencies/SaaS/hosts (transparent pricing, per-site economics, white-label layer); Content.One as federated multisite for organizations that own their properties (shared content model, network-wide publish, role-based governance).
Sections
Also patched: cross-link footer on all 8 existing Vs pages
Inserted Duda link between Optimizely and Blog on: contentful, drupal, sanity, sitecore, storyblok, contentstack, adobe-experience-manager, optimizely. Every Vs page now cross-links to the other 8 + blog.
Sitemap
Added
/duda-vs-content-one.htmlrow towebengine/views/sitemap.xml.Internal cross-links (per kaya's brief)
/solutions/federated-multisite/(verified live)/blog/federated-multisite-cms-manage-100plus-websites-from-one-platform/(verified live)/blog/why-content-operations-break-in-multilocation-businesses-and-what-to-fix-first/(verified live)Deferred cross-links flagged in kaya's brief (not-yet-live pages):
/blog/duda-alternatives— will add once the blog post ships/cms-for-multi-location-businesses/— will add once the industries page shipsCaveats from kaya's production notes
Preview
https://hj5v68xn-kaya-duda-vs-page.webengine.zesty.io/duda-vs-content-one.html?zpw=bobby
duda-vs-content-one.html(same manual step as prior standalones — 5 unmapped Vs pages already share this pattern). Drop the ZUID once created and I'll wire it intozesty.config.jsonso sync-to-zesty starts PUTting our version.Test plan