Why Lattice reads like a strategy document on purpose
A coalition website has one primary reader: the program officer deciding whether five small organizations can really hold one large grant. Everything on this site is engineered for that reader — and this guide explains how.
About this fictional coalition
The Lattice Coalition is a fictional shared-infrastructure initiative formed by five small nonprofits — and here the demo collection folds in on itself: four of the members are the other concept sites (Marigold, Uplink, Junction House, Porch Light), plus a fifth, the Eastside Family Literacy Project. Together they pool grant capacity, coordinated intake, aligned measurement, and back-office operations.
The scenario it represents is increasingly common: funders pushing for collaboration, small organizations wanting it, and nobody having the connective infrastructure — fiscal, data, or narrative — to make it real. Lattice is that infrastructure with a name.
Who this site was designed for
Institutional readers, institutional pathways
Foundation program officers get the whole pitch in scannable order: problem (01), members (02), priorities (03), funding mechanics (04), measurement (05), ask (06). It's a grant proposal you can scroll.
Public-sector partners get the phrase they need for procurement: one accountable fiscal partner with community reach across five service areas.
Prospective member nonprofits get a named pathway to join in year two.
Backbone organizations and intermediaries get familiar collective-impact vocabulary used precisely, not decoratively.
Report-grade, deliberately not dashboard-blue
One type superfamily does everything: IBM Plex Serif for editorial gravity, Plex Sans as the workhorse, Plex Mono for numerals, section numbers, and data labels — the same coherence a well-produced annual report has. The palette is paper, graphite, and steel with a single oxide accent, precisely because civic data sites default to blue dashboards and this one needed to feel like print strategy, not analytics software.
The signature motif is the lattice itself — nodes joined into a load-bearing grid, drawn with organic spacing so it never reads as a circuit board. It animates once, on arrival: the network assembling. Numbered sections (01–06) and hairline rules do the rest of the visual work.
Claims backed by mechanisms
Every assertion on the page is immediately followed by the machinery that makes it true: "one investment" is followed by the flow diagram; "shared measurement" by the indicator set; "infrastructure, not overhead" by the actual list of what the coordination layer does. The voice is strategy-document plain — defined terms, short declaratives, no movement rhetoric.
Deliberately left out: synergy language, unattributed statistics, and any suggestion that members surrender independence — the site repeats member autonomy at every level, because that's the fear that kills real coalitions.
Digital infrastructure elements included
- Numbered document architecture (01–06) that doubles as a proposal outline
- Member directory with live cross-links to member organization sites
- Funding-flow diagram: funders → coordination layer → members → shared outcomes
- Logic model and filterable first-year indicator set with honest target framing
- Combined-reach statistics labeled illustrative — data integrity as a design feature
- Role-routed contact form (funder / agency / prospective member / press)
- Accessible typography, AA contrast, mobile-responsive layout, reduced-motion support
What Rooted & Wired helped clarify or build
- The shared language: five organizations describing one initiative identically — the hardest and most valuable coalition artifact.
- The funding mechanics: a flow model that answers the program officer's first three questions (who's accountable, who reports, who delivers) in one diagram.
- The measurement spine: a common indicator set that respects each member's mission while adding up to one community story.
- The infrastructure itself: a site that functions as the coalition's standing one-pager, memo attachment, and due-diligence packet at once.
How a real coalition could use a site like this
Replace: the members with your members (linked to their real sites — the cross-links are half the credibility), the indicators with the set your members actually agreed to, and the flow diagram labels with your real fiscal structure, whether that's a fiscal sponsor, a lead-agency model, or a new entity.
Keep: the numbered structure and the claims-then-mechanisms discipline. A coalition site that reads like a manifesto loses the institutional reader; one that reads like a strategy document gets forwarded.
Build next: the shared indicator dashboard behind section 05, a members-only coordination space, a downloadable framework deck for the "Request the Framework Deck" button, and an MOU template library for incoming members.
design guide