stage → production: Culture Cares landing + kaya's August batch (Duda, Webflow, nonprofit RFP, contact-us padding) - #98
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.
…-> 6.156rem) Kaya (2026-08-30). Scoped to /contact-us/ only; sitewide nav margin unchanged. Mobile 41px -> 37px, desktop 109px -> 99px.
contact-us: -10% top section padding (kaya)
Nonprofit variant of the website RFP template per kaya's brief (2026-08-30).
New page:
- Same hero + form + informational structure as /website-redesign-rfp-template.html
- Copy nonprofit-specific: chapter/affiliate governance, volunteer editor
permissions, WCAG accessibility, donations + AMS integration angles
- Form is 4 fields (was 2 on generic): first name, email, organization name,
organization type dropdown (Charity or foundation / Trade or professional
association / Multi-chapter or federated network / Other). Routes to same
Zoho endpoint (ContentOneContentDownload) with a distinct zf_referrer_name
('Nonprofit Website RFP Template') so submissions segment automatically.
Org type dropdown posts as 'Dropdown' field — flag: Zoho schema needs a
Dropdown field defined; if it isn't, either add it or provision a
dedicated nonprofit form endpoint (noted in PR body).
- Footer CTA anchors to #rfp-form rather than linking a public file — the
entire gate depends on submission
- Variant switcher below hero + reciprocal small link on generic page
Fix to generic page (kaya explicitly flagged):
- The generic RFP page's Footer CTA linked directly to the public Google
Doc, bypassing the Zoho gate entirely. Replaced with anchor to #rfp-form.
- Added subtle cross-link to the new nonprofit variant.
Sitemap: added /nonprofit-website-rfp-template.html row.
Build /nonprofit-website-rfp-template.html + fix generic RFP gate bypass
Build /duda-vs-content-one.html versus landing
…ed on stage after #92 Duda) Identical intent to closed PR #94, rebuilt on top of latest stage after PR #92 (Duda) landed and created merge conflicts on the shared 'Compare Content.One' footer nav across all Vs pages. Same page + copy verbatim from kaya's brief (2026-08-30). Same Webflow-added-to-footer patch, this time also applied to the newly-live Duda page so all 10 Vs pages cross-link to each other consistently. Sitemap: /webflow-vs-content-one.html row added.
Build /webflow-vs-content-one.html versus landing (was #94)
Culture Cares Podcast x Content.One nonprofit-focused campaign page per sam's brief (2026-08-31). Structure: - Hero (above-the-fold listener-exclusive benefits card with 5-item bullet list, warm-accent border to signal exclusivity, primary royal CTA to /contact-us/?ref=culture-cares, editorial visual on desktop naming real nonprofit customers/partners) - Listener-exclusive offer section (3 detailed cards: consultation, AI visibility audit, complimentary migration) with reinforcing CTA - Why this matters (4 nonprofit-website-value cards: discovery, trust, action, AI/traditional search) with reinforcing CTA - CauseCircle section: visually differentiated per sam's brief - warm- bordered card on soft gradient, outline-style secondary CTA (not primary royal fill), external link to www.causecircle.org with rel='noopener noreferrer' - Final CTA on dark royal gradient with warm glow accent All primary CTAs anchor to /contact-us/?ref=culture-cares for attribution. Secondary CauseCircle CTA points external. Placeholder: CauseCircle mark is an editorial glyph until the official SVG is supplied - flagged as a follow-up in PR body. Sitemap: added /culture-cares.html row.
…ntact-form Per sam's follow-up (2026-08-31) - include the demo form directly in the landing rather than routing to /contact-us/. Reuses the sitewide ContentOneDemoForm Zoho endpoint (same one the /contact-us/ page uses) with a distinct zf_referrer_name value 'culture-cares-landing' so submissions segment cleanly for campaign attribution. - Final CTA section restructured: same H2/subhead copy, form embedded directly below on the dark royal gradient in a translucent white card. id='contact-form' anchor target. - 4 primary CTAs now anchor to #contact-form (hero, section 2, section 3, nav 'Book a demo' pill) - CauseCircle CTA still external to www.causecircle.org (unchanged) - Footer 'Contact' link kept pointing at /contact-us/ (sitewide chrome) - Zoho fields (Name_First, Name_Last, Email, SingleLine, MultiLine) match the schema verbatim - do not rename or values drop silently - On submit, Zoho redirects to /thank-you/?type=demo (existing pattern)
…by' social proof strip
Per sam (2026-08-31):
1. Hero image: replaced the editorial gradient card on the right column
with the supplied Culture-Cares.jpg. Wrapped in rounded-3xl w/ ring +
warm-accent glow behind for continuity with the listener-exclusive
visual language. eager-load + fetchpriority=high since it's LCP.
2. Social proof section added between hero and Listener-Exclusive Offer.
Title matches sam's ask verbatim ('Trusted by leading enterprises and
nonprofits'). Uses the same grayscale+opacity+hover pattern as the
sitewide /-/block/client_logos.html but hardcoded here so we can
control the title and the enterprise/nonprofit mix.
Logos (3 enterprise + 3 nonprofit, balanced):
- Enterprise: Sony, Singlife, Wattpad (reused from contact-us Trusted-by)
- Nonprofit: Adjoin, AFP, Nonprofit Storytelling Conference (reused from DEI page)
Enterprise SVGs get the brightness(0)+opacity treatment since they're
originally reversed-white marks that need to render as dark on the
light strip.
Per sam (2026-08-31): The Salvation Army, Sony, Phoenix Suns, kin, wattpad, Singlife. To be reused as the default marketing-page customer lineup unless a specific ask says otherwise. - Dark bg (ink) so the reversed-white SVGs read cleanly alongside the colored marks (Phoenix Suns purple/orange, wattpad orange) - Tagline kept as 'Trusted by leading enterprises and nonprofits' from sam's earlier ask (his reference screenshot uses a different tagline but the logo mix is the point of this update) - Each logo sized to its own natural aspect (Sony/kin/Singlife wordmarks smaller h-6/7, Salvation Army/Phoenix Suns badges h-10/12, wattpad h-7/8) so no logo dominates the row Salvation Army: using the_salvation_army_reversed.svg (white on dark) since a colored red-shield SVG isn't on Zesty CDN. If sam wants the red version, drop the asset URL and I'll swap.
Build /culture-cares.html landing page for sam
Contributor
🚀 Production publish preview (publish-only)Will publish — promote dev → live (0): Already live, skipped: 5
192 mapped resources · publish-only · 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
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.
Promoting stage → production per ardeay's Discord (2026-09-02):
"please send this to stage and the prod #97"
Note on request
PR #97 (Culture Cares) was already merged to stage on 2026-08-31 via commit 29677d8. This PR completes the second half of the request — pushing stage to production. That promotion carries #97 plus every other PR sitting in stage.
Scope — 5 PRs in this batch
/culture-cares.html) with embedded demo form + "Trusted by" social proof strip/nonprofit-website-rfp-template.html) + fix on generic RFP page's Google Doc gate bypassAfter merge
Same standing manual step as prior standalone HTML pages. Sam/kaya need to create these view records in the Zesty editor and drop the ZUIDs so I can wire the sync-to-zesty mappings:
culture-cares.htmlnonprofit-website-rfp-template.htmlduda-vs-content-one.htmlwebflow-vs-content-one.html(Duda + Webflow have been in stage since 2026-08-31 so may already be set up — worth double-checking.)
Sanity checks after CI
/contact-us/top padding tightens on desktop (~109px → ~99px)/culture-cares.html,/nonprofit-website-rfp-template.html,/duda-vs-content-one.html,/webflow-vs-content-one.htmlall load 200