KC Spaces Fund

A finished campaign site for cultural-space mutual aid

Built and maintained the campaign's Ghost-based web stack, customized a reusable theme, and implemented donation, application, sign-up, and contact pathways plus a fundraising progress display for a collaborator-led 2020 mutual-aid campaign.

KC Spaces Fund website showing its cultural-space support message, donation route, navigation, and support section.

The 2020 campaign surface brought its purpose, donation, application, sign-up, contact, and fundraising pathways into one coherent public system. KC Spaces Fund public website capture, August 20, 2026; historical campaign content.

What to know first

My responsibility: Web Infrastructure, Theme & Implementation Support
What became usable: A maintained Ghost site with a reusable campaign theme and visible routes to donate, apply, join, contact, and follow fundraising progress.
Evidence to inspect: Ghost-based campaign web stack and deployment
Customized reusable campaign theme
Jump to artifacts

At a glance

Role: Web Infrastructure, Theme & Implementation Support
Years: 2020
Context: Rapid Public Implementation
Status: Short proof page
Visibility: public-safe
Role fit: Rapid public implementation, product operations, web systems, campaign infrastructure, visual communication, and cross-channel delivery.

From urgency to a legible public system

KC Spaces Fund needed a clear place to turn attention into action during the first months of COVID-19. My documented role was behind the scenes: I built and maintained the Ghost-based web stack, customized a reusable campaign theme, and implemented routes for donations, applications, sign-up, and contact, plus a fundraising progress display.

Design was part of delivery

The visual system did practical work. A single name could travel across the domain and collaborator-led social channels. The home screen stated the purpose quickly, gave the donation action unmistakable priority, and let organizers route people back to one coherent surface.

The result is useful portfolio evidence because implementation and presentation are inseparable here: identity, information hierarchy, action routes, theme customization, and deployment all had to work together under time pressure.

Collective campaign, precise credit

KC Spaces Fund was collaborator-led. I am documenting the public web system I built and maintained, not claiming organizer, fundraising, fiscal-sponsor, account-authorship, or grant-selection authority. That distinction makes the implementation proof clearer: my responsibility was to make the campaign's public digital surface usable, coherent, and ready to act through.

Artifact gallery

workflow / 02

Reusable campaign implementation

A customized Ghost theme, deployment workflow, fundraising progress display, and reusable action-route pattern for donation, application, sign-up, and contact.

Scope and sources

Known

Jamie built and maintained the campaign's public web stack, customized its theme, and implemented its principal action routes for a collaborator-led mutual-aid effort.

Open

Additional implementation artifacts and collaborator role details require separate review before publication.

Protected

Applicant, grantee, donor, subscriber, payment, credential, private correspondence, and sensitive operational records remain offline.

Source basis: Public campaign site, contemporary public campaign records, source-backed implementation evidence, and public-safe archive summaries; private applicant, donor, payment, and subscriber records remain offline.

Claim and care limits

Historical, collaborator-led campaign. This page documents Jamie's web implementation role; it does not assign him organizer, fundraising, fiscal-sponsor, account-authorship, or grant-decision authority.

Keep public organizer credit with the campaign's named organizers and describe Jamie's contribution as web infrastructure, identity support, and implementation.