Capital Campaign Microsite — Page Outline

Client: Ree & Jun Kaneko Foundation Goal: $35M capital campaign Reference model: Brownell Talbot — buildingbttogether.org (5 pages + offsite donate) Status: Pre-quote outline — for internal G&M scoping

Each bullet is tagged: - [meeting] — explicitly stated in the 4/21 meeting or follow-up notes - [Brownell] — pattern borrowed from the reference site - [G&M rec] — our recommendation, client to confirm - [TBD] — unknown, awaiting Sarah/Troia's content doc


Stack & Platform


Page 1 — Home

Page 2 — The Vision

Page 3 — The Collection Building

Page 4 — Support the Campaign

Page 5 — Contact

Page 6 — Donate


Cross-cutting Elements (every page)


Beyond the Microsite — Full Campaign Scope

A capital campaign is more than a website. The microsite is the public-facing hub, but the work that actually drives a $35M raise happens across email, print, video, events, signage, and direct mail. Below is the menu of campaign-wide deliverables G&M is positioned to take on. We can scope these as one bundled engagement or break them into phases tied to the silent → public timeline.

1. Brand & Identity

2. Email Design & Strategy

3. Print Collateral

4. Direct Mail

5. Video & Motion

6. Photography

7. Event Materials

8. Signage & Environmental

9. Social Media

10. Press / PR Toolkit

11. Strategy / Consulting


G&M Recommendations Summary

For when Kristin walks the client through this, here's where we're recommending vs. asking:

Topic Recommendation Why
Donate platform Give Butter, embedded on the dedicated /donate page Already the working assumption from the 4/21 call. Consistent platform across Track 1 (Foundation general giving) and Track 2 (campaign) reduces tooling sprawl for Foundation staff.
3D walkthrough Phase 1: embed the existing fly-through video. Phase 2: add Matterport embed if architect delivers a build. Video assets exist today — fastest path to launch, plays on every device, no dev risk. Matterport-style interactive walkthrough only if it's worth the architect's upload time. Self-hosted three.js/glTF is overkill for v1.
Stack WordPress with a custom theme — standard template pages One custom page template per page, with ACF field groups for content. No Flexible Content modules on this project; the page set is fixed and tightly designed, so per-template fields are simpler than module flexibility.
Donor wall management Foundation self-manages in WordPress admin ACF field group on the Home page template gives Foundation a structured editing UI inside the same WP admin they already use. Saves G&M from a quarterly retainer task. We'd build the schema + UI.

Open Questions Before Final Quote