Bill W:
Chad G:
#7 of 21 in a series: Building SOAPSzone
Story Idea #099 – Building the SOAPSzone Forum
A publication can talk to readers. A forum lets readers talk to one another.
That distinction is central to the SOAPSzone community plan.
The forum is being built as a place where gig drivers and online consumers can compare experiences, ask practical questions, flag recurring app problems and help identify stories that deserve reporting.
The challenge is making the structure useful without creating a maze. Categories need enough specificity that information can be found later, but not so much that a new visitor faces 80 nearly empty rooms. Short descriptions need to explain where a post belongs without taking over the page.
We are also thinking about the relationship between forum discussion and journalism. A post is a lead, not automatically verified evidence. If ten drivers describe the same behaviour, that can identify a pattern worth investigating; it does not let us skip verification.
Moderation will matter for the same reason. Criticism of companies should be welcome. Harassment, doxxing, unsupported accusations presented as fact and exposure of customer information should not be.
The forum can also connect directly to the Knowledge Base and driver utility app. A driver who documents an incident may be able to move naturally from evidence to discussion to a formal story tip.
This article will follow those design choices in public: software, layout, categories, moderation rules and the things we change after actual people begin using it.
The goal is not to manufacture engagement statistics.
It is to create a room where people doing the work can compare notes—and where some of those notes eventually become reporting.
