Static deliverables and working files — design comps, reports, and reference docs. Organized by client below.
Website and Analytics Refresh (EA-2026-0001).
A cinematic scroll experience built from real Guilford photography — the camera moves through campus as each content chapter arrives. Keeps every content piece. Four background treatments to compare below. (Best in a real-GPU browser.)
Concept E refined with the E&F review — kept hero, Concept F audience bar, text pulled off images, soft feel-language stats. The flat/production-ready direction.
Concept G's chrome and content over a scrollable 3D world built from its own hero photograph — a depth map is derived from the image at load time and displaces real geometry, so the near hedge slides against the distant building as you scroll. three.js is vendored locally (no CDN), and with no WebGL or reduced motion it falls back to exactly the flat hero.
The reusable templates from the page-type inventory: Hub (T1), Article (T2), Filterable Listing (T3), Profile/Program (T4), Interior (T5), and the portable Brand Frame (T6).
The same page-type set as Concept G, carrying the Immersive brand plus a GSAP/Lenis scroll-reveal layer.
The warm heritage direction, rebuilt to AA. Includes an animated variant.
file://. On this deployment they work over HTTPS; locally, run
python3 -m http.server in the concepts folder and open the page from
http://localhost. The flat concepts A–G open fine either way.
Note the 3D World ships its own copy of three.js under vendor/three/, so unlike
Concept H it has no CDN dependency at runtime.
GuilfordConsent.reset() in the console to see the
banner again.
Class handout for Guilford’s marketing team. How the GTM/GA4 plumbing works, the eight words that cause every reporting mistake, the five screens that answer real questions, a ten-minute guided lap, and how not to lie to yourself with the numbers. Every figure is Guilford’s own 90-day baseline.
What the finished report looks like inside GA4 — the “Guilford reporting” collection: enrollment funnel, giving, audiences, channels, pages and device, once the tagging plan is live. Illustrative data.
How to get Guilford’s container onto the athletics site — which is vendor-hosted on Sidearm and already carries two GTM containers, its own GA4 and no consent gate. Includes the cross-domain and consent configuration, and four defects found in the live audit.
Shareable issue report for Guilford’s IT team. The bare domain’s redirect strips the query
string, so campaign tags and the Google Ads gclid never reach the landing page.
Includes repro commands, who owns the fix (it’s Slate), and how to verify.
Companion runbook. apply.guilford.edu is Slate and already carries Guilford’s
container — that work is configuration, plus a root redirect that strips campaign parameters.
giving.guilford.edu is WordPress with no analytics at all, which is why the giving
funnel has never had a baseline.
GA4 / GTM implementation plan — funnels, events, audiences, reporting.
Measurement framework tying site metrics to the “Thriving Together” goals.
Inventory of guilford.edu page types feeding the template/redesign scope.
Sub-nav audit of guilford.edu's mega-menus vs. hub-page links, with a per-section plan to cut ~55% of drop-down items. Client recommendation — no nav changes made.
Paste-ready prompt for applying the approved Bordewich and Mencorini copy changes to the Drupal site in the CMS, with the blocked items called out so nothing gets invented.
Why the cyclist in the rotating hero loses her head, and how to carry the fix into the Drupal build — including the two cross-fade constraints any implementation has to keep, and how to verify it.