a community for meaning makers
Create Space
Collective
A membership space for people who make things. Tactile practice kits, live make-alongs, and real support to finish and share the work.
Enrika Greathouse · product design and build · 2026
The problem
Making is the easy part to talk about
Most creative people do not need another place to discuss making things. They need the thing they are making to actually leave the building.
Communities stall at talking
Feeds reward posting about the work rather than finishing it.
Courses end alone
The lesson finishes, the support stops, the project does not ship.
The middle is solitary
The hard part is the middle, and nobody is there for it.
The belief it is built on
A tool to do the work, not just a place to connect.
A place to connect puts the rooms at the centre and measures conversation. A tool to do the work puts the loop at the centre and measures work leaving the building.
The palette
Cream ground, ink type, one loud accent
Warm neutrals do the work. The colour is reserved, which is what lets a single highlight mean something when it appears.
The highlight marks one phrase at a time, the way a pen would. The four softer tones belong to the rooms, so a space is recognisable before you read its name. Type is Playfair Display over DM Sans, with a hand face for the asides.
Design throughline
A room to room experience, not a dressed-up forum
Clean, simple, never overwhelming: the work is supposed to be the demanding part.
Rooms, not channels
You walk into a named place with a purpose, not a list of topics.
One thing per surface
Each room asks one question. No unread counts competing for attention.
Drawn, not decorated
Hand-drawn single-weight icons, one per room. Warmth from the line.
Quiet by default
Per-member notification modes, down to quiet. Presence without pressure.
A forum optimises for conversation volume. This optimises for walking in, doing something, and leaving with it finished.
Quiet by default, as a control
The member sets the terms
How quiet do you like your space? Notification modes, down to quiet. Mentions still reach you.
Match-ups, on or off. Weekly meetups suggested from shared goals, only if invited.
Reader voice. The voice that reads things aloud, with a sample to hear first.
Welcome Committee. Count me in, or not now. Greeting newcomers is opt-in.
The framework I design against
Nine stages, four groups, stranger to advocate
Not every product has all nine. A stage left out on purpose is a decision worth stating, not a hole worth hiding.
Get them in
Reach
Enroll
Get them going
First Run
Setup
First Win
Keep them
Home Base
The Loop
Return
Grow through them
Champion
First Win is its own stage: the first time someone gets the thing they came for. Neither orientation nor habit, and where products die.
Arrival
Stranger to first win
The recurring loop
Support is the hub, not a step
Drawn as a step it would say support arrives once the work is done, which is the opposite of what the place is for.
Shipping has two ranges and the order is the argument: seen by a few who care, then by everyone.
Celebrating closes the turn. It is a state, not a page, so it is built into the end of each experience.
Reach
The public pitch
Outreach runs on live interactive letters and small events, published from Delivery, a multi-brand publisher built alongside this.
The letters are the loop run once, in public, for free: watch, make something, write back. The outreach is a sample of the product rather than an advert for it.
First Run
Welcomed by a person, not a tour
Opening it also asks the welcome committee to say hi: existing members are notified to greet the newcomer, matched on shared profile signal.
Shown in the built-in admin preview, which lets a host re-run onboarding without consuming a member's first-run flag.
Home Base
Where a member starts
The dashboard greets you by name and offers a numbered Where to next: step into a space, watch the walkthrough, see what is happening.
The rooms rail runs down the left, hand-drawn, one icon per space, so the place reads as a floor plan rather than as navigation.
Hold this slide in mind. What it offers is the subject of the finding.
The loop, in the product
A weekly rhythm and a place to join
Personal challenges are described in the app as just yours, a pep talk then one small rep a day. That framing is the First Win shaped correctly, and it sits five steps into the loop.
The detail the whole loop runs on
Feedback, on every surface
Support is the hub of the loop, so it cannot live in a comment box at the bottom of a page. Feedback attaches to the thing itself: a phrase, a frame, a point in a picture.
Click any of these to read them properly. Built as one feedback layer rather than three features, so a new surface inherits it instead of reimplementing it.
Both directions
Rich media on all inputs and outputs
Rich going in. It asks you to offer encouraging feedback, then gives you more than text to do it with.
Rich coming out. Any post plays back as speech, in a reader voice the member picks. Media plays inline, highlights toggle off to read clean.
Consent before critique
Feedback has a dial, and a summary
The maker sets the level first. Encouragement welcome tells the room what kind of response is wanted before anyone replies. That is what makes honest critique possible later.
Resonance aggregates the answer. A maker sees the shape of the response without opening every reply.
The granular layer tells you what one person thought of one phrase. This tells you what the room thought of the whole thing.
What the mapping found
The product had no First Win placed at arrival
Every option on the dashboard was orientation. The thing the landing page promises in its first sentence was four clicks away.
The fix turned out to be placement, not capability. Every door into a first post already worked: weekly check-in, Daily Do, work log, ask for help. All of them already land in the Living Room.
Ask for help counting as a first win is the deliberate part: someone stuck with nothing made yet, which is often why they joined, can still cross the line on day one.
Naming the gap correctly changed the size of the work by an order of magnitude. Nothing to build, something to move.
Architecture · as of 3 October 2026
A door, then rooms
Built with
Boring infrastructure, on purpose
| Layer | Choice | Why |
|---|---|---|
| Framework | Next.js 16, React 19 | Server components for gated rooms, one deploy target |
| Styling | Tailwind v4 | Design tokens in one stylesheet, hand-drawn assets stay SVG |
| Data and auth | Supabase, Postgres | Row level security per room, realtime presence, SSR cookies |
| Media | Cloudflare R2 | Member uploads and avatars, served cheaply at any size |
| Postmark | Transactional only | |
| Publishing | Delivery, own build | Multi-brand letters, blogs and social from one place |
| Hosting | Vercel | Preview per branch |
Built solo. The interesting decisions here are the flow ones, not the infrastructure ones.
Where it stands
Pre-launch, by design
Shipped
Public site, invite flow, onboarding, Living Room, Challenges, Maker Rooms, Live Studio, the wall, welcome committee, the feedback layer
In build
Pods and Paths, the interactive Letters edition, Delivery, the First Win placement
Next
Open the gates to the free members already gathering, with the Living Room seeded so the flywheel has something to turn on
Soft enrollment is live and converting visitors into free members now. The full tier opens with the cohort.
Enrika Greathouse · enrika@smallgorillacreative.com