For community stewards
The town’s voice, run by whoever has Tuesday night free.
Stewards curate the layer above the marketplace — the portal, the collections, the news, the sense that this place has a voice. Volunteer capacity is the binding constraint on all of it.
Outcome 01
A hall-committee volunteer can run it unaided
Not a designer, not a developer, not the operator on call. Anything that fails that test is not finished, however well it works when we drive it.
How nnest does it
Pages are assembled from seven labelled blocks so the person with the password does not need to be the person with the training.
Outcome 02
The community’s voice is its own
A portal is an editorial space, not a neutral results page. A platform that hands you a template and a logo slot has not served you.
How nnest does it
You set what is featured, what the history says and how it looks so the site sounds like your town rather than like a platform.
Outcome 03
Curation proportionate to the capacity available
A model that requires stewards to populate before anything appears will fail on the first quiet month.
How nnest does it
Listings arrive in the portal by geographic boundary so a quiet month costs you nothing, because the site was never empty to begin with.
Outcome 04
What you build here is yours and stays yours
Community groups are rightly wary of building on ground they can be moved off.
How nnest does it
Content, identity, search equity and subscribers accrue to the community so moving to your own domain later is a decision, not a rescue.
Where these come from
Anything that fails the volunteer test is not finished, however well it works when the operator drives it.
The releasability test is the organising outcome for the whole content-management layer. See what's built against them →