The Problem
Frogging Nook was a crochet community that lived entirely in group chats and Instagram comments. Workshops got announced in a story, RSVPs arrived as DMs, and if you found the community a week late you had already missed the session. There was no home base — nowhere to see what was coming up, and no way to tell a first-timer what to expect before they walked into a room.
The harder problem was tone. Craft communities can be quietly intimidating. Someone who has never held a hook does not want to show up to a room of people who clearly know what they are doing. Whatever we built had to fix the logistics and lower the stakes at the same time.
What We Did
We built the site around events instead of a storefront. Workshops, meetups, and crochet-alongs each get their own listing, and the full set filters by type so you can find the thing that matches how much you already know. Nothing on the site sells anything.
The writing did as much work as the layout. “Stitch. Share. Belong.” “Materials on us, judgement at the door.” Those lines set expectations before a beginner reads a single event description, and they are the reason the tone holds up on pages we had not designed yet.
Member accounts stayed deliberately thin. Sign up, verify your email, say roughly where you are as a maker — that last part is what lets the site point a first-timer toward a beginner workshop instead of a project-based crochet-along. Anything more would have been a form standing between someone and a hobby.
We built it in Astro, which fit the shape of the problem. Most of the site is content that rarely changes, so it ships as static HTML, and only the parts that genuinely need to be interactive load any JavaScript — event filtering, the sign-up and verification flow, and the Instagram feed behind the gallery.
The Result
Live at froggingnook.com. The community has run 6 workshops and welcomed 59 makers across Kathmandu, Lalitpur, and Bhaktapur, and the site is now where that gets organized rather than something that describes it after the fact.
Designing and building it myself meant the gap between the two mostly disappeared. A layout that did not survive contact with real content got changed the same afternoon, instead of going back around a handoff.
