stage → production: DEI landing + sitemap wiring + canonical fixes + Vs parity - #89
Merged
Merged
Conversation
…ith rest) PR #69 only reordered Sitecore + Contentful; Drupal + Sanity still had At-a-glance first. Kaya flagged the mismatch (2026-07-29). This brings all 8 Vs pages to the same section order: Hero → Reviews → At-a-glance → Comparison table → Body → FAQ → CTA. Cross-link footer was already on all 8 (verified: 'Compare Content.One' block present).
Vs pages: reorder Reviews-above-At-a-glance on Drupal + Sanity (parity)
- website-redesign-rfp-template.html: canonical was '/website-redesign-rfp-template/' (trailing slash, no .html) → 404. Now points at the real '.html' URL. - free-tools.html: canonical was '/free-tools' (no extension) → 404. Now points at the real '.html' URL. Full canonical audit of the other 15 public standalone HTML pages: all match their served URL. These 2 were the only mismatches.
Fix canonical URLs on RFP template + free-tools (kaya audit)
Kaya created the sitemap.xml view record in the Zesty editor (2026-08-07) after we established that PR #77 shipped the file to git without an associated Zesty view — sync-to-zesty had no ZUID to PUT to, so prod kept serving Zesty's auto-generated fallback (which misses every standalone HTML page). With this mapping in place, next sync-to-zesty run replaces the auto-gen with our webengine/views/sitemap.xml, so the 15 standalone HTML pages (pricing, free-tools, all 8 Vs pages, MCP press releases, RFP template, bridgetech, why-building-websites-is-still-hard) become discoverable.
Wire /sitemap.xml ZUID (kaya-created view)
DEI & Community Partnership landing per sam's brief (2026-08-09): - Hero: 'More voices. Better systems. Stronger communities.' with dual CTA (invite to speak / request sponsorship) + editorial visual (no stock DEI imagery) - Belief statement: 'Inclusion is something you build.' with scroll-triggered warm-accent highlights on heard/access/act (reduced-motion respected) - Section 3: Content.One + CauseCircle shared commitment (700px max-width per brief; CauseCircle logo asset TBD, wordmark placeholder for now) - Section 4: 3 cards (inside the company, in the product, in the community) with editorial icons — no demographic illustrations - Section 5: Community-in-practice logo wall (Ajoin, Nonprofit Storytelling Conference, AFP, BridgeTech) with relationship-type chips (Sponsor / Community partner / Program supporter) — hard-coded for launch, CMS schema is a follow-up - Section 6: Speaking engagements 2-col with 5-topic list - Section 7: Sponsorship invitation with CTA to /contact-us/?ref=dei-sponsorship - Section 8: Closing dual-CTA on dark gradient - FAQ: 4 questions from brief Design choices per brief: - Brand palette + one warm accent (#D97757, terracotta) used sparingly on eyebrows, highlights, logo strip labels - No rainbow / no demographic stock imagery - WCAG 2.2 AA contrast throughout - prefers-reduced-motion respected on belief-statement animations Follow-ups flagged in PR: - CauseCircle logo asset (placeholder wordmark until sam supplies SVG) - Dedicated Zoho sponsorship-request form with sam's field list (currently routes to /contact-us/?ref=... for triage) - CMS-driven logo-wall schema for the community-in-practice section - Hero editorial image (gradient placeholder until sam supplies an authentic event/team photo) Sitemap: added /dei-community.html row per sitemap-coverage convention.
…ntact-form Per sam's follow-up brief (2026-08-09) — replaces the closing-CTA section with a dark-gradient form section (id=contact-form) housing the Zoho SpeakingEngagementsContentOne form he provided. All page CTAs (hero x2, events section, speaking section, sponsorship section) now anchor to #contact-form instead of routing to /contact-us/?ref=… — form is the single conversion target at the bottom of the page. Form fields match Zoho schema verbatim (SingleLine2 first name*, SingleLine last name*, Email*, SingleLine1 org, Website, MultiLine interest); relabeled 'Describe your interest' textarea placeholder to prompt for event/program/initiative context relevant to DEI-page intent. Referrer tag set to 'dei-community-page' for triage. Nav 'Book a demo' pill + footer 'Contact' link intentionally kept pointing at /contact-us/ — those are sitewide chrome, not DEI-page CTAs. Section order now: Hero → Belief → CauseCircle → 3 cards → Events → Speaking → Sponsorship → FAQ → Contact form (bottom).
…ps to 'Sponsor', drop descriptions Sam supplied logo URLs for the 4 partner orgs (2026-08-10) and asked to drop the wordmark text + normalize every relationship-type chip to 'Sponsor' for a neater look. Also dropped per-card descriptions since he called out cleaner visuals as the goal. Assets wired: - Adjoin: /Adjoin-Logo.webp (also corrected slug 'ajoin' -> 'adjoin' per sam) - Nonprofit Storytelling Conference: /NP-Story-Club-Pro-Image-1600x900-1.png - AFP: /IconLogoNoDate_1000x400.png - BridgeTECH: /BridgeTECH_323.webp Card frame now h-20 (was h-16) to give varied-aspect logos more room. object-contain keeps every logo on a consistent visual baseline regardless of source aspect ratio (Adjoin/BridgeTECH square-ish, NP-Story-Club 16:9, AFP 5:2).
Build /dei-community.html landing page for sam
Merged
3 tasks
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 message (2026-08-10):
"push this into stage and then to prod #88"
Scope — 4 PRs stacked in stage since 2026-07-29
/dei-community.html) with embedded Zoho form/sitemap.xmlview mapping (ZUID 11-a0eaa6de93-2zzclz) — finally makes our custom sitemap live/website-redesign-rfp-template.html+/free-tools.htmlAfter merge
dei-community.htmland drops the ZUID here.