In May 2026, Hampshire College will close its doors. It is a place that has changed tens of thousands of lives that dared to imagine education differently, and soon it will be gone. The campus will go quiet. The email addresses will stop working. If nothing is done, the institutional memory will scatter to the wind.
Â
Yet even as the institution ends, the community Hampshire built need not disappear with it. The stories, the photographs, the Div III projects, the commencement posters, the zines, the late-night debates, the campus traditions; all of it is still alive and still worth preserving. Right now, it exists in fragments: a Facebook group here, a WhatsApp community there, an Instagram account run by an unknown alum, a hard drive no one has opened in years. We invite you to help us gather and preserve these fragments by joining the Frogbook effort and sharing your memories, materials, and ideas.
Â
To address this fragmentation, Frogbook is not competing with Facebook, Instagram, or similar platforms. It is building something Facebook structurally cannot be: a permanent, community-owned, ad-free home for Hampshire’s history — a place where the community controls what remains, what is seen, and who can access it.
Â
In this way, Frogbook offers a digital third space for Hampshire people. It does not aim to replace social media or to ask anyone to abandon the platforms they already use. Instead, it provides a single, shared room where the whole Hampshire community across every generation, every digital habit, every corner of the world, can exist together.
Â
Frogbook’s origins are deeply rooted in the Hampshire community. A group of Hampshire alums had been researching and planning an independent Hampshire Online Image Archive — a collaborative photo and media repository for the community. Their work, documented through shared notes and WhatsApp discussions, covered platform options, feature requirements, community management, and content policy in careful detail.
Â
Recognizing their shared purpose, that group’s research and Frogbook’s infrastructure work were solving the same problem from different angles. This project now brings them together as a single, unified effort. Their platform evaluation, archive expertise, and feature thinking are now foundational to what Frogbook is. Frogbook provides the community infrastructure, technical foundation, and operational framework that their archive vision needs to move from planning to reality.
Â
The Long-Term Archive Vision: The Div III Library
The Div III was the most Hampshire thing about Hampshire. Every student who completed one spent at least a whole year (if not more) on a project entirely of their own design — no grade, no rubric, no template. Thousands of those projects exist only on hard drives, in filing cabinets, or in memory. Building a virtual Div III Library would be the most meaningful archive Frogbook could create — a testament to what independent learning looks like when it is taken seriously.
How Frogbook is built
Frogbook runs on WordPress, the same open-source platform that powers roughly 40% of the web. This means the entire site — the community, the archive, the donation page — lives on infrastructure that is self-hosted, community-owned, and not dependent on any single company’s continued goodwill or business decisions. If a vendor shuts down or changes its terms, we can move. The data stays ours.
Â
The community layer
The social features — member profiles, the activity feed, spaces (groups), direct messaging, and events — are powered by FluentCommunity, a WordPress plugin built by WPManageNinja. It runs directly on the same WordPress install as the rest of the site, so there is no separate social platform to log into. One site, one login, everything in one place. FluentCommunity currently runs on its free plan, which covers all core features. A community vote will determine when to upgrade to the lifetime plan ($399, one-time), which unlocks external media storage and removes free plan limits.
Â
The archive layer
The structured archive — collections, metadata, search, and taxonomy — is powered by Tainacan, a free and open-source digital repository platform built by the University of BrasÃlia and used by museums and cultural institutions worldwide. It runs as a WordPress plugin on the same install. Tainacan is what allows the archive to be properly organized rather than just a pile of uploads: photos can be tagged, filtered by year or housing or division, browsed by collection, and searched by any metadata field. It is the same category of tool that national archives and university libraries use — built for exactly this kind of permanent cultural preservation.
Â
Media storage
At launch, all uploaded media is stored on Hostinger’s servers as part of the current hosting plan. When the FluentCommunity lifetime upgrade is purchased — and Hostinger is upgraded to the Business plan alongside it — media storage will move to Cloudflare R2, a cloud object storage service with no data transfer fees. From that point, every photo, audio file, video, or document uploaded to Tainacan routes automatically to R2 rather than the local server, keeping costs predictable as the archive grows. R2 storage costs approximately $0.015 per gigabyte per month — storing 100 GB of Hampshire history costs about $1.50 a month.
Â
The backup mirror
The final stage of the infrastructure plan is a periodic mirror backup of the entire Tainacan archive to the Internet Archive, a nonprofit digital library that has been preserving the web and human culture since 1996. Tainacan can export collections as CSV and JSON, and these exports will be uploaded to the Internet Archive as a public collection under a Hampshire namespace. This means that even if Frogbook ever goes offline — for any reason — a full copy of the archive exists independently, publicly, and permanently somewhere else. The archive does not depend on Frogbook’s survival.
Â
Donations and financial transparency
Donations are collected through GiveWP, a free WordPress donation plugin built specifically for nonprofits and community fundraising. Payments are processed through a Stripe account registered in Frogbook’s name, which is currently being set up and verified. Once active, there are no platform fees on top of Stripe’s standard rate (2.9% + 30¢ per transaction) — every other cent of a donation goes directly into the running costs fund. Every transaction — income and expense — is logged publicly on Open Collective at opencollective.com/frogbook, where anyone can see the full financial history of the project in real time. GiveWP handles the on-site donation experience; Open Collective handles the public transparency ledger.
Â
Hosting
The site currently runs on Hostinger’s Personal plan, which covers the needs of an early-stage launch. When the FluentCommunity lifetime upgrade is funded by the community, the hosting will be upgraded to Hostinger Business ($4.99/month), which adds daily backups, a free CDN, and significantly more storage capacity — providing the foundation for media expansion and the full archive rollout. The domain is registered through Hostinger as well.