Part 8: Building a Community Board in Phases

A help site works best when readers can help each other. In late September I asked whether Digital Den could have a discussion board, using the community on growthhackers.com as my reference.

Learning from someone else's mistakes

I shared screenshots of the GrowthHackers board, and Claude noticed something I hadn't: the site was throwing errors, because some of its web addresses were stuffed with very long lists of ID numbers. We designed our board so it wouldn't fall into the same trap.

Building it in phases

I decided to build the board custom on Supabase rather than bolting on an outside forum product, and to do it in three phases. Phase 1 covers the basics: categories, threads, replies, reactions, reporting a post and moderation. Phase 2 adds following threads, notifications and search. Phase 3 brings images, polls and reputation. My reply to that plan was simply "I like the phases." I also asked for Top Voices, a way to recognize the most helpful members.

Phase 1 went live at /community, along with an admin page at /admin/members where I can promote members to moderator or admin. I tested it with my own admin account and a member test account named Tester Man, cleared the test data, and posted a welcome message in Announcements.

Testing like a batch job

The database tests were run inside transactions that roll themselves back. Each test creates its data, checks the results, and then undoes everything, so nothing is left behind. If you ever ran a batch job against a copy of production before trusting it with the real thing, it's the same idea.

One small loose end from this stretch: an updated privacy policy file was swapped in but left uncommitted when the session ended, meaning it was changed on my computer but not yet saved into the project's history. Easy to fix, and a good reminder to finish each session with everything saved.

The lesson

Study a site you admire, including its mistakes. Build big features in phases. And test database changes the way you'd test a batch job: run it, check it, roll it back.

Try it yourself

When you want a big feature, ask the AI to split it into phases where the first one is useful on its own. Create a test account with an obvious name so you can see the site the way a regular member does, and clear out the test data before you launch.

Next time: a real workflow between the two AI tools, and locking the front door against bots.