lunatechs
← Chapter Guide
Tutorial · 4 of 5

Make a recap

After a great night, give it a recap page — a short story, a photo grid, and your turnout. It's how your past events stay alive for newcomers.

One command now. Building and checking a recap are ready-made skills that ship with your kit. Run ./dev.sh once and your assistant picks them up — then the three slash-commands below do the heavy lifting.
1

Build it — /recap

Point /recap at your event's whole photo folder. It does the lot: curates the best ~20 shots (a diverse, flattering mix), writes a short warm story, builds the page, wires it into events.json, and deploys.

Run

/recap — “the photos are in recaps/june-night/raw/; it was our June Vibe Coding night — 42 people, 18 first-timers, 9 projects shipped.”

Give it variety to work with — a big group shot, candids, portraits, people hands-on, your speakers, plus venue, food, and decor. Always include one great wide shot of the full room — that's what sells your scale.

Why it matters: your chapter's reputation rides on the vibe of these photos — and on how big and well-run your nights look. Hand it generous, real, room-filling shots.
2

Polish the words — /recap-editor

An editor's pass over the prose: it makes the voice punchy and on-brand, fact-checks every speaker and partner name, leads with the wow, cuts filler, and catches typos and date slips.

Run

/recap-editor

3

Final check — /recap-check

The technical gate before you share it: the WhatsApp / link preview is correct and loads, no broken images, co-hosts and partners show up, both card buttons work, and the build is clean.

Run

/recap-check

Then publish — it's live at your-city.lunatechs.social/recaps/june-night.

✓
Your event now has a beautiful recap — and your “Past” section is filling up with proof your chapter delivers.
Remember: the site shows a curated handful of web-sized photos — it's not your photo archive. Keep the full set in your own cloud drive (see the website overview).
Next · 5 of 5Make an event page → BackAll guides