MinorMakersNeighborhood maker fair.
A monthly neighborhood maker fair, bringing community projects to people who never read tech blogs — and inviting them to build alongside.
Why this exists
A neighborhood maker fair
MinorMakers is a one-day, free, no-registration neighborhood maker fair. We run it on the third Saturday of every month in a different community space — a library back room, a school courtyard, a borrowed café.
People bring whatever they're making: a hand-knit scarf, a Python script, a 3D-printed prosthetic, a sourdough that finally rose. There's no judging, no selling, no platform — just tables, and people behind them ready to explain.
What it became
We started this in 2024 expecting maybe 20 people. The third edition had 180. By the end of year one, we'd run 14 editions across 7 neighborhoods. About 40% of attendees came back the next month — usually with something new.
The most-shared sentence from feedback: "I didn't know there were people like me in this neighborhood."
What we don't do
- We don't accept corporate sponsorship.
- We don't have a website with featured speakers.
- We don't post photos of attendees online.
- We don't track anything beyond a head count.
It is, intentionally, a very small thing. That's why people keep coming back.
Run one yourself
We've published a 6-page playbook. Borrow it, modify it, run one in your block. We're happy to spend 30 minutes on a call with anyone who wants to start.
How it's going
- Q4 2024MinorMakers idea pitched at a Novawerk open day. First collaborators commit a Saturday afternoon.
- Q1 2025Validation conversations with target users. Scope cut on purpose; the smaller version turns out to be the one people actually want.
- Q2 2025First measurable result: Neighborhood maker fair.. The team writes the playbook so others can replicate.
- Q4 2024Working with a partner organization to extend reach without losing the qualitative care that made it work.
“We didn't want a product launch. We wanted something that would still be here in three years — without us.”
Team & roles
Coordinates direction, runs weekly retros, talks to partners.
Owns the artifact — code, hardware, or the printed thing — depending on the week.
Shows up in person where the work meets the world.
Documentation, retros, community check-ins. Looking for someone.
Get involved
If anything in here resonates — even just one paragraph — that's enough to start a conversation. Lightweight contribution is welcome. So is sitting in on a retro before you decide.
