Build /dei-community.html landing page for sam

[ardeay]

Summary

DEI & Community Partnership landing page per sam's brief (2026-08-09).

Standalone HTML page at /dei-community.html, follows the same standalone pattern as vendor-partnerships / media-partnerships / bridgetech (own head, nav, footer, Tailwind CDN).

Structure (8 sections + FAQ)

1. Hero — dual CTA ("Invite us to speak" primary, "Request sponsorship" secondary) + editorial visual (gradient card with warm-accent glow, no stock imagery)
2. Belief statement — "Inclusion is something you build." Scroll-triggered warm-accent highlights on heard, access, act (reduced-motion respected)
3. Content.One + CauseCircle shared commitment — dual logo lockup, 700px max-width paragraph
4. How the commitment shows up — 3 cards (inside the company / in the product / in the community) with editorial icons
5. Community in practice — 4-org logo wall (Ajoin, Nonprofit Storytelling Conference, AFP, BridgeTech) with relationship-type chips
6. Speaking engagements — 2-col with 5-topic list
7. Sponsorship invitation — CTA to /contact-us/?ref=dei-sponsorship
8. Closing CTA — dark-gradient dual CTA
9. FAQ — 4 questions from brief

Design choices per brief

• Brand palette + one warm accent (#D97757, terracotta) used sparingly — eyebrows, highlights, logo strip labels
• No rainbow palette, no demographic stock imagery
• WCAG 2.2 AA contrast throughout
• prefers-reduced-motion respected on belief-statement scroll animations
• Editorial icons (universal-access, people-in-conversation, community/globe) instead of demographic illustrations
• CTAs equal conceptual weight; slightly stronger emphasis on "Invite us to speak" (primary/royal vs outline)

Follow-ups flagged (all deliberately punted from v1)

• CauseCircle logo asset — placeholder wordmark until sam supplies SVG
• Dedicated Zoho sponsorship-request form with sam's field list (name, email, org, initiative, date, location, community served, ask, etc.) — currently CTAs route to /contact-us/?ref=dei-sponsorship and ?ref=dei-speaking for triage
• CMS-driven logo-wall schema for community-in-practice section (org name, logo, alt, URL, year, location, relationship type, description, optional photo) — brief calls for this, hard-coded 4 entries for launch
• Hero editorial image — gradient placeholder until sam supplies an authentic event/team photo (per brief: no generic staged workplace imagery)

URL decision

Brief suggested /dei-community (clean URL). Went with /dei-community.html to match every other standalone landing (vendor-partnerships.html, media-partnerships.html, pricing.html, etc.) — the trailing-slash pattern requires page_html/<dir>/ subdirectory and a Zesty routing rule. Canonical + og-tags all match .html. If sam wants clean URLs, worth a follow-up PR that migrates ALL standalones since one-off inconsistency is worse than the current uniform pattern.

Sitemap

Added /dei-community.html row to webengine/views/sitemap.xml per sitemap-coverage convention.

⚠️ Preview will 404 until sam (or ardeay) creates a Zesty view record for dei-community.html — same manual step as prior standalones. Once created, drop the ZUID in Discord and I'll wire it into zesty.config.json.

Test plan

• Once Zesty view is wired: hero renders on desktop + mobile, dual CTAs visible above fold
• Belief-statement highlights animate on scroll-in, don't animate under prefers-reduced-motion: reduce
• 3 cards stack correctly on mobile
• Logo wall renders 4-col desktop / 2-col tablet / 2-col mobile
• All CTAs route to /contact-us/?ref=… with query preserved
• FAQ accordion opens/closes; first item open by default
• Canonical matches actual URL (/dei-community.html)

Preview (once ZUID is wired): https://hj5v68xn-sam-dei-community.webengine.zesty.io/dei-community.html?zpw=bobby

[github-actions]

💾 Stage sync preview

New files to create (1):

• webengine/views/dei-community.html

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

• webengine/views/sitemap.xml

Unchanged, skipped: 0

_{190 mapped resources · zesty-sync}