4 Months, 601 Members, 18,630 Atomic Essays: Here's the tech stack powering Ship 30 for 30's 30-Day Writing Challenge

Ship 30 for 30 is a 30-day community-based writing challenge.

Every day for 30 days, members ship a single Atomic Essay (a short essay, under 250 words, in a single iPhone screenshot).

Ship 30 for 30 helps beginner writers overcome the most-common struggles in building a writing habit.

• Distractions
• Over-editing
• Perfectionism
• Procrastination
• Self-confidence
• Generating ideas
• Impostor syndrome
• Writing consistently
• Choosing a platform
• Finding time to write

Writing and publishing every day for 30 days takes care of these problems. But doing it with a community working alongside you, providing feedback, accountability, and camaraderie, makes it even better.

Over the last four months, we've had three 30-day cohorts with over 600 total members, each one better than the last. Along the way, we've iterated both the program and the tech stack that powers it.

In the beginning, I felt overwhelmed by the number of options there are to build products and manage communities.

My goal for this post is to share our initial tech stack for the MVP cohort, our current tech stack that will help us scale, and the reasons behind our tech decisions and iterations.

There's a ton to dive into here and I can't wait to answer the follow-up questions, but here's the TL;DR (some affiliate links here):

• Landing page: Carrd, NameCheap, Typeform
• Email: Gmail at first, now ConvertKit
• Course content: Notion at first, now Podia
• Community management: Slack, then Circle, now back to Slack, but also Twitter
• Live sessions + workflows: Zoom, Lu.ma, Loom, Notion, Youtube
• Surveys: Typeform, but Google Forms is fine
• Analytics: Hypefury, ilo.so
• Atomic Essay template: Figma

I have a full post breaking down the tech stack, but since I'm new it won't let me post something with so many links 😂 but here is the thread version in the meantime!